Access
Roles & Permissions
Tenki Cloud's role-based access system. Learn about Owner, Admin, and Standard roles, workspace vs. project scopes, and detailed permission breakdowns.
Roles are designed to help admins create tailored environments that align with their specific use cases.
Currently, a user can be assigned only one role per workspace. For example, a user might have an admin role in one workspace, while holding a standard role in another.
Roles
We currently support the following roles:
| Role | Description |
|---|---|
| Owner | Automatically assigned upon Workspace creation. Provides full control over the Workspace. |
| Admin | Full access to manage resources, configurations, and settings. |
| Standard | Focused on day-to-day operations within assigned workspace and projects. |
Scopes
Tenki supports two access levels: Workspace and Projects, allowing permissions to be granted at either level. The scope is defined when inviting a user but can also be adjusted later from the Members page.
| Scope | Description |
|---|---|
| Full Workspace | Includes access to all projects currently in the workspace, as well as any that are added in the future. |
| Project Specific | Access restricted to selected projects only. |
Action-Based Permissions
The table below outlines the actions available for each role:
| Actions | Owner | Administrator | Standard |
|---|---|---|---|
| View Workspace Dashboard | ✅ | ✅ | ✅ |
| Create Workspace | ✅ | ✅ | ✅ |
| Edit Workspace Settings | ✅ | ✅ | ❌ |
| Delete Workspace | ✅ | ✅ | ❌ |
| View Project Dashboard | ✅ | ✅ | ✅ |
| Access Runners Activity | ✅ | ✅ | ✅ |
| Create Project | ✅ | ✅ | ❌ |
| Connect GitHub Org / Repo | ✅ | ✅ | ❌ |
| Edit Project Settings | ✅ | ✅ | ❌ |
| Delete Project | ✅ | ✅ | ❌ |
| View Members | ✅ | ✅ | ❌ |
| Edit Members Access | ✅ | ✅ | ❌ |
| Invite New Members | ✅ | ✅ | ❌ |
| Trigger Workflow | ✅ | ✅ | ✅ |