Roles and permissions

Roles organize your team. SurveyTester uses roles to grant permissions to users: every user should be assigned to at least one role, otherwise they cannot do anything in SurveyTester.

One user, several roles

A user can have several roles. The user receives the permissions of all assigned roles.

Example: you have a role for project managers and one for scriptwriters. Most team members have one role; some colleagues have both and therefore the combined permissions.

Granular permissions

When defining a role, an administrator grants granular permissions to it. A role that includes User/Role Management can only manage permissions that it has itself.

Initially, many users are simply administrators with many permissions. Over time you should organize your team more efficiently and show team members only the areas they need for their work.

Empty roles as groups

Typical roles grant permissions on features, but you can also create empty roles without any permissions and use them like groups.

Because roles can be assigned to projects, all team members with that role get access to the projects the role is assigned to. This is how you model end clients: everyone who works on a client's projects is a member of that client's role/group and gets access to its projects through it. Their functional level is defined by other roles, such as Internal Tester.

Roles and issues

• You can assign roles to issues. Roles without the permission CanSeeAllIssues only see issues of projects they are assigned to.
• In an issue description or comment you can mention a role with @RoleName. All users of that role receive an email notification.
• The Issues table shows the roles of the users who reported issues. Only roles with functional permissions are shown there.

Role descriptions

You can add a description to a role. Users see this description where roles are listed, which helps them understand what a role is for.