Accounts & Profiles
Deepdesk uses a two-level organization model to separate customers and their internal structures:
- Accounts represent tenants (customers) with isolated deployments and data.
- Profiles subdivide an account by brand, department, region, or business unit.
What is an Account?
An Account typically represents a single tenant (customer) and corresponds to one deployed environment with its own:
- Domain and routing (for example:
acme.deepdesk.com,acme-admin.deepdesk.com) - Configuration and feature toggles
- Authentication setup (SSO, roles, permissions)
- Segregated data storage and analytics
Larger enterprises may operate multiple Accounts (e.g., one per brand or geography). These Accounts are often deployed in dedicated environments for stronger isolation, and enterprise security features.
What is a Profile?
Profiles are subdivisions inside a single Account. Use them to reflect internal structures such as brands, departments, or business units that share infrastructure but require separate:
- Content and suggestions
- Tags and routing rules
- Model training datasets and evaluation
- Feature enablement and configuration versions
In a fresh Account, a default Profile is created during onboarding. Additional Profiles can be added as needed.
Choosing between Accounts and Profiles
Use multiple Accounts when you need:
- Strong data and operational isolation between business entities
- Separate authentication providers or role models per entity
- Independent deployment pipelines and maintenance windows
Use multiple Profiles within a single Account when you need:
- Shared infrastructure and SSO, but distinct content/models per brand/department
- Separate tagging, routing, or feature configs within one tenant
- Easier cross-team administration under a single tenant umbrella