Scope
This guide covers daily operation for Tenant Console & Provisioning. Availability depends on your tenant package, role and configured providers.
Purpose
Create and operate isolated SaaS customer workspaces.
Manage lifecycle, domains, features, branding and configuration.
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.
- Manage lifecycle, domains, features, branding and configuration.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Provision approved tenants from the enquiry workflow.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Review tenant status, seats, usage and operational state.
Verify the result
Review tenant status, seats, usage and operational state. 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
Preserve isolation, audit events and controlled activation. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.