Workspaces and roles
Isolation per client, brand or market; role separation, SSO and audit depending on availability.
Integrations · Architecture
A governed architecture, from source to destination.
Your sources enter an isolated workspace. Roles, keys, scopes, webhooks and logs frame every process, through to enabled destinations. The Enterprise API is offered on quotation, with scopes, limits and support defined in the contract.
Last verified · 26 September 2026
SourcesIsolated workspaceApprovalEnabled destinationsLog
How does Aive fit into an enterprise architecture?
Aive receives your sources, whether videos, CMSs, catalogues or analytics, in an isolated workspace. Access runs through roles, API keys and scopes; events are notified by webhooks and every action is logged. Approved content goes to enabled destinations. The Enterprise API is offered on quotation; the published OpenAPI 3.1.0 specification documents 48 endpoints.
- Isolated workspace
- A space dedicated to one client, brand or market, with its own data, roles and destinations.
- Scope
- The set of actions an API key is authorised to perform.
- Webhook
- A notification Aive sends to your system when an event occurs.
Overview
Sources, Aive, destinations.
01Sources
- Videos, channels and media libraries
- CMSs and content bases
- Product catalogues and PIMs
- Analytics and first-party events
02Aive
- Isolated workspaces per client or brand
- Roles, API keys and scopes
- Human approval and versions
- Webhooks and timestamped logs
03Destinations
- Enabled CMSs and sites
- Player and Media Factory experiences
- Exports to your data warehouses
- Analytics and BI tools
Control building blocks
Four building blocks, one status each.
API keys and scopes
Every key carries scopes and limits defined in the contract.
See the API
Webhooks and logs
Event notifications to your systems and a timestamped record of every action.
See webhooks
Authorised sandbox
An environment to assess the architecture before any deployment, on request.
Security and contract
Secured, controlled, contracted.
Security
- SOC 2 Type II report published: scope on the Trust Center
- GDPR framework; DPA and contract define processing
- ISO 27001 process under way
- TLS 1.2+ in transit and encryption at rest, as described by Aive
Controls
- Need-to-know access for authorised staff
- Customer data never used to train models
- Retention, deletion, revocation and export
- Action log per workspace
Prerequisites and availability
- Enterprise API on quotation
- Scopes, limits and support defined in the contract
- Connectors validated one by one
- Authorised sandbox depending on scoping
What the architecture does not assume
- API access falls under the Enterprise offer on quotation, with scopes, limits and support defined in the contract.
- No public SLA: availability, support and SLAs are contractual.
- No connector is enabled by default: every destination is tested and authorised.
- EU/EEA processing prioritised for core services; governed transfers possible under policy and contract.
Frequently asked questions
Is API access part of the subscription?
The API falls under the Enterprise offer on quotation, with scopes, limits and support defined in the contract. The public documentation, in OpenAPI 3.1.0 format, is available at api.aive.tech.
Can we test before committing?
An authorised sandbox can be opened as part of an architecture assessment, depending on scoping. Its scope is defined with the Aive team.
How is data from several brands kept apart?
Each client, brand or market can have an isolated workspace, with its own data, roles and destinations. Isolation, SSO and audit are specified depending on availability and contract.
Where can I find security documents?
The Aive Trust Center sets out the published SOC 2 Type II report and its scope, the GDPR framework and the ISO 27001 process under way. Security and procurement questionnaires go through the dedicated form.
Let’s talk about your architecture.
Sources, destinations, security and contract, scoped with the Aive team.