Skip to main content
Every connection has a sharing scope and a per-person access level. Open a connected account and go to the Access tab.

​
Who should have access?

Anyone in your workspace can use this connection. Use it for shared company accounts.Everyone on the team gets Full access unless you restrict them here. Per person you can choose:
  • Full access: all of the connection’s tools.
  • Read-only: only this app’s read tools.
  • No access: the person does not see this connection at all.
Custom MCP connections are always team-only.

​
What “connect your own account” means

For personal tools like email and calendar, the normal pattern is that each teammate connects their own account as a Private connection. Henry then acts as each person, in their own account, with their own permissions. Nobody needs to share a login. If you ask Henry for something that would need a colleague’s private connection, Henry tells you the integration is private to that person and offers the two paths: ask them for access, or connect your own account.

​
Access and identity across channels

Access follows your Henry identity, not the channel. A private connection you can use in Slack is available when you text Henry or use the web app. In Microsoft Teams, link your Microsoft account in Settings → Profile so Henry knows the Teams user is you.

​
Guests

People who are not members of your workspace, such as Slack Connect guests from another company, never get access to your connections, your memory, or your tasks. Henry answers them from the conversation alone.

​
When someone leaves

Removing a member from the workspace disables the connections they owned rather than deleting them, revokes the invites they had extended, and removes their standing approvals. Team-scope restrictions you set on them stay in place so a re-invite does not silently restore full access. See Members and roles.