Tenants, users & roles
Dependra is a multi-tenant platform. Every organization operates within its own tenant, and all data — applications, components, dependencies, and business mappings — is fully isolated between tenants.
What is a tenant?
A tenant represents a single organization in Dependra. When you sign up, a new tenant is created for your company. All of your architectural data lives within this tenant boundary.
Tenants have:
- A unique name and optional brand color
- A subscription plan that determines available features
- Members, each with their own roles and access
No data is ever shared between tenants. This is enforced at every layer of the system — API routes, database queries, and session management.
Users and membership
A single user account (identified by email) can belong to multiple tenants. This is useful for consultants, contractors, or employees who work across organizations.
When a user belongs to more than one tenant, they are prompted to select which tenant to work in after signing in. The active tenant can be switched at any time from the application header.
Roles
Each membership carries a role that determines what the user can do within that tenant:
| Role | View | Edit | Admin settings | Manage users |
|---|---|---|---|---|
| Viewer | Yes | No | No | No |
| Editor | Yes | Yes | No | No |
| Admin | Yes | Yes | Yes | Yes |
| Owner | Yes | Yes | Yes | Yes |
- Viewer — Read-only access to the landscape, dependencies, and blast radius results.
- Editor — Can create, update, and delete applications, components, dependencies, and business mappings.
- Admin — Can manage tenant settings, invite users, assign roles, and create API keys.
- Owner — Full control including billing and subscription management. Assigned to the user who created the tenant.
Grant the minimum role needed. Most team members only need Editor access to contribute to the architecture model.
Switching tenants
If you have access to multiple tenants, use the tenant switcher in the application header. Switching tenants changes your entire data context — you will see only the applications, components, and dependencies that belong to the selected tenant.
The active tenant is stored in your session, so your selection persists across page navigations.