External integrations administration

Prerequisites and authority

Use an individual staff account with the action permission and required organization module/license. Viewing a menu does not establish permission to mutate records.

Configure external integrations

Use External Integrations and the relevant Settings area for only the providers actually supported by the installed release. Payment providers, institutional synchronization, Telegram and SMTP serve different purposes; do not reuse one provider's credentials or callback rules for another.

1. Confirm the module and required permissions.
2. Identify the intended provider, environment and direction of data flow.
3. Enter credentials through the protected configuration form.
4. Set scope, endpoints and synchronization options as supported.
5. Test one small authorized workflow.
6. Inspect operation/delivery records and resulting customer data.

A connection test proves connectivity, not the correctness of every import or synchronization rule. Check duplicate handling, retries and source identifiers before a full production run.

Rotate credentials through a planned change and test again. Avoid exposing secrets in URLs, screenshots or exported configuration. Retain enough configuration in the recovery record to restore connectivity without storing all secrets in a shared document.

Configure supported payment providers and webhooks is authoritative for payment setup. Telegram customer onboarding and commands covers Telegram onboarding, and Notifications or email not delivered covers delivery failures. Unsupported future connectors remain outside the current guide.

Related guides

Related guides: Staff accounts, roles and permissions, Administrative session and audit investigation, System operations and task controls, Roles and permission matrix.