Platform Governance and Reporting
About 4% of the CIS-SP exam — see all 6 domains.
- Reporting: report results follow the domain of the user running them, so the same report returns different data per tenant, and a provider user above the customers can aggregate across them. Reports are separated into domains and have an Overrides field; from global, use Expand Domain Scope to see them all.
- Domain Separation Center (All > Domain Admin > Domain Separation Center, or /domaincenter): configure and schedule the built-in audits (inactive by default; daily, weekly, or monthly), run them now, review audits with errors and warnings, and enable detailed domain logging. Avoid daily audits on large tables.
- Domain Log [syslog_domain]: holds domain path recalculation results and audit details. Verbose logging (glide.sys.domain.verbose) plus session debug shows the domains each query was restricted to.
- Customer administration: domain separation is built for the provider to configure services. Customers can safely manage reports, CIs, and users without roles; for that, create custom "customer admin" roles and ACLs. The admin role passes every role check and can change its own domain, so do not give it to tenants. Choice lists and other global parameters stay with the provider's admin team.
- Global parameters common to every domain include system properties, dictionary overrides, field labels (sys_documentation), the data model, ACLs, and inbound actions.
Sample questions from this domain
Three of the 12 in this domain, with the reasoning. The full set is in the question bank.
What is 'delegated administration' in a domain-separated service provider instance?
- A. Setting domain-specific versions of policies, saved as overrides for that domain. ✓
- B. Granting customer admins domain-scoped admin rights so they configure their own tenant.
- C. Using the domain_admin role to let each customer create its own child domains.
- D. Letting a lower domain's admin edit the global policy in place for every domain.
Why: Delegated (process) administration lets administrators set domain-specific policies: when they modify a higher-level client script, policy, or module while in a domain, the system inserts an override for that domain instead of changing the original. It does not mean giving customers domain-scoped admin rights; domain separation is designed for the provider to configure services, with custom customer admin roles only for safe tasks. domain_admin manages all domains and belongs to the provider. Editing the original in place is exactly what the update-into-insert behavior prevents.
A service provider wants each customer's local administrator to manage that customer's users without seeing other customers. The appropriate mechanism is to:
- A. Give each customer admin the admin role, with their user record kept in the customer's own domain.
- B. Create a custom customer admin role and ACLs for user management, granted to users in that customer's domain. ✓
- C. Give each customer admin the domain_admin role so that they can manage the users who belong to their own customer domain.
- D. Grant each customer admin a visibility domain for the provider domain so that they can maintain users.
Why: The base admin roles are built for one admin team per instance, so the provider creates custom customer admin roles and ACLs for tasks such as maintaining users; data separation keeps those users within their own domain. The admin role passes every role check and lets the holder change their own domain, so it is never safe for tenants. domain_admin creates, edits, and deletes domains for the whole instance and belongs to the provider. A visibility domain for the provider domain would expose provider data and grants no user-management rights.
How does reporting across domains work for a provider-level (oversight) user?
- A. Reports run in the domain where the report was created, so a report spans whatever domains its creator could see.
- B. Each report must list its target domains in a filter condition, because report queries are not domain restricted.
- C. A user with broad domain visibility (e.g., in global) can build reports spanning the domains they can see. ✓
- D. Cross-domain reports need the oversight user to Toggle Domain Scope before each run so that child data is included.
Why: An oversight user with broad visibility can report across all the domains they can see, while customer users running the same report see only their own domain. Report data follows the runner's domain, not the creator's. Report queries are domain restricted like every other query, so no manual domain filter is needed. Toggle Domain Scope changes a form's record or session scope; descendant data is already included in reports for users above the customers.