If your company uses an Identity Provider (IdP) that Drata doesn't support, you can simply export your data from your IdP (on-prem or cloud-hosted) into a CSV file. Make sure the fields are named and formatted to the spec below and upload into Drata.

Now, if anyone has onboarded since your last CSV upload or is no longer with your organization, you'll want to regenerate a new CSV file and upload that to have Drata sync your personnel.

Understand the CSV fields and expected formats

Here is a template to follow, so you can see an example of the headers, and fields.

Ensure that the CSV follows the following table:

Column Name	Field Type	Required	Max Length	Description
id	string	yes	191	Primary ID in the IdP Accepted values: Numbers Alpha strings Alphanumeric string with dashes (GUID/UUID format)
first_name	string	yes	191	First name of user Accepted values: Alphanumeric with special characters (space, ', -, I, ., ,, +, :, _, #, &, /, (, [)
last_name	string	yes	191	Last name of user Accepted values: Alphanumeric with special characters (space, ', -, I, ., ,, +, :, _, #, &, /, (, [)
email	string	yes	191	Email of the user
avatar_url	string	no	768	Full public URL to the user's avatar image
is_contractor	boolean or binary	yes	16	Indicate if user is a contractor Accepted values: 1, 0, yes, no, true, false (case-insensitive)
mfa	boolean or binary	yes	16	Indicate if user enabled MFA for their IdP Accepted values: 1, 0, yes, no, true, false (case-insensitive)
job_title	string	no	191	Job title of the user Accepted values: Alphanumeric with special characters (space, ', -, I, ., ,, +, :, _, #, &, /, (, [)
customer_id	string	no	191	Alternate ID for the user Accepted values: Numbers Alpha strings Alphanumeric string with dashes (GUID/UUID format)
created_at	date	yes	191	Date the user was created in the IdP Accepted values: ISO 8601 (strict or not), American US date format, RFC 3339. Not Accepted values: European date format (day-Month-year), written out long or short date format (Thursday, January, 18th), Epoch Time

The following list showcases the acceptable dates for the created_at column.
- ISO 8601 example: 2019-10-31 09:00:00
- American US Date example: 01/18/2022
- RFC 3339 example: 2022-01-18T15:30:00Z
If the customer_id has a leading zero, Excel might remove the leading zero. Please closely evaluate your values before import.

CSV Upload Issues

If you run into issues when uploading your CSV, an email will be sent out to you with the subject line: [Drata] CSV IdP Upload Issues..." which contains the issues that the CSV file has. Resolve the issues and re-upload the CSV file.

The most common issues are: incorrect file, mislabeled column headers, or field formatting issues (example: email missing @).

Authentication

This data is used to seed your personnel on Drata, the identities of your workforce. To have your personnel authenticate into their "My Drata" page, you'll need to connect your authentication system to our Enterprise Single Sign-On connection.

NOTE: You must have an Identity Provider (IdP) connected to Drata first, before making an SSO connection for sign-in. All Drata logins, including admins, are enforced by and restricted to what syncs from the IdP. If you connect SSO before an IdP, you will be locked out of Drata. In that case, please reach out to our Technical Support team for assistance in restoring account access.

HERE'S HOW

Follow these instructions to upload a manual CSV for your personnel:

Go to the Connections page.
Search for and select connect on Manual import connection.
A drawer will expand from the right side of the screen. Follow the prompts on the drawer. First download the CSV template, add all of your personnel, then upload your CSV and click on the "Save & Test Connection" button.
Your Identity Provider is now set!

To upload a new CSV file to update your personnel on Drata, go back to the connection and select the edit icon.

Troubleshooting

If you run into uploading issues, most likely it's formatting issues in your CSV. You will see an error message like this:

Please reach out to the Customer Success Team with any questions.