Auto CSV is a powerful way to automate user provisioning in Bridge, but it isn’t the right choice for every organization.
This article helps you decide whether Auto CSV is right for you and how to safely move from manual CSV provisioning to Auto CSV.
When Auto CSV Is a Good Fit
Auto CSV works best when:
| Scenario | Why Auto CSV Works Well |
|---|---|
| You have an HRIS or authoritative data source | Bridge can reliably reflect a single source of truth |
| Your user data is automatically generated | Reduces the risk of missing or incorrect users |
| You want fully automated user management | No ongoing manual user updates in Bridge |
| Your organization is comfortable with strict automation | Auto CSV removes manual overrides |
Tip: Auto CSV is most successful for medium to large organizations with stable HR processes.
When Auto CSV May Not Be the Right Choice
Consider sticking with manual CSV uploads if:
| Scenario | Why Auto CSV May Not Fit |
|---|---|
| You frequently add or edit users manually | Manual user management is disabled |
| Your CSV is built manually or inconsistently | Errors can lead to unintended terminations |
| Your user structure is still evolving | Auto CSV enforces strict consistency |
| You only update users occasionally | Manual CSV uploads may be simpler |
Tip: Many customers start with manual CSV uploads and move to auto CSV once their data stabilizes.
Key Considerations Before Enabling Auto CSV
Before moving forward, make sure you understand that:
- Your CSV becomes the master record for users in Bridge
- Any user missing from the CSV will be terminated
- Manual user creation and editing will be disabled
- Correct permissions are required (View Account Config or Manage Account Config)
If any of these are a concern, Auto CSV may not be the right option yet.
Moving from Manual CSV to Auto CSV
If you’re currently managing users via manual CSV uploads, follow these steps to transition safely.
Step 1: Align Your Manual CSV With Your Future Auto CSV
Before enabling Auto CSV:
- Ensure your manual CSV contains all active users
- Confirm UID values exactly match what you intend to use long term
- Remove test users or temporary records
- Ensure required fields are populated consistently
Tip: Your final manual CSV should closely resemble the CSV that Auto CSV will eventually pick up.
Step 2: Review Smart Groups and Enrollments
Auto CSV updates user attributes automatically, which can impact:
- Smart group membership
- Course enrollments
- Program enrollments
Before switching:
- Review smart group rules that depend on CSV attributes
- Confirm attribute naming and formatting is consistent
- Understand that group-based enrollments may change after the first Auto CSV run
Tip: Attribute changes between manual and auto provisioning are one of the most common causes of unexpected enrollment changes.
Step 3: Understand What Happens During the First Auto CSV Sync
When Auto CSV runs for the first time:
- Existing users are matched by UID
- Users missing from the CSV are terminated
- Attribute changes are applied immediately
- Group logic and enrollments are recalculated
Tip: Always confirm your CSV output before the first scheduled run. A test review can prevent large-scale issues.
Step 4: Enable Auto CSV With Bridge Support
Auto CSV requires configuration by Bridge Support or an Implementation Consultant.
You will need to provide:
- SFTP details and credentials
- A live CSV file with a fixed file name
- Confirmation that your CSV is ready to act as the master record
Once enabled, manual user management in the UI will be disabled.
What to Read Next
- Auto CSV and User Provisioning in Bridge: Full setup, permissions, logic, and troubleshooting.
- Auto CSV Requirements and Best Practices: Recommendations for formatting CSV files.
Not Sure Yet?
If you’re still unsure whether auto CSV is right for your organization, contact Bridge Support, your account manager, or join a Bridge Office Hours session hosted by the customer empowerment team to discuss your current setup and goals before proceeding.
Related to
Comments
0 comments
Article is closed for comments.