ProductsProduct Surface
Governance
Governance groups the support surfaces behind the shared workspace.
Best fit: Administrators, managers, and technical operators
Company context
Keep company identity stable before you move into contacts, outreach, or relationship work.
Relationship visibility
See how people, teams, and structure connect so decisions are made with better context.
Shared control
Keep team access and platform oversight available without overwhelming the product story.
Why this surface matters
Shared systems lose trust when permissions and platform behavior are unclear.
Managers and admins need to see how the product stays reliable, not just how it looks.
Control surfaces matter, but they should support the main workflow rather than become the whole story.
How Governance fits into the workflow
1
Define access
Control which users can see or operate different parts of the workspace.
2
Monitor runtime behavior
Use scheduler, API usage, and health views to understand whether the operational environment is behaving as expected.
3
Preserve confidence during change
Keep administrative oversight clear and dependable as teams expand their use of the platform.
Why this surface works
Role-based control helps teams keep sensitive responsibilities separated appropriately.
Health, usage, and oversight views support reliable day-to-day operations.
That control layer helps teams trust the platform as usage grows.
Inspect the control layer
Open Administration to review access, usage, and system status.