Directory Applications
| Info |
|---|
The first step to configuring your Zilla Security tenant is to set up a directory application that will serve as a source of truth for user details. Some customers may wish to use a CSV data export from an HRIS or |
...
ERP system. |
The CSV file a customer uses for a directory import must include the following attributes;
Unique ID - This must be an attribute that is guaranteed to be unique for each user. Common UID examples include but are not limited to; Employee ID, sAMAccountName, Account ID, or email address.
First Name
Last Name
Email Address
...
Non-directory Applications
| Info |
|---|
Applications that will not serve as a directory in Zilla have fewer mandatory fields. Any data that is not mapped directly to a Zilla attribute will be imported as account metadata. |
The csv file a customer uses for an app import must include the following attributes;
Unique Account ID - This must be an attribute that is guaranteed to be unique for each account in the application. Common UID examples include but are not limited to; Employee ID, sAMAccountName, Account ID, or email address.
In addition to the above, including the following attributes in an application CSV file is recommended but not required;
Permissions - Include whichever attributes might be interpreted as a “permission” in the application. Examples include Groups, Roles, Entitlements, User Type etc.
In addition to the above, including the following attributes in an application CSV file is highly recommended;
First Name
Last Name
Email Address
Account Status -If not provided, all included accounts will be assumed to be active.
Last Login