Tenants & organizations
Multi-tenant model, isolation guarantees, and when to use multiple tenants
Tenants & organizations
A tenant is one customer organization in SigSentry. Throughout the dashboard we use the word organization; in the API and database we use tenant. Same thing.
What a tenant owns
- Users — every team member
- Projects — logical groupings inside the tenant
- Subscription — plan tier, billing state, trial status
- System configurations — tenant-wide notification defaults
- Audit log — who changed what, when
Isolation guarantees
All tenant data is fully isolated — one tenant cannot read another's data:
- Logs fetched in an analysis are never persisted; only the resulting diagnosis is stored, scoped to your tenant
- API keys are tenant-scoped — they can never reach another tenant's data
- A user can only belong to one tenant at a time. To switch tenants you sign out and in with a different account
Creating a tenant
A new tenant is created when someone signs up at dashboard.sigsentry.com/signup without an invitation token. That user becomes the owner of the new organization. See Sign up → Create a new organization for the walkthrough.
Multi-tenant within one company
If your company has multiple isolated workloads (e.g. separate teams managing separate products), you can create multiple tenants — but you typically don't need to. Use projects within a single tenant instead. Projects already give you full isolation of log sources, repos, channels, and analyses, and team members can have different project-scoped access via the project access list.
The main reason to create multiple tenants would be billing separation between business units.
