Deprovision a Tenant

You may deprovision a tenant to permanently delete all data, users, and other information associated with the tenant.

Note:

Before you can deprovision a tenant, you must first disable it. A disabled tenant is viewable by an administrating tenant user, including data and metadata, but not accessible by end users.
When a tenant is disabled, the files will be retained if they are not excluded. If the files are excluded, they will be deleted after 30 days by default. For more information, see File Retention
When a tenant is deprovisioned there is a grace period of 6 days before all data, users, and, other information associated with the tenant is permanently deleted. During this 6-day period, you cannot create a new tenant with the same name to ensure no conflicting actions can occur during this period.
This feature is also available through Visier's public APIs. For more information, see Tenants API.

Tenant deprovisioning allows administrators to delete a tenant, including the tenant's data, users, and artifacts. There is no recovery after deprovisioning a tenant.

You may reprovision a tenant after it was deprovisioned using the same tenant code, but the tenant is a fresh, empty tenant. No history of data, users, or artifacts exist in a reprovisioned tenant.

To deprovision a tenant in Visier:

Sign in to Visier as an administrating tenant user and navigate to the studio experience.
On the global navigation bar, click Tenants.
In the list of tenants, disable a tenant.
Tip: Before deprovisioning, take time to make sure that the tenant and its data must be removed. The tenant can be disabled for any amount of time before deprovisioning.
Hover over the disabled tenant and click the Deprovision button . Visier’s internal deprovisioning process may take several days to complete. During this time, you cannot reprovision the tenant.
Warning: Deprovisioning a tenant is not reversible. All data and users are permanently deleted and cannot be recovered.