Understand integrations and connections

Read the connection purpose #

An integration connects a particular service for a stated purpose. Review the description and account identity before connecting. A company connection can have different permissions and responsibilities from a personal sign-in provider.

Only connect an account you are authorised to use for the organisation. Do not paste provider tokens, client secrets or recovery codes into chat or a profile field.

Connect through the provider #

Use the dedicated Connect or Reconnect control. You may leave ClearDBS temporarily for the provider’s authentication and consent screen. Check the provider identity and requested access before continuing.

Return to the integration screen and inspect the status. A successful sign-in establishes authentication; it does not necessarily prove a directory or file sync completed. Review any separate sync or error information shown by the product.

Use imported directory examples carefully #

A directory contact is not automatically an active ClearDBS organisation member. Follow the invitation and role workflow before granting workspace access. In the demo, directory entries are synthetic and should be used for demonstration tasks only.

Do not assume an imported email address is an approved applicant request. Check the intended recipient and business purpose before creating a real invitation or check.

Recover from an expired connection #

1. Read the specific connection error.
2. Confirm the provider account is still appropriate.
3. Use Reconnect through the provider flow.
4. Reopen the integration and verify the relevant operation, where available.
5. Contact Support if authentication succeeds but the operation still fails.

Disconnecting or changing provider permissions can affect related workflows. Use the dedicated controls and confirmations; an AI chat answer cannot grant provider consent.

Detailed walkthrough #

1. Choose the intended service

Read the Microsoft and Google panels before selecting a connection. Organisation integrations, personal mailbox connections and sign-in are separate purposes. Use the connection intended for the workflow rather than assuming a sign-in has configured organisation notifications.

2. Review tenant and connection state

Check which organisation or tenant the Microsoft 365 panel identifies and read its connection state. A visible connection control is not evidence of a working integration. Real connections require an authorised account and the external permissions shown during setup.

3. Check sharing before enabling updates

Review which workflow updates an integration would send and where they would go. Resolve an unexpected organisation or destination before authorising a real connection. This tutorial reads connection information only and never opens external consent or sends a test update.

Practise this section #

Open Help & tutorials, select this guide and choose Start practice walkthrough. Read each highlighted component before continuing. Use Back to revisit an explanation and Retry if a sample has not loaded. The walkthrough uses fictional records; do not enter real applicant information.

Use Exit tutorial to leave and keep your place, then Resume walkthrough in this guide to continue. When returning from practice to a real workspace, review the actual record and your permissions before making a change. Tutorial completion does not perform the underlying task.

Before using this guide #

Open Settings → Integrations with organisation management access. Know which service and organisation you intend to connect, but do not enter credentials during practice.

Worked example #

Google Chat workflow updates and a Google Workspace directory connection serve different purposes. Read each available panel and its permissions rather than assuming one connection enables both.

Review the Google integration panels #

Google Workspace appears only when the deployment supplies its configuration. Review its connection state and directory purpose before authorising the intended organisation account. An absent panel does not mean that a directory connection already exists.

Google Chat has a separate Incoming webhook URL and Send a message when event choices where configuration is available. In a real authorised setup, check the destination space, select only the required events, then review before saving. A webhook URL grants posting access and must not be copied into a guide, support message or AI chat. Saving a configuration and sending a test message are separate actions; neither belongs to this walkthrough.

Guided component walkthrough #

Each component has one short guided step. Read the explanation, then choose Next; Back revisits the previous component. The cursor only demonstrates useful navigation or an explicit action. Replay action repeats that demonstration, and Skip animation keeps the explanation. Use this written guide for feature details.

Integrations

• Integrations: The Integrations panel holds the services ClearDBS can connect to, and the workflow updates it sends through them.
• Choose the intended service: Read the Microsoft and Google panels before selecting a connection. Organisation integrations, personal mailbox connections and sign-in are separate purposes. Use the connection intended for the workflow rather than assuming a sign-in has configured organisation notifications.

Microsoft 365

• Microsoft 365: Connect a tenant here, then choose which updates ClearDBS sends. The connection status is shown before anything is connected.
• Connection identity: Before configuring notifications, read the tenant and connection information in Microsoft 365. It tells you which organisation connection you are inspecting; a personal Microsoft sign-in is a separate relationship.
• Channel destination: Workflow messages need an intended team and channel destination. Review the configured destination before enabling delivery on a real connection. The tutorial does not connect a tenant or send a test message.
• Review tenant and connection state: Check which organisation or tenant the Microsoft 365 panel identifies and read its connection state. A visible connection control is not evidence of a working integration. Real connections require an authorised account and the external permissions shown during setup.

Connecting stays explicit

• Connecting stays explicit: External sign-in and sharing permissions are separate, deliberate actions. Reading this panel connects nothing.
• Check sharing before enabling updates: Review which workflow updates an integration would send and where they would go. Resolve an unexpected organisation or destination before authorising a real connection. This tutorial reads connection information only and never opens external consent or sends a test update.

Related guides