> ## Documentation Index
> Fetch the complete documentation index at: https://crm-social.exuratech.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Activation with ExuraCopy

> Coordinate branches, existing users, and webhooks before enabling the production integration.

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

| Item | What to provide |
| - | - |
| Branch catalog | Stable ID, name, and, when available, UUID for each CRM branch. |
| Existing users | Confirmation of the field that associates each user with a branch. |
| Webhook | Public HTTPS URL and secret storage for account creation events. |
| Technical contact | Person responsible for validating signatures, retries, and end-to-end tests. |

## 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.

> [!WARNING]
>
> 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.

> [card] [Previous: Responsibilities](https://crm-social.exuratech.com/getting-started/responsibilities.md)
>
> Review what each system manages.

> [card] [Next: Authentication](https://crm-social.exuratech.com/getting-started/authentication.md)
>
> Prepare the backend credentials.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.