Concepts
Organization and tenants
How Diska isolates data between companies and manages permissions.
Diska is multi-tenant. Each organization has its agents, Flows, histories, telephony and API keys isolated.
Hierarchy
Diska platform
├── Organization (tenant)
│ ├── Agents
│ ├── Flows
│ ├── Members
│ ├── Integrations
│ ├── Telephony
│ └── Histories
Roles
| Role | Capabilities |
|---|---|
| Owner | Full control, including deleting the organization. |
| Admin | Organization settings, members, API keys and deletions. |
| Membro | Creates, edits and publishes agents, flows and knowledge. |
| Visualizador | Read-only plus testing, no changes. |
Details under Members.
Authentication
Sign-in is handled by Diska's identity service (Better Auth). Every request carries the active organization, so the API always knows which workspace to operate on — data from different organizations never crosses.

