Scope
This guide covers daily operation for AI Studio: Module Builder. Availability depends on your tenant package, role and configured providers.
Purpose
Create reusable structured modules, fields and pages.
Build and maintain reusable structured content components.
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.
- Build and maintain reusable structured content components.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Insert modules into eligible studio and page workflows.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Review module use, errors and lifecycle state.
Verify the result
Review module use, errors and lifecycle 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
Restrict schema changes and preserve compatibility. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.