Skip to main content

Administrators Quick Start

Use this guide to start operating a Cloudaware account as an administrator. It focuses on the minimum sequence needed to secure access, establish governance, connect reliable inventory sources, and prepare Cloudaware modules for the teams that depend on CMDB data.

Before You Start​

Confirm that you have:

  • An active Cloudaware account and administrator access.
  • Authority to manage users, roles, profiles, permission sets, SSO, MFA, and access reviews.
  • Access to configure cloud, billing, security, ITSM, monitoring, and automation integrations.
  • A list of in-scope accounts, subscriptions, projects, tenancies, clusters, vCenter instances, and third-party tools.
  • Named owners for cloud operations, security, compliance, FinOps, and developer platform workflows.
  • Agreement on the first governance standards, such as required tags, access boundaries, integration ownership, and data retention expectations.

Learn The Platform Model​

Start by understanding how Cloudaware is structured and where administration responsibilities sit across Cloudaware and Force.com.

Use:

Secure User Access​

Configure access controls before opening the tenant to a wider audience. Start with a small administrator group, then grant least-privilege access by role, module, object, and operating scope.

Recommended sequence:

  1. Review RBAC to understand Cloudaware access concepts.
  2. Define baseline administrator, operator, security, FinOps, and developer access with Least Privilege.
  3. Configure authentication with SSO & MFA and SSO Configuration.
  4. Use Profiles, Permission Sets, and Scoping to separate duties.
  5. Establish periodic reviews with Audit Access.

Connect Baseline Inventory​

CMDB is the shared inventory layer for Cloudaware modules. Connect the core cloud and infrastructure sources first, then validate that assets, relationships, tags, and ownership metadata are updating.

Start with the providers in scope:

After setup, refer to Integrations, CMDB Ingestion, and CMDB Navigator to confirm that the expected configuration items are present.

Establish CMDB Governance​

Define the minimum CMDB standards that downstream users need before they rely on reports, policies, budgets, or automation.

Focus on:

Track incomplete ownership, stale records, missing relationships, and untagged resources as operational backlog items.

Enable Priority Modules​

Enable modules only after the required CMDB and integration inputs are available. Start with the modules that match the tenant's first operating goals.

Common starting points:

Review each module's requirements before granting broad access or publishing dashboards.

Add Operational Integrations​

Connect the tools that administrators and operating teams use to route work, enrich CMDB context, and notify owners.

Use:

Publish Administrator Views​

Create initial operational views that help administrators identify gaps quickly:

  • Integration status and ingestion freshness.
  • Cloud account, subscription, project, tenancy, and cluster coverage.
  • Missing required tags, owners, applications, or environments.
  • Access review findings and privileged user changes.
  • Module coverage, policy status, open findings, and ticket routing health.

Use CMDB List Views, CMDB Search, Queries & Reporting, and Advanced Analytics guides to build the first views.

Next Steps​