Repository navigation
Tenancy and isolation model for TAMS #232
Description
Context
TAMS does not currently appear to define a clear tenancy or isolation model. If TAMS is intended to support multi-tenant deployments, some form of isolation may be required for content separation, access control, and tier-based billing.
Description
This issue is intended to start a discussion on whether TAMS should define a tenancy model.
The following points should be clarified:
- How should tenant information be passed to TAMS?
- If explicit tenancy is not introduced, would a namespace-based model be a better fit for TAMS?
- How should TAMS APIs be isolated if tenancy is introduced?
Use Case
- Guarantee content isolation when TAMS is used as a multi-tenant application.
- Support tier-based billing when TAMS manages the underlying storage.
Activity
j616 commentedon Jul 20, 2026
Thank you for your issue. Please see AppNote0016 for approaches to fine-grained authorisation. PR #229 is extending this model to Storage Backends. This will allow tier-based billing to be carried out either by creating Storage Backends associated with specific charge-codes and use scoped to specific groups accordingly. Otherwise, billing may be applied by inspecting the
created_byfield or theauth_classestags on Flows.Akshay-Narayan-Pai commentedon Jul 20, 2026
Thanks for the reference, will look into it