Skip to content

Personas

Jump to bottom
Ryan Wold edited this page May 21, 2021 · 16 revisions

⏪ Product Cycle

Who is Touchpoints built for?

A Persona represents a general category of user, based on the user's behaviors and needs. Often, Personas are "brought-to-life" via real-world examples, pictures, interviews. Generally, Personas are a place to collect and display information related to user needs and how they interact with a system.

List of Personas

System Administrator

Manages all aspects of Touchpoints, including:

  • Users
    • Inactivate Users
  • Organizations
  • Form Templates
  • Forms
  • Manage Background Jobs
Form Manager - User who manages one or more Forms
  • Manage an Organization's Forms and Responses.
Response Viewer
  • Read-only access to a Form and its Responses
Website Owner
  • User can create and manage a new website inventory record
Person who responds to Data Collections
  • User can draft and submit a Data Collection
    • (only OMB CX Quarterly submissions for now)
Public users
  • a non logged-in public user who uses a .gov website to access and or complete a Touchpoint form

Assumptions

  • Users can only belong to 1 Organization at a time
  • A User can only be added to a Form that belongs to the same Organization as the User

How do Personas map to Roles & Permissions?

  • Admin has admin flag set
  • Form Manager & Response Viewer can login and do not have admin flag set
  • Form Manager can login and has FormManager relation in a UserRole record
  • Response Viewer can login and has ResponseViewer relation in a UserRole record
  • Public users do not login

For more detailed information on how each Persona can use Touchpoints, see the Use Cases.

Clone this wiki locally