Skip to main content

Phase 4: Consent Management

Organization consents are at organization level (not per-user) and must be accepted by an authorized signatory (CEO or equivalent).

Required Consents

Key Difference from Individual Consents: Organization consents require acceptedBy object with signatory details.

Accept Terms and Conditions

Endpoint: POST /api/v2.1/customer/organization/{organizationId}/consents/termsHeaders:
Request Body:

Accept Privacy Policy

Endpoint: POST /api/v2.1/customer/organization/{organizationId}/consents/privacyRequest Body:

Accept Data Processing Agreement

Endpoint: POST /api/v2.1/customer/organization/{organizationId}/consents/data-processingRequest Body:

AcceptedBy Object

The acceptedBy object captures signatory details for legal compliance:

Authority Types



Director Consents (Optional)

Each director may need to accept individual DATA_PROCESSING consent.
Note: Director consents are currently BYPASSED in activation checks for testing purposes.
Endpoint: POST /api/v2.1/customer/individual/{directorIndividualId}/consents/data-processing

Next Step

After all consents are accepted, proceed to Phase 5: Organization Activation.

Phase 5: Activation

Validate roles and activate organization