Skip to main content
TestDino uses role-based access control (RBAC) at the organization level. All permissions are determined by a user’s organization role, which applies uniformly across every project in the organization. There are no separate project-level roles.

Organization Roles

Five roles form a hierarchy. Higher roles inherit all permissions from lower roles. Users & Roles page showing member list with role dropdowns, invite button, and filter controls

Manage Members

Invite a member

  1. Click Invite Member on the Users & Roles page
  2. Enter the email address
  3. Select a role from the dropdown
  4. Optionally check External User for time-limited guest access
  5. Click Send Invite
NoteOnly Owners and Administrators can invite members. The invite recipient receives an email with a link to join the organization.

Change a role

Click the role dropdown next to any member in the list and select a new role. Role changes take effect immediately.

Remove a member

Click the remove button next to the member. A confirmation dialog appears. Removing a member revokes all access to the organization and its projects.

Filter members

Use the All Roles filter to show only specific roles (Administrator, Member, Viewer, etc.).

Role Delegation Rules

When assigning roles, these rules apply: Constraints:
  • You cannot change your own role
  • You cannot remove yourself from the organization
  • The last administrator cannot be removed or demoted if no owner exists

External (Guest) Access

External members are users from outside the organization who receive time-limited access. Administrators can extend or revoke external access at any time from the Users & Roles page.
TipUse external access for contractors, auditors, or temporary collaborators who need to view test results but should not have permanent organization membership.

Permission Matrix

Organization & Members

Projects

Test Runs & Test Cases

Manual Test Cases & Suites

API Keys & Integrations

Project-level: GitHub App, GitLab, monday, Azure DevOps, Slack App, Slack Webhook. User-level: Jira, Linear, Asana.

Analytics, Reports & Dashboard

Billing & Subscription

InfoMembers can create and edit manual test cases but cannot delete them. Only Owners and Administrators can perform destructive actions on test data.

Best Practices

Troubleshooting

  • Only Owners and Administrators can invite members. Verify your role on the Users & Roles page.
  • Check if your organization has reached the member limit for your plan. See Billing & Usage.
  • You can only assign roles at or below your own level. Administrators cannot assign the Owner role.
  • You cannot change your own role. Ask another Owner or Administrator to update it.
  • All permissions are organization-level. There are no separate project-level roles. Check the member’s organization role in the permission matrix above.
  • Viewers have read-only access. Members cannot perform destructive actions (delete test runs, delete test cases). Promote the role if more access is needed.
  • External access is time-limited (default 30 days). An Owner or Administrator can extend access from the Users & Roles page.
  • Expired external members are automatically removed. Re-invite them if continued access is needed.
  • Project-level integrations (GitHub, GitLab, Slack, monday, Azure DevOps) require Owner or Administrator role.
  • User-level integrations (Jira, Linear, Asana) require at least Member role. Viewers and Billing Managers cannot connect personal integrations.
  • Only Owners and Administrators can create, upgrade, pause, or cancel subscriptions.
  • Billing Managers have read-only billing access. They can view subscriptions, invoices, and payments but cannot change them.

Organizations

Organization setup and structure

Projects

Create and manage projects

Billing & Usage

Manage subscriptions and usage limits

Project Settings

Configure project-level settings

Single Sign-On

Set up SSO and the default role for new users