TurtleApps uses role-based access control (RBAC) to manage what team members can do. Understanding roles helps you set up the right permissions for your team.

Available Roles

Developer

The default role for team members who create and work on tickets.

Can:

Create and edit tickets
View all project tickets
Comment on tickets
View deployments
Access preview environments

Cannot:

Approve deployments
Change project settings
Invite team members
Access billing

Product Owner

For product managers and leads who need to approve work.

Can do everything Developers can, plus:

Approve tickets for deployment
Initiate deployments
Rollback deployments
Assign tickets to team members

Workspace Admin

For team leads who manage the workspace.

Can do everything Product Owners can, plus:

Change project settings
Invite and remove team members
Manage roles and permissions
Configure integrations
View audit logs

Super Admin

Full access to everything. Usually the workspace creator.

Can do everything Admins can, plus:

Access and manage billing
Delete projects
Transfer workspace ownership
Delete the workspace

✨Least Privilege

Assign the minimum role needed for each person's work. Developers who don't need to approve deployments shouldn't have Product Owner access.

Permission Matrix

Action	Dev	PO	Admin	Super
Create tickets	✓	✓	✓	✓
Approve deployments	—	✓	✓	✓
Deploy to production	—	✓	✓	✓
Rollback	—	✓	✓	✓
Project settings	—	—	✓	✓
Team management	—	—	✓	✓
Billing	—	—	—	✓

Changing Roles

Admins can change team member roles:

Go to Settings → Team Members
Click the member's current role
Select a new role from the dropdown
Changes take effect immediately

⚠️Role Changes

When you change someone's role, they immediately gain or lose access to features. Make sure they're aware of the change.

Project-Level Permissions

In addition to workspace roles, you can restrict access to specific projects:

Full Access — Can see and work on the project
View Only — Can see but not modify
No Access — Project is hidden

Rollen & Permissies