Account and folder scoping
- Last UpdatedJul 30, 2026
- 3 minute read
- Engineering
- Integration Service 4.1
- Integrators
AVEVA Integration Service (AIS) is scoped within the AVEVA CONNECT platform — both at the Account level and at the Folder (previously called Asset) level.
|
Level |
Description |
|---|---|
|
Account |
The top-level organisational entity in CONNECT. Every customer has at least one Account. An Account maps to the organisation or project at the highest level. Services subscribed at Account scope are available across all Folders within that Account. |
|
Folder (Asset) |
A sub-division within an Account, formerly known as an Asset. Each Account automatically has at least one Folder whose name matches the Account name. Administrators can create additional Folders to represent projects, plants, or departments. AIS solutions enabled at Folder scope apply only to users and resources within that specific Folder. |
CONNECT account structure
CONNECT Account: ACME Corporation
├── Folder: ACME Corporation (default, same name as account)
├── Folder: Refinery Project Alpha
├── Folder: Offshore Platform Beta
└── Folder: ERM Central Hub
AIS scoping modes
AVEVA Integration Service supports two scoping modes when being enabled on CONNECT. The administrator selects the appropriate mode based on the integration architecture and data-flow requirements.
Account level scoping
When AIS is subscribed and enabled at the Account level, the service is available across all Folders within that Account. Permissions granted are applied account wide.
Important: If a customer wants to publish data from E3D (enabled at Folder level or Account level) to ERM (enabled at Account level), AIS MUST be enabled at the Account level — not just at individual Folder level. Enabling AIS only at a Folder level will prevent cross-scope data publishing to Account-scoped applications such as ERM.
Folder level scoping
When AIS is enabled at the Folder level, the service instance is tied to a specific Folder. Users and permissions are scoped to that Folder only.
Note: Folder-Level scoping does NOT support direct data publishing to applications that are scoped at Account level (e.g., ERM at Account level). If cross-scope integration is required, upgrade to Account-Level scoping.
Integration flow
The following services are enabled once at the Account level and are shared across all folders within the account:
|
Service |
Level |
Description |
|---|---|---|
|
AIS CONNECT (SaaS) |
Account |
AIS API, Data Channels, Data Sources |
|
ERM (SaaS) |
Account |
ERM APIs and ERM Integration |
Note: Because these are Account-level services, any folder within the account can interact with them, no per-folder enablement required.
Integration Flow
-
UE Browser Access enabled in AIS40 and UEOV1 integrates with the Account-level AIS CONNECT (SaaS) using a Service Access Token.
-
Both UE Gateway requests and ERM Integrations flow up to the Account-level AIS CONNECT service.
-
Data Source Admin must be assigned for the integration to succeed. Requests without the correct role are rejected with an Unauthorised error.
Important : If you need to publish data from applications like UE or ERM across multiple folders to AIS CONNECT, AIS must be enabled at the Account level and not at each individual folder level.