Connectors

Connect a tool you already use — like Google, GitHub, or Slack — so your teammates can work with it, while you decide exactly which permissions you hand over.

In short

• A connector links a tool you use (Google Drive, Slack, GitHub…) to your teammates so they can read or act in it.
• You browse a catalog of tools, search for the one you want, and connect it in a small pop-up.
• For some tools you pick exactly which permissions to grant — all are ticked by default, and you can only narrow them.
• Connecting never sends anything on your behalf. It just links the tool; sending still waits for your OK.
• Find it under Connectors (Connecteurs) in the side menu.

What a connector is

A connector is a link between an outside tool and your teammates — think of it as giving a new hire a key to one room in your office. Once Google Drive is connected, a teammate can read the files you’ve allowed; once Slack is connected, it can post where you’ve allowed. Nothing is connected until you say so, and each tool is connected on its own.

Open Connectors (Connecteurs) in the side menu. At the top you’ll see a few orientation cards (Agent Tools, Invocations, File Sync, and Custom MCP server). Below them are the connectors themselves: a Featured row of popular tools, and an All Connectors section you can expand to browse the full catalogue.

The Connectors page — orientation cards on top, then Featured and All Connectors below.

To find a specific tool, expand All Connectors and type into the Search box — results filter as you type by name and description. With the box empty you can browse by category instead.

Connect a tool

Pick a tool from the catalog

Find the tool in the Featured row or by searching, then click its card. A small Connect pop-up opens, naming the tool and what it does.

Clicking a connector card opens the Connect pop-up for that tool.

Choose what to share (when offered)

Some tools — Google, GitHub, Microsoft, and Slack — let you tick exactly which permissions to grant under Permissions to grant. Every permission is ticked by default; untick anything you don’t want to hand over. Others simply show you the access they’ll use so you know before you continue.

The permissions list — all ticked by default, with a plain-language line for each.

Authorize and confirm

Press Connect to [tool]. A new tab opens on the tool’s own sign-in page, where you log in and approve. When you return, the pop-up closes and the tool shows as connected. For tools that use a key instead of a sign-in, you paste the key into the field and press Save.

Authorizing on the tool's own page, then landing back in the Portal connected.

You’ll know it worked when you come back from the sign-in tab and the tool’s card shows it’s connected. Your teammates can now use it within the permissions you chose.

You choose the permissions (least access)

When a tool offers the permission list, every box starts ticked — so you always grant at least what you’d expect, and you can only ever narrow it, never widen it. A good habit is to leave only what a teammate actually needs: if a teammate only needs to read files, you can untick the “create and update” permission.

Good to know — grant the smallest set that gets the job done. You can always reconnect later to grant more if a teammate needs it.

A permission (sometimes called a scope) is one specific thing the tool will let a teammate do — for example “read your files” or “post messages.” Each one is spelled out in plain words in the list.

Manage or disconnect a tool

To change or remove a connection, reopen the tool’s card from the catalog. To grant different permissions, connect again and adjust the ticks. Disconnecting a tool stops your teammates from using it; reconnect any time to bring it back.

File Sync (Files) — the File Sync card at the top of the page opens the Files view, where you can see how documents your teammates produced are syncing to each connected tool, and turn syncing off or retry it per file.

Custom MCP server is Advanced. The Connect by URL card lets a technical user link their own tool server by pasting a web address. If that’s not something you set up yourself, stick to the catalog tools above — they’re the simple, recommended path.

Connecting is not sending

Connecting a tool only gives your teammates access to it. It does not send any message, post, or email on your behalf.

No card. No connecting your email. Nothing gets sent without your OK.

Ask before sending is ON by default — so even after a tool is connected, anything heading out (an email, a post, a message) pauses and waits for you. You give the final OK. For reviewing what’s waiting, use the Approvals page.

What if it isn’t working?

If a connection won’t go through, walk these in order:

1. The sign-in tab opened but nothing happened back here. Finish signing in and approving on the tool’s page, then return to the Portal — the pop-up closes itself once you’re back.
2. “OAuth credentials not configured.” This tool isn’t set up to connect on your workspace yet. Ask whoever set up your company to enable it, or pick a different tool for now.
3. The Connect button is greyed out. You’ve unticked every permission — tick at least one to continue.
4. You pasted a key but it won’t save. Make sure every required field is filled (optional ones are labelled), with no extra spaces.
5. A teammate still can’t use the tool. Reconnect it and check you granted the permission that action needs — for example “create and update,” not just “read.”

Still stuck? Head to Getting help and we’ll sort it out.

FAQ

Does connecting a tool send emails or post anything for me?

No. Connecting only links the tool so your teammates can use it. Sending still waits for your OK — Ask before sending is on by default, and nothing leaves your account without your approval.

Can I share less than the tool asks for?

Yes, when the tool offers the permission list (Google, GitHub, Microsoft, Slack). Every permission starts ticked; untick the ones you don’t want. You can narrow what you grant, and reconnect later if a teammate needs more.

What's the difference between connecting and uploading a document?

Connecting links an outside tool so teammates can act in it. Uploading a file stores a document for teammates to read. For documents, use the Business knowledge page.

A tool says its credentials aren't configured — what now?

That tool hasn’t been enabled to connect on your workspace yet. Ask whoever set up your company to turn it on, then try connecting again.

What is the 'Custom MCP server' card for?

It’s an advanced option for connecting your own tool server by pasting its web address. If you didn’t set that up yourself, you can ignore it and use the catalog tools instead.

Next steps

Tools and voice

Give a single teammate the tools it needs for its job.

Approvals

Review and approve anything a teammate wants to send.

Business knowledge

Upload documents for teammates to read — separate from connecting tools.

Trust and safety

How your data stays private and why nothing sends without your OK.