The integration administrator role enables you to manage Anaplan Data Orchestrator and CloudWorks.

Only tenant administrators can assign the integration administrator role. Before users can be assigned the integration administration role, they must be a workspace administrator for a model in the tenant.

Note: Tenant administrators can only assign the integration administrator role to internal users within their default tenant. They can only assign this role from the Users > Internal page.

Integration administrators can manage capabilities for Data Orchestrator and CloudWorks.

If your tenant is entitled to Data Orchestrator, integration administrators can access and manage data integrations in Data Orchestrator.

They can only access data within their assigned dataspaces. Tenant administrators can assign dataspaces to integration administrators.

In Data Orchestrator, integration administrators can manage:

  • Connections
  • Source data
  • Transformations
  • Model links

In CloudWorks, integration administrators can manage:

  • Connections
  • Integrations
  • Integration notifications
  • Integration flows and schedules

The integration administrator and the restricted integration user have similar access and permissions, but there are differences:

  • Both integration administrators and restricted integration users have access to CloudWorks. However, restricted integration users are confined to assigned workspaces. 
  • The roles have different CloudWorks permissions for connections and integrations. This depends on who made the initial connection and integration.

Note: Integration administrators have access to‌ large amounts of data. For example, an Integration administrator can move data from one model to another across workspaces via CloudWorks. 

Consider your company's data privacy rules when you assign the integration administrator role.

The table below displays the resources that ‌integration administrators can control. 

A checkmark indicates that this administrator can create, read, update, or delete the resource. A cross (X) indicates that this action isn't available.

Resource TypeCREATEREADUPDATEDELETE
Tenant

false

true

false

false

Transactional API

true

true

true

true

Cloud connection

true

true

true

true

Integrations

true

true

true

true

Role membership

true

true

false

true

Role

false

true

false

false

Datasets

true

true

true

true

Dataspace

true

true

true

true