Fleet & Inventories•4 min read•Multi-Tenant
Projects & Role-Based Access (RBAC)
Structure workloads across isolated project workspaces and delegate operational permissions with Owner, Maintainer, Operator, and Viewer roles.
CIEL isolates infrastructure assets, playbooks, secrets, and task executions by project workspace. Access within each project is governed by role-based permissions.
1. Project Workspaces (/projects)
Every asset in CIEL is bound to a specific project:
- Resource Scoping: Hosts, inventories, playbooks, variable sets, SSH keys, saved runs, and schedules belong exclusively to their active project.
- Filesystem Isolation: The controller maintains a dedicated directory structure for each project under
workspaces/<project_id>/containing local playbook files, temporary runner environments, and execution artifacts. - Fast Switching: Use the project dropdown at the top of the sidebar to switch between project workspaces. The UI updates the active context immediately.
Creating and Managing Projects
- Open the project switcher in the sidebar header and select Manage Projects (or navigate to
/projects). - Click Create Project, provide a name and optional description, and submit.
- Project settings allow owners and maintainers to update the display name, description, and assign default execution container images.
2. Project Roles and Permissions (/members)
Access within each project is divided into four distinct roles, plus the global system administrator:
| Role | Operational Scope | Key Permissions |
|---|---|---|
| Workspace Owner | Project Governance | Full administrative control. Manage members, change roles, configure secrets, delete the project, and execute playbooks. |
| Maintainer | DevOps & Automation Engineering | Create and edit playbooks, manage hosts and inventories, configure schedules and notification channels, view secrets, and execute tasks. Cannot manage members or delete the project. |
| Operator | Day-to-Day Operations | Trigger playbooks, run saved runs, execute schedules manually, cancel running jobs, and inspect live execution logs. Cannot edit playbooks, modify inventories, or view plaintext secrets. |
| Viewer | Audit & Monitoring | Read-only access to playbooks, host metadata, execution streams, and job histories. Cannot trigger executions or inspect secrets. |
| System Admin | Global Platform Administrator | Unrestricted read and write access across all projects, system users, licenses, and global settings. |
Capability Matrix
The /members workspace displays a live capability breakdown across five core domains:
- Workspace Governance: Project deletion and team membership are strictly restricted to Owners.
- Playbooks & Inventories: Creating, editing, and deleting playbooks or server groups is restricted to Owners and Maintainers.
- Execution & Jobs: Owners, Maintainers, and Operators can run playbooks, relaunch jobs, and cancel active runs.
- Secret Variables & Keys: Plaintext secret inspection and variable editing require Maintainer or Owner permissions. Operators and Viewers only receive masked values (
********).
3. Managing Team Members
- In the sidebar under Project Workspace, navigate to Members (
/members). - Click Add Member.
- Select an existing user account from the directory and choose their assigned role (Owner, Maintainer, Operator, or Viewer).
- Click Add Member to apply permissions.
- Owners can modify a member's role or remove their workspace access at any time using the action menu on the member's card.
4. External References
For access control standards and multi-tenant security architecture:
- NIST Role-Based Access Control (RBAC): Formal model for role assignment, permission encapsulation, and least privilege.
- OWASP Access Control Cheat Sheet: Authorization guidelines for multi-user web platforms and API endpoints.