Skip to main content
Adding branches and account creation events requires a coordinated activation. The CRM team prepares the data, registers its receiver through the API, and validates delivery; ExuraCopy Support coordinates the migration of existing branch assignments.

​
Information the CRM must provide

​
Activation order

1

Synchronize branches

First register the CRM catalog through POST /api/v1/branches/sync. Repeat the operation whenever a branch name or UUID changes.
2

Request the migration of existing users

Ask ExuraCopy Support to assign every existing integrated user to the appropriate branch. The CRM must not attempt this migration through bulk SSO requests.
3

Validate a sample

Test new and existing users from different branches. Confirm that they can see the correct products and operate within their branch.
4

Start sending branch_id

Once the migration is confirmed, always include the external branch ID in POST /api/v1/sso/start.
5

Activate the webhook

Register the receiver with POST /api/v1/integrations/crm/account-webhook, store the one-time signing secret, and complete a social.account.created test before production.
Do not enable branch rules until ExuraCopy Support confirms the migration. A user without a valid assignment may be unable to see products or subscribe to a master.

​
Future branch changes

When a branch name or UUID changes, synchronize it again while preserving the same id. If a user moves to another branch, coordinate the operational impact with ExuraCopy before sending the new assignment in the next SSO request.

Previous: Responsibilities

Review what each system manages.

Next: Authentication

Prepare the backend credentials.
Last modified on November 3, 2026