Scope
This guide covers daily operation for Projects & Brand Workspaces. Availability depends on your tenant package, role and configured providers.
Purpose
Organise brands, domains, knowledge and marketing work.
Keep campaigns, sources, knowledge and tasks in project scope.
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.
- Keep campaigns, sources, knowledge and tasks in project scope.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Route project events into relevant workflows and agents.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Review project-level activity, delivery and outcomes.
Verify the result
Review project-level activity, delivery and outcomes. 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
Separate access, credentials and brand assets by project. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.