First things first, let our Support team know by sending an email to support@bridgeapp.com or using the chat inside of Bridge. We can help change billing docs moving forward, as well as your URL and contact info for your admins.
- We have a form from our legal team you’ll need to fill out to officially make the change.
You’ll also want to plan messaging for your learners, and let them know to update any bookmarks. We can change your URL and Account Name on our backend at a date and time of your choosing to coordinate with any mass comms to your learners. Other elements you may want to consider adjusting:
- Intranet
- Sharable and/or saved links
- Custom Support email (if you have that set up)
Here are some reminders if you are using SSO.
Are you changing email domains?
User profiles can be updated en masse via the API. If you are familiar with running API calls, you can do that on your own, or if you need some help, support can assist. To update via the API, it'd be an update on users. You will need the existing user's Bridge ID (column A in the user's exports) and the new UID the users will log in with after the update. If you need assistance from support, having a CSV file of the old and new UIDs (as pictured below) will assist in gathering the required information for these calls to be completed.
You’ll also want to pick an off time to make the change, and of course, coordinate any communications described above with this change.
How do you provision your users?
Turn off Auto CSV until everything is updated. You’ll want to ensure that the provisioning feed’s UID matches the UIDs in Bridge. We recommend stopping Auto CSV, then running the script above and then resuming the feed with the new uids in that provisioning feed. If you do not update your provisioning method, duplicate profiles will be created.
If you’re using Manual provisioning, you’ll want to ensure that the provisioning file has the new UIDs, otherwise duplicate profiles will be created.
WARNING! If you do not follow this part of the directions carefully, you risk creating duplicate profiles. Profiles cannot be merged.
The appropriate process here would be to run the script for the mass UID change, and then run the provisioning file as normal.
What to do if you create duplicate accounts?
Delete the duplicate users via CSV. The duplicates will still be in the database, but they will not be visible to anyone (unless selecting the filter to view inactive accounts). Then, run the update again after making the change to the UID.