Cloudaware Administrators
Cloudaware Administrators are responsible for operating and governing the Cloudaware platform. They combine day‑to‑day configuration and operations in the Cloudaware UI with elements of Salesforce platform administration.
This page summarizes their role, responsibilities, and the kinds of permissions they typically require.
Role & Responsibilities
Cloudaware administrators typically own:
- User and access management – controlling who can see and change what (RBAC, profiles, roles, MFA, SSO).
- Cloud and third‑party integrations – onboarding and maintaining cloud accounts, billing sources, Breeze Agent, monitoring, ticketing, and security tools.
- CMDB governance – data quality, tagging conventions, enrichment rules, and lifecycle controls.
- Module configuration – enabling and tuning modules such as Cost Management, Compliance Engine, Vulnerability Management, Patch Management, Backup & Replication.
- Operational observability – monitoring ingestion health, change tracking, backup coverage, and security posture across the estate.
Permissions & Access Model
Cloudaware runs on Force.com and uses its administration model. In most deployments, a Cloudaware Administrator (or Cloudaware System Administrator as an equivalent profile for some accounts) has permissions to:
- Access Setup to manage users, apps, company profile, security controls, domains, and data management.
- Access App Setup to configure automation, Analytics Studio and other connected apps.
- Use Personal Setup/My Settings for their own account and assist users with configuration where policies allow.
Within the Cloudaware UI, administrators have access to:
- Integration management (cloud accounts, billing sources, Breeze Agent, and other connectors).
- CMDB configuration (ingestion, customization, and change tracking settings).
- Module administration views (Compliance Engine, Backup & Replication, Vulnerability Management, Patch Management, Cost Management, etc.).
Organizations typically restrict these permissions to a small group of trusted administrators and apply least‑privilege principles using roles, profiles, permission sets, and SSO/MFA policies.
CMDB‑Focused Responsibilities
For CMDB usage specifically, administrators typically focus on:
- Integrations and ingestion – onboarding and maintaining cloud accounts, Breeze, and third‑party tools so CMDB has complete, fresh data.
- Customization – defining custom objects, calculated attributes, and enrichment rules so the CMDB data model aligns with business concepts.
- Change tracking – enabling and tuning change tracking policies, notifications, and retention for critical configuration items.
- Tagging standards – establishing and enforcing tag schemas (
Owner,Application,Environment,Cost Center, etc.) that drive scopes, reports, and automation. - Access controls – ensuring CMDB object and field‑level access matches team responsibilities and compliance requirements.
See also:
Typical Admin Workflows
Common workflows for Cloudaware administrators include:
- Onboarding a new cloud account or integration
- Add the account or connector in the Admin (Admin Console).
- Verify ingestion health and that configuration items appear in CMDB Navigator.
- Use Tag Analyzer to confirm that tags and ownership metadata are being collected correctly.
- Rolling out a tagging or ownership standard
- Define required tags and mapping rules.
- Use CMDB Search, list views, and queries to find non‑compliant CIs.
- Apply enrichment rules and automation to normalize tags over time.
- Enabling a new module
- Deploy Compliance Engine policies or backup policies using module admin views.
- Use CMDB scopes to target the right CIs.
- Monitor findings, coverage, and history via module‑specific tabs on CI pages.
- Hardening access and security
- Configure SSO/MFA and IP restrictions where appropriate.
- Review roles/profiles and CMDB object access for least privilege.
- Coordinate with security teams to align Cloudaware controls with broader identity and network policies.