Effective AI governance relies on a combination of organizational, technical, and data-focused controls embedded throughout the entire AI lifecycle. With Creative Force at the helm, studios have full control and total visibility over the entire product life cycle and how it interacts with AI throughout.
Introduction
AI Governance allows studios to access, review, and approve AI Vendors and models from a central location. Creative Force's approach to AI Governance is built around three core pillars: Clarity, Control, and Continuity.
Pillar | Solution | Function |
Clarity | AI Native Solutions | Review all AI-powered features and understand what models are involved in their functionality. |
Control | AI Models & Functions | Access, review, and approve third parties for use in a central location |
Continuinty | Audit Log & Report | View a detailed audit log of events related to AI Governance, and generate reports for compliance. |
⚙️ Permissions: To open any AI Governance screen, the role must have the AI Governance permission set to View or Edit. View shows the screens read-only, while Edit permissions allow changes.
Required Agreements
Part of the 'Control' aspect of AI Governance is that some AI-related functionality requires internal acknowledgement before the related functionality becomes available for use.
|
|
Native Solutions | All require agreement to relevant AI vendor(s) and model(s) for use. |
AI Connectors | Subfunctions of the Creative Force AI connector require agreement to relevant AI vendor(s) and model(s) for use. All other AI Connectors do not require agreement because customers must agree to the vendor’s terms and conditions in order to get the credentials needed to enable the connector. |
⚠️ Implementation Grace Period: Customers using Native Solutions and AI Connectors prior to October 6, 2026 have until November 3, 2026 to agree to the relevant AI vendor(s) and model(s). After this date, the AI features powered by AI vendor(s) and model(s) that have not yet been approved will not work until the relevant approvals have been made.
AI Native Solutions
In the AI Native Solutions tab, all available native solutions along with key information, version review, and a toggle to enable or disable. AI Native Solutions is a section inside Integrations & AI. To access it, head to Studio Settings → Integrations & AI → Native Solutions.
Layout/Navigation
The page is broken up into sections by feature. Each feature card shows its active version, a Feature enable toggle, and other details.
Section | Description |
Feature | The name of the Native Feature and a short description. |
Version Selection | Select and enable the version(s) of Native Solutions you’d like available for use in Creative Force. |
Enable/Disable | Toggle On/Off Controls whether the selected model and version are approved for use within Creative Force. |
Models | Shows a row for each AI Model related to the selected feature & version.
|
⚠️ Important: In order for a Native Solution to be enabled, the related AI Models must first be approved under AI Models & Functions.
AI Models & Functions
The AI Models & Functions tab details AI models and vendor functions in use across Native Solutions and Connectors, with their vendor, inference location, and acceptance status. AI Models & Functions is a nested subsection inside AI Governance. To access it, head to Studio Settings → AI Governance → AI Models & Functions.
Layout/Navigation
Filtering and search options along the top allow you to search and review entries based on their value.
For the generated results, the tab will be broken down into sections by Model, all of which we have outlined in the table below:
Section |
|
Model | Lists which vendor and individual model the section relates to.
|
Model Approval | Shows the current governance approval status for the Model.
|
Category | Shows the primary AI Model Category.
|
Inference Location | Lists the currently set preference for instance location. If there are no configurable locations, it will be blank.
|
Used In | Lists all Native Solutions and AI Connectors that the AI Model is associated with.
|
Documents | Provides a link to external documentation for the specific Model.
|
AI Model Category
Category | Description |
Multimodal | AI models that can process and understand multiple types of input simultaneously, such as text, images, and video. Generally, they can receive a mix of inputs and generate responses based on the combined context. |
Vision | AI models focused on understanding and analyzing images or video frames. This would cover capabilities like image recognition or object detection. Primarily focused on interpreting rather than generating. |
Video Generation | AI models that generate video content from prompts, images, or other inputs. Generally, these are tools that produce short video clips based on text descriptions or reference media. |
Image Generation | AI models that are specifcially trained to generate images from text prompts or other inputs. |
Post Production | AI models that modify or transform existing images, rather than generating from scratch. This includes background removal, expanding canvas, sharpen / upscale, and more. |
Review & Accept
To accept the use of a model and its subprocessors, you must first review its detail card and accept by toggling and saving.
Menu Subtab | Overview |
Subproccesor | Shows the sub-processor agreements and the authorization consent checkbox.
Consent is recorded by user and timestamp, and can be revoked later. |
AI Models | Approve or reject individual AI models offered by each vendor.
|
Locations | Set instance location preferences per vendor, and order them by priority (if applicable).
⚠️ Location controls are not available for all models. |
Terms of Service | Review Creative Force’s terms and conditions for using the AI vendor. |
Approval Status
The status listed under the Model Approval section will appear here and varies depending on the steps taken so far in the approval process.
Status | Description |
Vendor Pending | Appears when the sub-processor has not been approved, or after approval was manually revoked. |
Pending | Appears once a sub-processor has been approved, but before specific AI Models have been approved. |
Approved | Appears once both the sub-processor and models are approved. |
Auto-Approved | Appears once both the sub-processor has been approved, and AI Models have been approved via the 'Auto-Approve' toggle setting. |
Included | When a model’s Category is AI Function, it will show as included. The studio approves it automatically the moment it accepts the vendor’s Sub-Processor terms, and it cannot be un-approved individually. |
Revoking Approval
Approval can be revoked manually at any time once approval has taken place. In the 'view details' menu, scroll to the bottom and select 'Revoke Sub-Processor Acceptance,' confirm the details via the pop-up dialogue, then hit 'Revoke & Save' to apply the revocation.
⚠️ Important: Revoking a vendor blocks all new tasks using that vendor's models. Tasks that are currently in progress are not interrupted.
Document Reference
The following table contains a reference for the types of documents that may commonly be linked to within the details menus for review and acknowledgement.
Document Type | Description |
Terms of Service (ToS) | Details the ongoing service relationship between the provider and the user. Sometimes covers broader topics like SLAs, billing, account management, and liability. |
→ Vendor ToS | Linked to from the sub-processor lists. |
→ Creative Force ToS | Shown in the view details menu.
|
Privacy Policy | A public-facing document describing how a company collects, uses, and shares personal data– broader in scope than the ToS, and typically what links out to the Subprocessor List. |
Subprocessor List | Companies typically maintain a public Subprocessor List, often as part of their Privacy Policy, to stay transparent and compliant with privacy regulations. A subprocessor is essentially any vendor behind the vendor that may interact with data.
|
Data Processing Agreement (DPA) | A legally binding contract (often an addendum to the ToS) that governs how a vendor processes personal data on a customer's behalf, specifying obligations around data protection, breach notification, and use of subprocessors– typically required for GDPR/CCPA compliance. |
Audit Log
In the Audit Log, you will find a single source of truth outlining all events related to changes in AI behavior within Creative Force.
The Audit Log is a nested subsection inside AI Governance. To access it, head to Studio Settings → AI Governance → Audit Log.
Layout/Navigation
Filtering and search options along the top allow you to search and review entries based on their value. For the generated results, the log will be broken down into sections, which we have outlined in the table below:
Column | Description |
User | The user who performed the action related to the specific entry. |
Role | The role assigned to the user related to the specific entry. |
Date & Time | The exact date and time the event occurred. |
Event | The specific operation, action, or event that was triggered. |
Entity | What was acted upon - the object, record, or resource that the action was performed on. |
Details | Additional context about the action and highlighting what changed. |
⚠️ Important: All governance actions are audit-logged with 12-month retention. The log is immutable, meaning you cannot otherwise edit or delete entries.
Report
In the Report section, you will find a generated report that provides a singular overview of information relevant to AI Governance in Creative Force. Report is a nested subsection inside AI Governance. To access it, head to Studio Settings → AI Governance → Report.
📝 Note: The information in the report is a snapshot generated at the time the page is loaded.
Layout/Navigation
Section | Overview |
Select the button anchored top-right to export the entire report through the browser’s print dialog as a single multi-page PDF. This allows studios to easily generate and hand off a document for internal compliance or external auditors. | |
Overview | At the top of the AI Governance Report, you will find three counter cards, showing the total number of related vendors, solutions, and connectors, and the number of them that are currently enabled.
|
Vendor Compliance | A list of vendors/sub-processors, along with their acceptance status, who approved, and other governance details. |
Native Solutions | A snapshot of the information shown in Native Solutions, including feature status, active version, and required vendors. |
Connectors | A summary of connectors that utilize AI functionality, including their enablement status, payment type, and related sub-function statuses. |
Model Inventory | An inventory of all AI Models, grouped by vendor, with references to the solutions they are used in. |
Recent Activity | A selection of the most recent governance activity from the Audit Log. |












