Scope
This guide covers setup & configuration for Tenant Console & Provisioning. Availability depends on your tenant package, role and configured providers.
Purpose
Create and operate isolated SaaS customer workspaces.
Qualify enquiry and define tenant owner, plan, region and limits.
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
- Open the correct tenant and confirm the project or workspace that owns this capability.
- Qualify enquiry and define tenant owner, plan, region and limits.
- Connect or select the required source records and owners.
- Create a safe test configuration before using live customer or campaign data.
- Review tenant status, seats, usage and operational state.
- Preserve isolation, audit events and controlled activation.
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.