1. Import and export data
  2. Import Data into Models
  3. Import data from another model
  4. Access constraints in model-to-model imports

When you import from one model to another, you may have different access rights in the source and target models. The type of data you want to import, and whether you’re a workspace administrator, determines whether your access rights limit the import.

Module and Saved View data imports

For both workspace administrators and non-workspace-administrators, your model access rights apply to the source model when you import data from a module or saved view. This means you can only import data to which you have access from the source.

In the target model, if you're a workspace administrator, the import ignores any Selective Access and Dynamic Cell Access restrictions. Any restrictions on your model role still apply. If you’re a non-workspace-administrator, any restrictions on your user access rights in that model constrain which parts of the model you can import module data into. The same is true for saved views.

List data

If you're a non-workspace-administrator and you import data from a list, your selective read access rights apply to the source. 

If you’re a workspace administrator, and you import data from a list in the source to a list in the target, the import ignores any restrictions on your read access. The whole list imports. It's better to import into a list from a module or saved view, so you have more control over which data imports. When you import from a module or saved view the import respects any Selective Access restrictions that apply to the module. You can also filter a view to ensure that only the data you want to import into the target exports from the source.

In the target module the import only respects selective read access rights for non-workspace-administrators. Workspace administrators can import data into any list to which they could give themselves access.

Note that you do not need selective write access to import into lists.