Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Database Ops / Feeds
    • Automate incoming data feed per technical specifications
      • From Athena (in development)
        • Requires opt-out data fields for all Athena categories
        • New field for Athena UID
    • Automate outgoing data feed per technical specifications
      • To Athena
        • SPS opt-out values
        • Universal identifier (TBD)
  • Security and Access Management
    • Create a security model that supports three unique realms to serve the three utility functions
      • Advising
      • Alumni
      • Communications (for Slate+SPS initiative)
    • Create roles to control access to functionality based on business function
    • Update permissions on all existing objects to ensure proper access based on role and need
    • Create security documentation to define what permissions to apply to future objects based on the defined roles and realms
    • Add populations to users based on security requirements
    • Restrictions Management (Opt-outs)
      • Form to capture granular opt-in and opt-out for SPS communications
        • Align communication categories with Athena, and require designation in all communications sent through Slate
          • Categories provided in Athena integration docs
        • Ensure that all restrictions are honored across all communications

Populations

    • Create the populations for each of the defined population groups
    • Create population rules to assign records to the appropriate population(s) based on defined criteria
    • Create queries based on populations and ensure permissions adhere to security model
  • Landing Page
    • Create separate homepage widgets for the Alumni realm highlighting relevant information
      • Actual widgets TBD
  • Communications / Deliver
    • Use the Designer functionality for all standard communications
      • Create components for all of the potential elements that are included in a standard mailing
      • Create templates for each type of message that requires a specific layout
      • Create a simple template that can flex its layout depending on the components in use
    • Create template(s) in simple HTML to accommodate truly unique designs that fall outside of the designer components
      • May require content blocks for shared/reused messages

...