Tenant Dashboard

The Tenant Dashboard within Clonable was developed for agencies and organizations that manage multiple clients.
Instead of each client configuring settings and managing subscriptions independently, everything is managed centrally through a tenant environment.

A tenant acts as a management layer above multiple customer accounts and makes it possible to manage branding, support, subscriptions, invoicing, and feature access.

Accounts

Within the Tenant Dashboard, there are two types of accounts:

• tenant accounts (employees of an agency)
• customer accounts (end clients of the agency)

Tenant accounts

Tenant accounts are intended for agency employees. Within these accounts there are two roles:

1. The member role
2. The owner role

Members assist with managing clients within the tenant environment, while owners have full administrative rights within the tenant settings.

Permission	Member	Owner
invite customers	✅	✅
start support sessions	✅	✅
modify clone settings	✅	✅
assist customers with configuration	✅	✅
manage subscriptions	✅	✅
invite members		✅
modify billing details		✅
modify contact details		✅
manage invoices		✅
manage customers		✅

Customer accounts

Customer accounts are the end clients of a tenant, and the clients who ultimately want to have a translated website.
They have their own Clonable account to log in with, but are organizationally linked to the tenant.

An important distinction is that tenants themselves do not create clones and do not manage subscriptions directly; this is handled by the agency employees.
Customer accounts do have access to their clones and the underlying clone settings, allowing them to manage translations themselves.

Features of the Tenant Dashboard

The Tenant Dashboard provides agencies with extensive control over customer environments and configurations.

Whitelabeling

info

Whitelabel configuration can only be set up by Clonable employees.

The tenant environment allows you to use your own branding within the Clonable backend.
This includes the ability to customize:

• custom logo
• custom colors
• custom login page
• custom registration page

This creates a consistent environment for customers without visible Clonable branding (if desired).

Support sessions

With support sessions, tenant members can temporarily access customer accounts to modify settings or provide support.

Examples of actions during support sessions:

• Creating clones
• Managing subscriptions
• Providing technical support

This prevents customers from having to perform complex configurations themselves.

Feature management for customers

Tenants can determine which parts of the dashboard are visible or available to customers.
This makes it possible to disable specific functionalities that customers should not modify, helping simplify the user experience.

Custom customer support

Tenants can choose to provide first-line support themselves instead of direct support from Clonable.
This means:

• customers contact the tenant directly
• the tenant manages communication and support
• Clonable remains available as second-line support if needed
• transactional emails are first sent to the tenant

Subscriptions and invoices

Within a tenant environment, subscriptions and invoicing are managed centrally by the tenant, not by individual customers.
Subscriptions are always managed at the tenant level and not by customers themselves. The standard Clonable subscription plans are used.

caution

Tenants are responsible for selecting the correct subscription plan for the customer.

Invoicing

Invoices are never sent directly to customers.

Instead:

• the tenant receives all invoices
• the tenant manages payments towards Clonable
• the tenant may handle invoicing towards customers themselves

Tenants can choose between:

• one consolidated invoice for all customers
• separate invoices per customer

How these costs are internally or externally passed on to customers is determined entirely by the tenant.

Workflow within a tenant

A typical workflow looks as follows:

1. Customers register through the tenant registration page (this can also be done by the tenant on behalf of the customer)
2. Tenant employees configure clones and settings
3. Customers manage their translation settings within their account
4. Invoicing is handled through the tenant
5. Support is handled through the tenant

This structure makes it possible to efficiently and centrally manage multiple customer environments.