How to Create a Tenant
Navigate to Tenant Creation
To define a new tenant, log in to the MSP Console at https://<your-console-FQDN>/msp/console/
Example: https://demo.codacloud.net/msp/console
From the MSP Console, go to Managed Clients → Create New Managed Client.
Client Information
Tenant Name - The name shown in the tenant drop-down menu (top-right corner).
Website (optional) - Customer's website URL.
Description (optional) - Brief tenant description.
Billing Information
It is divided into two parts: Scanning Frequency and Billing Model.
Scanning Frequency - Choose how often scans and reports are generated for this tenant:
Scanning frequency options
-
Continuous - By default, Continuous means scans are performed daily using the following settings:
Agent-Based - every 8 hours
Agentless (network scans) - once every 24 hours
The timer for the agentless scanner can be set to a different value using the Scheduler.
Monthly - Scans and reports are generated once per month, either on the last day of the month or on a fixed date.
Weekly - Scans and reports are generated once per week on a selected day.
-
Billing Model - Define how the tenant is billed:
Max Billable Assets - Sets the maximum number of assets (devices) that can be billed for this tenant. Defaults to
0(unlimited).-
Enforce Max Billable Assets - When checked, the platform caps billing and blocks additional assets beyond the limit. Once reached, assets found via any scan source - agentless scanning, agent-based scanning, or vulnerability imports - will not be ingested into the platform.
For new tenants, set the limit during tenant creation.For existing tenants, you cannot set the limit below the current device count. To lower it, first reduce devices to the target or below, then apply the new limit.
Client Type
Coda Footprint supports 3 tenant types, each offering a different level of access and management:
Tenant type |
Code |
Managed by |
Customer access to UI/reports |
MSP/MSSP access |
Notes |
|---|---|---|---|---|---|
Fully Managed |
F |
MSSP only |
No |
Yes |
Typical MSSP‑only operation |
Co‑Managed |
C |
Customer/MSP + MSSP |
Yes (role‑based) |
Yes |
Shared management |
Self‑Managed |
S |
Customer only |
Yes |
No |
Software as a Service; no MSP/MSSP access |
For Co-Managed and Self Managed tenants, you must also provide a customer user with a First Name, Last Name and E-Mail address.
Once the tenant is created, the specified user will receive an email invitation to join the platform. If a user with that email address already exists, they will automatically be granted access to the new tenant - no separate invitation is needed.
For Fully Managed and Co-Managed tenants, below the tenant details, you'll see lists of Users and Groups. Select which MSSP users or groups can manage this tenant. This helps restrict tenant visibility to specific roles or teams. Users with the Global Admin role can access all tenants regardless of this setting.
A user can belong to multiple Co-Managed tenants. For example, if dan.pal@acme.org is added to both FN001 – ACME INC and FN002 – ACME PUBLIC, he will see both tenants in their drop-down menu when logging in.
Changing Tenant Settings
After creating your tenant, edit its options by going to MSP Console > Managed clients and filtering by tenant:
Paying vs trial
By default, all new tenants are fully licensed.
You can set a client to Trial, allowing 14 days to scan assets and view reports.
Trial clients have restricted usage quotas compared with fully licensed clients. They can add up to 25 agentless Scan Surface Targets; licensed clients can add an unlimited number of scan targets.
They can also clear databases up to 5 times. Once a trial quota is exhausted, additional scans are blocked. In addition, trial clients cannot manually start or stop Scheduler Tasks.
If more evaluation time is needed, use the Change Trial Period option to extend the trial.
To convert the client back to a paid license, open the same menu used for Convert to Trial Client; once the client is in Trial mode, this option changes to Convert to Paying Client.
How to Delete a Tenant
Delete a tenant directly from the MSP Console. Go to Managed Clients, find the tenant, click the … menu, and select Delete Client. Confirm the action to remove the tenant.
The confirmation shows users configured on the tenant because they will be removed during deletion.
Deleting the tenant suffices for decommissioning. Agents linked to the deleted tenant uninstall automatically during their heartbeat with the console.
No further decommissioning steps are needed after deleting the tenant, except manually uninstalling any ISVMs on the customer side, if applicable.
For customer-facing guidance, you can optionally ask the customer to clear tenant data before deletion by going to Settings → Clear all data from account. This action removes the tenant data and triggers the agents to uninstall during their next heartbeat with the console, but it does not delete the tenant itself. The tenant will still exist in the MSP Console and must still be removed separately by using Delete Client.
Comments
0 comments
Please sign in to leave a comment.