Manage connections
Sign in to the dashboard, select your tenant, and open Connections. Each saved connection belongs to that tenant. Several Slack workspaces, Discord servers, and Gauzy pairings can coexist.
Members with the board role can add, edit, verify, enable, and disable connections. Other members can view them. The server rechecks authorization on each operation. The tenant menu also offers Create tenant when the session provider supports it. Creating a tenant switches you into it with the board role; your existing memberships remain available.
Switching tenants reloads the current view and discards unsaved connection forms. Connection credentials are password fields; saved values never return to the dashboard. Editing a saved connection starts with blank credential fields. Leave them blank to keep the existing values.
Add a Slack workspace
- Create and install your Slack app using Slack setup.
- In Connections choose Add Slack. Enter a connection name, the app's Bot token, and Signing secret.
- Choose Save connection. Async verifies the bot identity and saves the authoritative Verified workspace ID. The connection starts disabled.
- Copy the card's Events URL, Commands URL, and Interactivity URL into the corresponding Slack app settings. Use the URLs shown on this card; each connection has its own identifier.
- Subscribe to the message events your app needs, invite the bot to those channels, and choose Enable in Async.
The callback paths are:
/ingress/connections/<connection-id>/events
/ingress/connections/<connection-id>/commands
/ingress/connections/<connection-id>/interactions
Repeat Add Slack for another workspace. Each record has its own credentials and verified identity. Copy the verified workspace ID when configuring Gauzy employee mappings; it is the Slack team ID, not a channel ID.
For workspaces installed from the same Slack application, use one saved connection's callback URLs in that application. Signed callbacks route to the matching enabled workspace connection, which has its own bot token. Disabling the connection whose URLs you copied stops its workspace; the same URLs still serve other enabled workspaces from that application.
Add a Discord server
Choose Add Discord. Enter a name, the Discord server ID, the application's 64-character public key, and its Bot token. Install the bot in that server before saving. Async verifies the application identity and server access.
Copy the card's Interactions URL into your Discord application's setup,
then enable the connection. It ends in
/ingress/connections/<connection-id>/interactions.
For ordinary channel messages, enable Message Content Intent in the Discord Developer Portal. Verified applications in 100 or more servers require Discord's privileged-intent approval. Give the bot View Channels, Send Messages, Send Messages in Threads, and Read Message History permissions.
Saving or enabling a connection verifies and stores the application's intent setting. The card shows Message Content Intent configured when available; enabling that connection starts its channel-message receiver automatically. Otherwise it shows Interactions only. After changing the setting in Discord, use Edit → Save connection or Enable to update the saved capabilities. Verify connection only tests the saved credentials and does not update them. Recipients must allow bot DMs to receive private nudges.
One saved connection's interactions URL can serve the same Discord application's other saved servers. Signed callbacks route to the matching enabled server connection. The Verified server ID is the guild ID to use in a Gauzy mapping.
Pair a Gauzy organization
The Gauzy deployment needs the Ever Async integration plugin and its settings UI. In your Gauzy organization, create that integration, select the permitted projects, and map employees using all four fields:
| Mapping field | Value |
|---|---|
| Chat provider | slack or discord |
| Workspace | Verified workspace/server ID from the Async connection |
| Chat user ID | User identifier within that workspace |
| Employee ID | Employee in the selected Gauzy organization |
Generate the integration credentials in Gauzy. The key and secret are shown once. In Async choose Pair Gauzy, and enter:
- A name, Gauzy API URL, and Gauzy web app URL.
- The Gauzy tenant ID, organization ID, and integration ID.
- The integration's API key and API secret.
- The verified Slack or Discord connections allowed to use this pairing.
The API URL must be approved by the Async deployment administrator before Async will send Gauzy credentials to it. Use your own Gauzy deployment's addresses. The web app URL supplies links people can open.
Selected connections is the default. Select at least one verified chat connection. The explicit All verified connections in this tenant option also includes future verified Slack and Discord connections in that tenant. It does not grant another Async tenant access.
Saving verifies the configured Gauzy integration, tenant, and organization. Enable the pairing when ready. Task lookups remain read-only and use Gauzy's current project selection and employee mappings. See the Gauzy connector guide for resolution behavior, transport details, and optional static self-hosted configuration.
Verify, rotate, or disable
Verify connection checks saved credentials and identity without posting chat messages. This confirms the provider handshake; it does not prove a live chat event has been enriched.
Use Edit to rename a connection, change settings, or replace credentials. Saving verifies changes before accepting them and preserves the current enabled state. For a Gauzy rotation, generate replacement credentials in Gauzy, then save them in the pairing's empty credential fields. Managed connections do not need an Async server restart.
Disable stops the connection and remains available even when the provider credential has been revoked. Enable verifies the connection again. If a record changed while its editor was open, close the editor, refresh the list, and review the latest settings before saving.
Set a conversation policy
Open Policies, select Chat connection, and enter the conversation's channel or thread ID. Each option shows its connection name, provider, and verified workspace/server ID. Choose Load to inspect the current policy, then Save policy after editing it.
Policies belong to the saved connection in the current tenant. Two Slack workspaces can use the same conversation identifier without sharing a policy. Disabled verified connections remain selectable so you can prepare a policy before enabling their chat traffic. Switching tenants clears the selection, conversation, and unsaved policy; late responses cannot fill the new view.
Static self-hosted deployments without managed Connections retain the explicit
Channel provider field, such as slack or discord.
Self-hosted availability
If Connections reports that management is unavailable, the deployment needs authenticated sessions and secure connection storage configured by its administrator. Keep encryption keys in the deployment's secret environment. The self-hosting guide and Gauzy connector guide cover deployment setup.