Skip to Content
AdministrationRoles

Roles

Access in Reelspect is set at two levels: each person has a role in the organization, and a role in each project they work on. To assign roles, see Members.

Organization roles

RoleDescription
AdminManages the organization: people, projects and integrations. Acts as a Manager in every project of the organization, unless given a different project role.
MemberHas no organization management rights. Sees only the projects they are added to, plus public projects.

Project roles

RoleDescription
ManagerEverything a Tester can do, plus test case statuses, project settings and project members.
TesterBuilds and runs tests: Library test cases, test plans, runs, schedules, tags and Jira issues.
ViewerSees everything in the project and works in their own Sandbox, but cannot change shared content.

Viewer is not a read-only role. A Viewer can create and launch test cases in their own Sandbox, ask questions in Knowledge and in the session chat, and generate session reports.

How a person’s project role is decided

Reelspect uses the first rule that applies:

  1. A role given to the person in the project’s Members settings. This applies to organization Admins too: an Admin given an explicit project role gets that role, not Manager.
  2. An organization Admin with no explicit project role is a Manager.
  3. In a public project, any other member of the organization is a Viewer.
  4. Otherwise, the person has no access to the project.

Whether a project is public is chosen when the project is created. See Project settings.

Project permissions

ActionViewerTesterManager
View the Library, test plans, runs, schedules, results and session recordingsYesYesYes
Use their own Sandbox: create, edit, delete and launch test casesYesYesYes
Send a Library test case to their own SandboxYesYesYes
Link Jira issues to their own Sandbox test casesYesYesYes
Ask questions in the session chat and generate session reportsYesYesYes
Ask questions in KnowledgeYesYesYes
Promote a Sandbox test case to the LibraryNoYesYes
Create, edit, move, duplicate and delete Library test cases and collectionsNoYesYes
Add and delete comments on Library test casesNoYesYes
Change a test case’s status (Draft, Active, Deprecated, Decommissioned)NoNoYes
Create, edit, delete and launch test plansNoYesYes
Create, edit, delete, launch and cancel runs; add and remove test casesNoYesYes
Override the status of a resultNoYesYes
Create, edit, pause, delete and trigger schedulesNoYesYes
Create, edit and delete tagsNoYesYes
Link and unlink Jira issues on Library test cases, plans, runs and resultsNoYesYes
Report an issue to Jira from a resultNoYesYes
Edit the project’s general settings (name, description, default URL)NoNoYes
Add, change and remove project membersNoNoYes

Organization permissions

ActionMemberAdmin
See the organization’s member list and Devices pageYesYes
Run a Device Bridge and manage their own bridgesYesYes
Create projects (New Project)NoYes
Add people, change organization roles, regenerate setup links, remove membersNoYes
Set up Jira connections and project mappings (Integrations)NoYes
Cancel all running and queued runs and Sandbox sessions in the organization (Stop all); schedules are not pausedNoYes
Act as Manager in every project without an explicit project roleNoYes

A bridge can only be made public, moved or removed by the person who registered it, whatever their role. See Private and shared devices.

Most buttons are shown to everyone in the project, whatever their role. If your role does not allow an action, Reelspect rejects it when you try and shows an error message. Only a few controls are hidden from people who cannot use them: New Project, the organization’s member management and Integrations, project member management, Stop all and the bridge owner controls.

When role changes take effect

Changes to a person’s project role apply straight away. A change to someone’s organization role, for example from Admin to Member, can take up to 5 minutes to reach the projects where they had the implicit Manager role.