Internal (Full Access) is an alias account for CloudWorks. CloudWorks uses permissions from this alias to perform actions in a model and run integrations.

Assign Selective Access read access for the Internal (Full Access) alias account when the source object of an action (import, export, or process) references a list with Selective Access enabled.

Integration administrations can run CloudWorks integrations that reference the Selective Access list if the Internal (Full Access) alias account is assigned read access.

If Internal (Full Access) isn't assigned read access, Selective Access restricts access to a list.

Without the proper Selective Access permissions:

  • Model-to-model imports won't reflect the latest data.
  • Exports will download an empty file.

Note: Restricted integration users don't use permissions from the Internal (Full Access) alias.

Workspace administrators can assign the Internal (Full Access) alias account with read access to a list with Selective Access enabled.

Internal (Full Access) only appears as a user in models that are tied to a CloudWorks integration.

To assign Internal (Full Access):

  1. Create a CloudWorks integration with the model.
  2. Open the model.
  3. Select General lists .
  4. Select the list with Selective Access enabled and select Open.
  5. Select the Grid View tab.
  6. From the Read column, select the ellipsis for either the top level of the list, or for specific list items for which you need to provide access. 
  7. Select Internal (Full Access) from the list of users and select OK.

With respect to Dynamic Cell Access, the Internal (Full Access) alias account is generally treated the same as a workspace administrator:

  • When Dynamic Cell Access is applied to a line item in the target model, an import into that line item ignores any Dynamic Cell Access restrictions.
  • When Dynamic Cell Access is applied to a line item in the source model, Dynamic Cell Access restrictions are followed:
    • Only data that is readable in the source is included in the source data and imported to the target.
    • Note that if Dynamic Cell Access is configured to use the Users list as part of the access driver, it isn't possible to assign the Internal (Full Access) alias account permissions to the access driver.