Tenant administration from the Studio, for instance administrators #22

Closed
opened 2026-11-16 20:34:32 +00:00 by claude-bot · 0 comments
Member

Tenants and their members can only be managed with the administration command, connected as the database owner. An administrator of the instance should be able to do it from the Studio.

Proposal

  • Administration API, for the instance role admin only and never under a tenant URL: list and create tenants, rename, suspend and reactivate one, list its members, add a member with roles, change the roles, remove a member; list the accounts of the instance to choose members from.
  • A "Tenants" tab in the administration dialog.
  • The application role of the database receives write access to the tenant registry, which it could only read.

Out of scope

Per-tenant resources (git repository, object storage, AI provider) come with the next part of the multi-tenant work; until then a tenant has a name, a state and members.

Acceptance

  • Unit tests on the service; the routes refuse a user who is not an administrator of the instance, and a request made under a tenant URL.
  • Documented in docs/MULTI-TENANCY.md and its French version.
Tenants and their members can only be managed with the administration command, connected as the database owner. An administrator of the instance should be able to do it from the Studio. ## Proposal - Administration API, for the instance role `admin` only and never under a tenant URL: list and create tenants, rename, suspend and reactivate one, list its members, add a member with roles, change the roles, remove a member; list the accounts of the instance to choose members from. - A "Tenants" tab in the administration dialog. - The application role of the database receives write access to the tenant registry, which it could only read. ## Out of scope Per-tenant resources (git repository, object storage, AI provider) come with the next part of the multi-tenant work; until then a tenant has a name, a state and members. ## Acceptance - Unit tests on the service; the routes refuse a user who is not an administrator of the instance, and a request made under a tenant URL. - Documented in `docs/MULTI-TENANCY.md` and its French version.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
modaka/studio#22
No description provided.