...
| Note |
|---|
The destination connection must be made with an account that has administrative privileges. |
File Format
The import source can be any delimited file or a database table. The import source needs to contain 2 types of information for each row in the file: the file path and the associated permissions.
...
Below is an example of exported report. The import only reads the five columns identified in the table below. Just edit the information for these columns as needed. All other columns are skipped regardless of the information in the columns.
Example Transfer Level Permissions Export
...
Column | Description | Notes |
|---|---|---|
source_name | This column identifies the user or group to whom permissions are being applied. | |
rights | This column identifies the access rights for a given item. | Valid values are read, write, append, delete, read_permissions, write_permissions, read_write, and full. |
access_control | This column indicates if access should be granted or denied. | Valid “allow” values are 1, true, and allow. (Allow is the default value.) Valid deny values are 0, false, and deny. |
audit_trail | This column is used to determine if the record should be skipped when applying permissions of if it should be included. | If there is a value in this field, the record will be skipped when applying permissions, and no permissions will be applied. If this column is empty, the indicated permissions will be applied. It is important that this column be empty for all records that need to have permissions applied. |
platform_path | This column identifies the transfer item’s source path defined in the job. |
...
Specify a permissions policy of
nonefor simple scenarios. See Permissions | Permissions Preservation.Create and utilize an account map with the option
map_by:passthroughfor simple scenarios (File Share or NFS; both sides only). See Permissions | Account Map / Group Map.When using the REST API to create a Job with permissions import, it is advisable to utilize the JSON configuration path
transfer.permissions.import.source.text.target.path.
...