Migrating conversation ownership
Protegrity Agent v1.0 does not track conversation ownership. All users with access to the Agent share a single pool of conversations.
Protegrity Agent 1.2.0 introduces per-user conversation ownership. As a result, conversations are visible only to their respective owners.
Because Agent v1.0 did not record the original creator of each conversation, the migration process cannot restore conversations to their original owners.
To migrate the ownership, select one of the following options:
| Choice | Setting | Result |
|---|---|---|
| Assign all existing Agent 1.0 conversations to a single user | migration.legacyConversationOwner=<username> | All Agent 1.0 conversations are assigned to the specified user. Only that user can view and continue those conversations after the migration. |
| Keep conversations ownerless (default) | Leave migration.legacyConversationOwner unset | Conversation data is preserved; however, it is inaccessible after migration because the Agent 1.2 API does not permit access to ownerless conversations. |
In both migration scenarios, users other than the designated owner lose access to the conversations that were available to them in Protegrity Agent v1.0.
The conversation ownership strategy should be selected before the migration and documented as part of the upgrade plan. After the migration is complete, the ownership assignment cannot be changed through the Protegrity Agent user interface or API. Modifying conversation ownership requires direct updates to the underlying database.
Feedback
Was this page helpful?