-
Notifications
You must be signed in to change notification settings - Fork 25
Personas
Ryan Wold edited this page Jun 5, 2023
·
16 revisions
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.
Manages all aspects of Touchpoints, including:
- Users
- Inactivate Users
- Organizations
- Form Templates
- Forms
- Data Collections
- U.S. Digital Registry records (Websites, Mobile Apps, Social Media Accounts)
- Manage Background Jobs
Organizational Admin - an executive or delegate responsible for organization-wide data, technology, or FOIA responsibilities
- Access all forms and form responses for an organization
- Manage an Organization's Forms and Responses.
- Read-only access to a Form and its Responses
- a non logged-in public user who uses a .gov website to access and or complete a Touchpoint form
- User can create and edit U.S. Digital Registry records for their Organization
- Manages /admin/registry, /registry, Websites, Digital Products, and Social Media Accounts (similar to the Digital Registry)
- Manages Goal Targets, Goals, Objectives
- User can draft and submit a Data Collection
- (only OMB CX Quarterly submissions for now)
- 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 aUserRole
record - Response Viewer can login and has
ResponseViewer
relation in aUserRole
record - Public users do not login
For more detailed information on how each Persona can use Touchpoints, see the Use Cases.