Background
We often receive requests for a testing environment by clients who are setting up a provisioning integration (SFTP, HRIS, Workday, etc.) for the purpose of verifying that user accounts will be created successfully.
As we currently do not offer a client-facing testing instance, this sometimes raises concern, as clients are unsure whether they can trust that users will be provisioned successfully after the integration is published.
Reasoning
The main reason we don't offer a testing environment is that clients are already able to test the two aspects of account provisioning: 1) transferring the data and 2) creating the account.
The data transfer and the account creation are built as two separate modules on our system.
The account creation module works independently from the data transfer one. This means that the mechanisms that work to create an account on our system will be the same, regardless if the data comes via SFTP, API, or a manual membership file.
So if the client wants to test the account creation, they can simply upload a manual file and see if our system will create an account. If it does - they can be sure we will create the account successfully with another data transfer method as well.
If the client wants to verify the data transfer, i.e. whether their integration is pulling data from their directory - they simply need to go to the Mapping step of the integration setup (this normally comes after the Authorization/Authentication step). If they see their internal fields appearing in the drop-downs, this is a clear indication that the connection is established successfully and the data fields are being pulled through.
If both the data transfer and the account creation modules work separately, they will work together as well.