Role-Based Access Guide
This guide outlines the permissions and capabilities for different user roles within organizations and projects on Lamatic.ai.

Permission Tables
1. Organization Level Permissions
| Permission | Owner | Admin | Editor | Developer | Viewer |
|---|---|---|---|---|---|
| Update organization name | β | β | β | β | β |
| Invite new users | β | β | β | β | β |
| Change user roles | β | β | β | β | β |
| Delete organization | β | β | β | β | β |
| Create Admin | β | β | β | β | β |
Note that to handle billing and organization settings, you need to be an Owner.
2. Project Level Permissions
| Permission | Admin/Owner | Editor | Developer | Viewer |
|---|---|---|---|---|
| Create new projects | β | β | β | β |
| Update project name | β | β | β | β |
| Pause/resume project | β | β | β | β |
| Delete project | β | β | β | β |
| Create/delete API keys | β | β | β | β |
| Secret | β | β | β | β |
| Secret Keys | β | β | β | β |
| Configure job settings | β | β | β | β |
| Deploy project | β | β | β | β |
3. Flows and Agents Level Permissions
| Permission | Admin/Owner | Editor | Developer | Viewer |
|---|---|---|---|---|
| Create new flow | β | β | β | β |
| Update flow | β | β | β | β |
| Delete flow | β | β | β | β |
| Deploy flow | β | β | β | β |
| Test flows | β | β | β | β |
| View flows | β | β | β | β |
| Create new agent | β | β | β | β |
| Update agent | β | β | β | β |
| Delete agent | β | β | β | β |
| Deploy agent | β | β | β | β |
| Test agent | β | β | β | β |
| View agent | β | β | β | β |
4. Prompts and Tools Level Permissions
| Permission | Admin/Owner | Editor | Developer | Viewer |
|---|---|---|---|---|
| Create prompt | β | β | β | β |
| Update prompt | β | β | β | β |
| View prompt | β | β | β | β |
| Delete prompt | β | β | β | β |
| Create tool | β | β | β | β |
| Update tool | β | β | β | β |
| View tool | β | β | β | β |
| Delete tool | β | β | β | β |
5. Context Level Permissions
| Permission | Admin/Owner | Editor | Developer | Viewer |
|---|---|---|---|---|
| Create new database | β | β | β | β |
| Update database name | β | β | β | β |
| Delete database | β | β | β | β |
6. Models and Configuration Level Permissions
| Permission | Admin/Owner | Editor | Developer | Viewer |
|---|---|---|---|---|
| Create new credential | β | β | β | β |
| Update credential | β | β | β | β |
| Delete credential | β | β | β | β |
| Create new configuration | β | β | β | β |
| Update configuration | β | β | β | β |
| Delete configuration | β | β | β | β |
| Update default models | β | β | β | β |
7. Integrations Level Permissions
| Permission | Admin/Owner | Editor | Developer | Viewer |
|---|---|---|---|---|
| Create integration | β | β | β | β |
| Update integration name | β | β | β | β |
| Delete integration | β | β | β | β |
| Update default integrations | β | β | β | β |
8. Test Suites Permissions
| Permission | Admin/Owner | Editor | Developer | Viewer |
|---|---|---|---|---|
| Create test suite | β | β | β | β |
| Update test suite | β | β | β | β |
| Delete test suite | β | β | β | β |
9. Jobs Permissions
| Permission | Admin/Owner | Editor | Developer | Viewer |
|---|---|---|---|---|
| Sync/pause job | β | β | β | β |
Key Points
-
Role Hierarchy
- Owner has full system access
- Admin has organizational management rights
- Editor can manage content and configurations
- Developer can create and modify flows
- Viewer has read-only access
-
Best Practices
- Assign minimum necessary permissions
- Regularly review user roles
- Document permission changes
- Audit access periodically
-
Important Notes
- Only Owners can delete organizations
- Editors can't create new projects
- Developers can create flows but can't deploy them
- Viewers can test flows but can't modify them
Need help? Contact [email protected] for assistance with roles and permissions.