Manage Tenants


By default, the suite administrator belongs to the root tenant. The suite administrator can perform the following tasks at this level:

  • Create sub-tenants

  • Modify the root tenant 

Each task is explained in the context of configuration tabs that are explained in the following sections.

Tenants List Page

When you navigate to the Tenant page from the Suite Admin Dashboard, you see the following details:

  • My Tenant: This is always the parent tenant from each CloudCenter Suite user's perspective! The suite administrator always belongs to the root tenant that was configured during the Initial Administrator Setup

  • Sub-Tenants: Each tenant admin can configure sub-tenants as required. If configured, they are listed in this section. Once configured, the sub-tenant admin receives an automatic welcome email.

The Tenant ID and the administrator's email is also listed in this page for both the My Tenant and the Sub-Tenants sections.

General Settings Tab

The root tenant configuration in this section is restricted to modifying the Tenant Name and Tenant Login ID. Root tenant users cannot disable or delete themselves.

When configuring sub-tenants, a tenant admin can configure the following details:

  • Tenant Settings: Tenant Name and Tenant Login ID

  • Tenant Admin Settings: First and Last Names, Email, and Auto Generate Password (default) to trigger a new message to this user (not available for the root tenant).

    If you disable the Auto Generate Password switch, you must manually create a password and manually send an email to this user.

    The eye icon besides making the password visible also monitors the password rule check to ensure that you set an acceptable password based on the listed rules. The password rules are configured by the suite administrator as specified in the User Password Rules Tab section below.

    The SMTP settings must be set up on a per-tenant basis as required for your enterprise. See Email Settings for additional context.

    Either way, when the user's password expires, the user sees this alert when logging in for the first time, along with a link to change the assigned password. Be sure to change the password and then dismiss the alert. The user has 30 days to act on this message and use the link to change the password.

  • Module Assignment: Select the modules that this tenant user can access by virtue of being in this tenant. The Initial Administrator can manage modules for sub-tenants at the root-tenant level

Branding Information Tab

This tab is only available at the My Tenant level. The information in this tab is inherited from the parent tenant, if configured. However, tenant admins can overwrite this information for their respective sub-tenants. 

To configure branding information at the My Tenant level, follow this procedure.

  1. Click the link in the Tenant Name column to open the Editing tenant Tenant Name form. This form has three tabs.

  2. Click the General Settings tab, if required.

  3. Click the Branding Information tab to configure the product branding, terms of service, privacy policy, and trademark details as listed in the form. All details in this form are optional and the default Cisco settings are identified in the Suite Admin DashboardFooter section.

  4. Click the User Password Rules, if required.

  5. Click Done.

User Password Rules Tab

This tab is only available at the My Tenant level. The information in this tab is inherited from the parent tenant, if configured. However, tenant admins can overwrite this information for their respective sub-tenants.

Predefined Tenant Actions

On the Tenant list page, the Actions column displays a dropdown list of actions that each Tenant admin can perform based on group membership and permissions. 

The following table identifies the actions available at the Tenant Level.

Tenant-Level ActionDescription
EditAvailable at the My Tenant and Sub-Tenant levels.


Once disabled, you must first enable a user to assign the user to a group and to see other Actions for this user.


When you attempt to delete a tenant or sub-tenant, the Suite Admin triggers a confirmation process to verify (with each module) that the resource can be deleted. If all product modules confirm the deletion, then the tenant or sub-tenant deletion is permitted to proceed. If the resource cannot be deleted the module returns a failure message with information about associated resources.

Associate Modules

This action provides the tenant admin with the ability to associate or disassociate one or more installed modules for users in this tenant. See Manage Module-Specific Content > Associate Modules for additional details.

If you disable all modules for a tenant, then users in this tenant are abandoned and cannot view an information in the CloudCenter Suite.

Impersonate User

A suite administrator or a tenant administrator can temporarily sign into the CloudCenter Suite as a different user. See Create and Manage Users > Impersonate User for additional details.

Module-Specific ActionsThis is a fluid list based on which module-specific actions were made available for each tenant, user, and module. See Manage Module-Specific Content for additional details.
  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks