Clarify v1-to-v2 connector migration impact on IDs#183
Merged
Conversation
Add a warning that migrating from a v1 to a v2 connector generates new app user IDs and entitlement IDs, which can break existing tasks, access reviews, and access profiles. Remove the misleading option 4b (moving a v2 connector into the original v1 app) since it does not preserve IDs and offers no advantage over using the new app directly.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
mindymo
changed the title
paigealleman-sketch
approved these changes
Apr 7, 2026
OneWhoNests
reviewed
Apr 7, 2026
OneWhoNests
reviewed
Apr 7, 2026
2 Suggestions. We want to add Access review templates as well. Co-authored-by: Nestor Reyes <108298854+OneWhoNests@users.noreply.github.com>
OneWhoNests
approved these changes
Apr 7, 2026
mindymo
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
The previous documentation implied that option 4b (removing the v1 connector from the original app and adding the v2 connector) was a form of in-place migration. In reality, the system generates new internal identifiers regardless of which app the v2 connector is placed in, because IDs are tied to the connector instance. This makes option 4b functionally equivalent to option 4a but more confusing, and users were not warned about the impact on tasks and access profiles.
Fixes: CE-591
Automated PR Notice
This PR was automatically created by c1-dev-bot as a potential documentation update.
This documentation requires: