If you previously used a custom API integration for user provisioning, you need to update your CSV script files to align with the updated API provisioning format. This update ensures that your API provisioning syncs remain successful and that new users and teams are updated as expected.
Note: The API remains backward compatible with legacy API files. However, updating ensures optimal performance and access to new features.
Update your legacy API files for API provisioning
Use the tables below to convert your existing files and column headers to the current API provisioning format:
users.csv
Legacy File | New File |
users.csv | members.csv |
Legacy Column Name | New Column Name | Notes |
id | externalMemberId |
|
language | languagePreferences | Use language codes (e.g., fr, en) |
| productAssignations | New column; defaults to Officevibe if no product is specified |
groups.csv
Legacy File | New File |
groups.csv | teams.csv |
Legacy Column Name | New Column Name |
id | externalTeamId |
name | teamName |
groups-mapping.csv
Legacy File | New File |
groups-mapping.csv | teams-mappings.csv |
Legacy Column Name | New Column Name |
groupId | externalTeamId |
userId | externalMemberId |
subGroupId | externalSubteamId |
After you update your files
Generate a new API key.
Set your risk thresholds.