Scope
This guide covers daily operation for Workspace Governance. Availability depends on your tenant package, role and configured providers.
Purpose
Manage people, roles, branding, security, billing and controls.
Maintain users, notifications, providers and marketing controls.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- State the operating objective and the record, audience, campaign or project in scope.
- Maintain users, notifications, providers and marketing controls.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Apply workspace defaults to eligible operational flows.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Review access, usage, security sessions and configuration changes.
Verify the result
Review access, usage, security sessions and configuration changes. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Use explicit roles, approvals and secret boundaries. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.