...
Create a csv file with the following parameters:
Extract contains a row per user.
File name: USERS_YYYYMMDDHHMMSS.csv
Daily Load: Extracts new users. (Can be loaded less frequently or manually if required)
Historical Load: Full snapshot of users.
Follows the file format above.
Sample:
View file name USERS_YYYYMMDDHHMMSS.csv
Column | Data Type | Value Mandatory | Description |
---|---|---|---|
USERNAME | STRING | Y | Unique id for the user Typically email of the user especially if SSO with Active Directory is used. Example: Jane.Doe@email.com |
FIRST_NAME | STRING | Y if IS_LOGIN_USER = 'Y' | Example: Jane |
LAST_NAME | STRING | Y if IS_LOGIN_USER = 'Y' | Example: Doe |
STRING | Y if IS_LOGIN_USER = 'Y' | Example: Jane.Doe@email.com | |
DESCRIPTION | STRING | N | Description or Title of the user Example: Head of Data |
IS_SYSTEM_USER | STRING | N | Is the user a human user or a system account ? One of the following values: (Y, N) 'Y' - system account 'N' - human user leave empty if unknown |
IS_LOGIN_USER | STRING | N | Will the user log into KADA ? One of the following values: (Y, N) ‘Y’ - login 'N' - no login Default to 'N' if not provided |
ROLES | STRING | N | Comma separated string of roles. Defaults to “kada_user” if no role is provided Valid values:
This will be overridden by roles managed in SSO if configured |
GROUP_NAME | STRING | N | The group (Team) the user belongs to. Must match a value from GROUP MAPPING interface (see below) |
USER_ID | STRING | N | INTERNAL use only. Leave empty |
...
Create a csv file using AD / LDAP with the following parameters:
Extract contains a row per group.
File name: GROUPS_YYYYMMDDHHMMSS.csv
Daily Load: Extracts new groups. (Can be loaded less frequently or manually if required)
Historical Load: Full snapshot of groups.
Follows the format above.
Sample:
View file name GROUPS_YYYYMMDDHHMMSS.csv
Info |
---|
In this context Groups = Teams |
...