Account Types and User Roles
| This Article Applies To: | |||
| Impact Edition | Pro Edition | Team Edition | Legacy Edition |
Account Types represent the license a User has and separates Team and Role access.
Account Type, which is derived from User Role, exists to restrict access, enforce access, and provide a default for access.
There are three Account Types that will determine User Role access:
- Full
- Standard
- Basic
|
User Role(s) |
Account Type |
|
Community-level User Roles |
|
|
Administrator |
Full |
|
Project Creator |
Full |
|
Member |
Basic |
|
Project-level User Roles |
|
|
Project Manager |
Full |
|
Support |
Full |
|
Observer |
Standard |
|
Participant |
Standard |
|
Applicant |
Basic |
User Roles
The User Roles described below correspond to the intent of the roles and the default configurations for each - you may have significantly different permissions assigned your Teams with these User Roles, but the purpose of these User Roles should generally align. For example, your internal / employee testers should be on teams with the Member user role.
Community
- Administrator: Owns the Community and has access to all community data.
- Project Creator: Exclusively creates projects and has no community data access.
- Member: Exists to be a test candidate/participant.
Project
- Project Manager: Project owner who controls access and structure, having access to all project data.
- Support: Support the Project Manager with Feedback triage and tester management, having access to all project data.
- Observer: Internal Users who can view a Project’s data, but not make any changes. Ideal Observers include; Stakeholders and non-Support Team Members.
- Participant: Provides Feedback and collaborates with other Users on public Feedback.
- Applicant: Exists solely for participant backup and consideration.
Notes:
- User Role defaults and intents are the same across all Centercode license editions.