Roles and Permissions
Note
Enterprise Feature: Roles and Permissions is available exclusively for Enterprise clients. This feature provides granular control over user access and permissions across your workspace.
Overview
Treblle’s Roles and Permissions system allows you to create custom roles with specific permissions tailored to your organization’s needs. Unlike the previous system with only Member and Owner roles, this new implementation offers:
- Granular Permissions: Fine-grained control over what users can access and modify
- Custom Roles: Create unlimited roles with specific permission combinations
- Per-API Access Control: Roles are assigned per API with environment-specific restrictions
- Environment-Specific Roles: Assign roles to specific environments (Production, Staging, Development)
Key Concepts
Roles
A role is a collection of permissions that can be assigned to users. Roles define what actions users can perform within your workspace and APIs.
Default Roles:
- Owner: Full access to all workspace and API features
- Member: Standard access with limited administrative capabilities
Both default roles can be customized to fit your needs.
Permissions
Permissions are specific actions or access rights grouped into two main categories:
Workspace Level Permissions
- Billing management
- Catalog access
- Workspace settings
- User management
API Level Permissions
- Request viewing and management
- Endpoint configuration
- API settings
- Integration management
Understanding Role Types
Treblle supports three main role types visible in the roles list:
1. Owner Role
- Full administrative access to all workspace features
- Can manage billing, users, and all APIs
- Typically assigned to workspace administrators and team leads
- Cannot be deleted as it’s a system role
- Default permission count: 33 permissions
2. Member Role
- Standard team member access
- Can view and work with APIs they have access to
- Limited administrative capabilities
- Default permission count: 14 permissions
- Most common role for development team members
3. Customer Role
- External user access for clients and partners
- Read-only permissions by default
- Typically has access only to “View My Requests”
- Default permission count: 1 permission
- Enable “Is Customer Role” toggle when creating roles for external users
How Roles Work
- Per-API Assignment: Roles are assigned per API. When a user is given access to an API, they are assigned a specific role for that API with optional environment restrictions
- Consistent Permissions: Users maintain the same role permissions on each API they access, but can have different roles across different APIs
- API Access Required: Having a role doesn’t automatically grant API access - users must be added to APIs via API Access
Managing Roles
Viewing Roles
Navigate to User Management > Roles to view all roles in your workspace.
The Roles table displays:
Column
Description
Name
Role name
Environment
Environments where the role applies (Production, Staging, Development, All)
People
Number of users assigned this role
Permissions
Number of enabled permissions
Role Actions:
Each role in the table includes an actions menu (•••) providing quick access to:
- View Role: Opens the detailed role view showing all permissions and assigned users
- Delete: Removes the role from the workspace (only available if no users are currently assigned to the role)
Creating a New Role
- Click + New Role in the Roles page
- Fill in the role details:
- Role Name: Enter a descriptive name (required)
- Environment: Select one or more environments where this role applies
- Select permissions:
- Expand Workspace Settings to view and select workspace-level permissions
- Expand API Level Access to view and select API-level permissions
- Permissions are organized by category for easy navigation
- Click Create Role
Environment-Specific Roles
Roles can be assigned to specific environments to control access based on deployment stage:
- Production: Live production environment
- Staging: Pre-production testing environment
- Development: Development and testing environment
- All: Role applies to all environments
Note
Environment Configuration: Environments are fully configurable per API. The available environments will reflect what you’ve defined in your API settings. You can configure environments when setting up your API or through your workspace settings to match your deployment workflow.
Note
Customer Role Toggle: When enabled, this designates the role for external users. Customer roles typically have limited, read-only permissions and are designed for clients who need visibility into their API usage without administrative access.
Permission Categories:
Workspace Permissions
API Permissions
User Management and Security Permissions
Tip
Best Practice: Create roles based on job functions (e.g., “Developer”, “QA Engineer”, “Product Manager”) rather than individual users. This makes it easier to manage permissions as your team grows.
Editing a Role
- Click the ••• menu next to the role
- Select Edit
- Update the role name, environment, or permissions
- Click Save
Viewing Role Details
To view comprehensive information about a specific role, click on the role name in the Roles table. This opens the role detail view.
The role detail view includes:
Header Information:
- Role Name: Displayed prominently at the top
- Environment Assignment: Shows which environments this role applies to (e.g., “None” means all environments)
- People Count: Number of users currently assigned to this role
- Action Buttons:
- “Edit Role & Permissions” - Modify the role
- “Delete” - Remove the role (if no users assigned)
Deleting a Role
Caution
Important: A role cannot be deleted if any users are assigned to it. You must first reassign or remove the role from all users.
To delete a role:
- Ensure no users are assigned to the role (check the People column)
- Click the ••• menu next to the role
- Select Delete
- Type
DELETEto confirm - Click Delete Role