Skip to main content
Camall supports multi-tenancy, allowing organizations to manage multiple tenants within a single instance. This guide provides an overview of how tenancy works in Camall and how to configure and manage tenants effectively.

​
Understanding Tenancy in Camall

Tenancy in Camall allows for the segregation of data and configurations for different organizations or groups within a single deployment. Each tenant operates independently, with its own set of users, clients, and resources. Clients can configure isolation based on tenancy to ensure that authentication and authorization processes are scoped appropriately.
  • Single organization tenancy: Clients are restricted to a single tenant, meaning users must belong to that tenant to authenticate. 
    # Single organization tenant must begin authorization under the organization
  https://login.camall.io/{organization_id}/oidc/authorize?client_id=your_client_id&response_type=code&redirect_uri=https://yourapp.com/callback&scope=openid profile email
  • Multi-organization tenancy: Clients can access multiple tenants, allowing users from different tenants to authenticate. 
    # Multi-organization tenant can begin authorization without specifying the organization
  https://login.camall.io/common/oidc/authorize?client_id=your_client_id&response_type=code&redirect_uri=https://yourapp.com/callback&scope=openid profile email