Platform Admin Console
Overview
The Platform Admin Console and its sub-modules — Tenant Management and Platform User Management — are available exclusively in the Commercial Edition. The Community Edition does not include these features. For multi-tenant scenarios, please use the Commercial Edition.
The Platform Admin Console is a specialized management portal for platform operations personnel. It exists independently of any regular business tenant and is delivered through a special system tenant (tenant ID 100000000). It handles only two platform-level responsibilities: managing the lifecycle of all business tenants and managing the operations accounts that can log in to this console.
You can think of it as the "root admin backend" for the entire platform:
- Administrators within a business tenant can only manage that tenant's own configuration items, users, collection resources, and so on.
- Operations personnel in the Platform Admin Console stand above all business tenants — they provision new tenants, suspend abnormal tenants, and maintain the platform's own login accounts.
What This Module Helps You Do
- Provision new business tenants: Create a fully isolated workspace for a new customer or business line and designate the first administrator.
- Control tenant runtime state: Start, stop, disable, or delete business tenants to handle expiration, anomalies, policy violations, and similar scenarios.
- Trace tenant changes: View the complete history of every tenant from creation through every status change.
- Maintain platform login accounts: Manage the operations accounts that can access this console, ensuring the platform's own access security.
How to Access the Platform Admin Console
The Platform Admin Console uses a dedicated URL that is different from the login entry point for regular business tenants:
| Entry Point | URL Format | Purpose |
|---|---|---|
| Platform Admin Console | https://<platform-domain>:<port>/itom/ui/100000000/ | Login for platform operations personnel |
| Default Business Tenant | https://<platform-domain>:<port>/itom/ui/100000001/ | The system-provisioned business tenant, ready out of the box |
| Business Tenant | https://<platform-domain>:<port>/itom/ui/<business-tenant-id>/ | Login for business users |
After logging in, check the left-hand navigation:
- If the navigation shows only "Tenant Management" and "Platform User Management", and the top banner reads "Platform Admin Console" — you are in the system tenant.
- If the navigation shows the full set of business menus such as "CMDB", "Discovery & Collection", "Users & Permissions" — you are in a business tenant.
Key Features
- Tenant-level isolation: Each business tenant has its own independent data space, user system, and permission configuration. Tenants never interfere with each other.
- Lifecycle management: Covers the full closed loop from creation, start, stop, disable, through deletion of a tenant.
- Platform account independence: Accounts created in "Platform User Management" can only log in to the Platform Admin Console — they cannot access any business tenant. Conversely, users within a business tenant cannot enter the Platform Admin Console.
- Traceable changes: Every status change and field modification on a tenant is recorded in the change history and can be reviewed at any time.
Differences Among System Tenant, Business Tenant, and Default Business Tenant
Understanding the differences among these three tenant types is a prerequisite for using this console effectively:
| Business Tenant (Regular) | System Tenant (This Console) | Default Business Tenant | |
|---|---|---|---|
| Tenant ID | Assigned by the system at creation | Fixed at 100000000 | Fixed at 100000001 |
| How Created | Created by operations personnel in "Tenant Management" within this console | Provisioned during platform deployment, cannot be deleted | Provisioned during platform deployment |
| Purpose | Hosts business data (configuration items, collection, dashboards, etc.) | Hosts only platform operations functions; stores no business data | Hosts business data; serves as the system-provisioned default business tenant |
| Visible Menus | Full business menus (CMDB, Collection, Monitoring, Users & Permissions, etc.) | Only "Tenant Management" and "Platform User Management" | Same as a regular business tenant |
| User Management | Full functionality (including roles, user groups, email activation) | Simplified functionality (all users have platform administrator privileges) | Full functionality |
| Login Accounts | Created within the business tenant; can only log in to that tenant | Created in "Platform User Management"; can only log in to this console | Same as a regular business tenant |
During initial deployment, the platform automatically creates a default business tenant with a fixed tenant ID of 100000001. It is a business tenant — it has the full set of business menus, can host configuration items / collection / dashboards and other business data, and is functionally identical to any business tenant that operations personnel later create manually in "Tenant Management".
Its only special characteristic is its origin: it is provisioned alongside the platform deployment and its ID is fixed at 100000001. After the initial platform deployment is complete, operations personnel can log in directly using this tenant ID and start configuring and using business features out of the box.
Users created in "Platform User Management" are only for logging in to the Platform Admin Console. If an operations engineer also needs to enter a specific business tenant to troubleshoot an issue, have that business tenant's administrator create a separate account for them within the tenant. Platform accounts cannot cross over into business tenants.
Typical Workflows
Scenario 1: Provision a Business Tenant for a New Customer
- Go to Tenant Management and click Create.
- Fill in the tenant name, description, and designate the first administrator account, email, and initial password for this tenant.
- After successful creation, share the "Access URL" and initial password with the customer.
- The customer uses that URL to log in to their own business tenant and begins configuration and usage.
See Tenant Management — Create a Tenant.
Scenario 2: Suspend an Abnormal Business Tenant
- Go to Tenant Management and locate the target tenant.
- Click the tenant name to enter Tenant Details.
- Click the Stop button. All users of that tenant are immediately unable to log in.
- After the issue is resolved, return to the details page and click Start to resume.
Scenario 3: Create an Account for a New Platform Operations Engineer
- Go to Platform User Management and click Create.
- Fill in the username, full name, and initial password (temporary password is mandatory).
- Deliver the password to the engineer through a secure channel. They will be required to change it on first login.
Best Practices
- Minimize platform accounts: The Platform Admin Console carries the highest privileges. Only create accounts for personnel who genuinely need platform operations responsibilities.
- Prefer suspension over deletion: Use "Stop" for temporary issues first. Only proceed to "Disable + Delete" when the tenant is confirmed to be permanently decommissioned.
- Back up before deleting: Deleting a tenant permanently erases all its data and is irreversible. Confirm whether a backup is needed before proceeding.
- Deliver passwords securely: Initial passwords set during tenant creation and user creation should be delivered through secure offline channels — never sent in plaintext email.