Enter to open, arrow keys to move, Escape to close

    Connecting tools

    Private and shared connections

    Share a connection with your workspace or keep it private, and see how actions use each person's own connection.

    On this page

    Who can see what a connection brings in, and who can act through it? Every connection belongs to one person in one workspace, and it starts private. Share it when the whole team should be able to use what it brings in, such as a team Slack or a company Notion. Keep it private when it holds your own work.

    Share a connection with the workspace

    1. Find your connection

      Open Connect > Integrations and find your connected card. It has a row that reads Private to you.

    2. Choose Share

      In that row, choose Share.

    3. Confirm

      A dialog asks "Share <tool> with the workspace?" and explains what everyone will be able to see. Choose Share with workspace.

    4. Check the row

      The row now reads Shared with the workspace. Right after sharing you can choose Undo. Later, choose Make private to take it back.

    For GitHub, the share control is in the Also connected directly row on the GitHub card.

    Making a connection private again withholds its content from everyone else straight away.

    If sharing fails

    Hoppflow says "Could not share it just now. It is still private to you." Nothing changed, so try again.

    What sharing covers

    • Sharing is offered for built-in connections such as Slack, Notion, Outlook, Microsoft Teams, GitHub and HubSpot.
    • Calendars are never shared. Outlook Calendar has no share control.
    • Remote MCP connections cannot be shared from the app. They stay private to the person who connected them.
    • On a shared Slack connection, private channels and direct messages are never synced, shared or not.
    • On a shared GitHub connection, the workspace sees open issues and pull requests from public repositories only. Issues and pull requests from private repositories, and from any repository GitHub does not confirm is public, stay visible only to you.
    • Each reader is checked again every time shared content is read.

    How sharing changes what the brain shows

    Sharing decides who can see what a connection added to the brain:

    • Content from a private connection is kept for the member who connected it. It does not appear in answers other members read.
    • Content from a shared connection is open to everyone in the workspace.

    Whether a connection's content enters the brain at all is a separate switch. See Choose what the brain reads.

    Why sharing does not let others act as you

    Sharing a connection lets the team see its content. It does not let other people act as you.

    • A tool call runs as the person it is made for. Hoppflow never falls back to the connection owner's account, or the workspace owner's.
    • Membership is checked again when an approved action is sent.
    • A write through a shared connection still needs the connection owner's own approval.
    • In an automation, every external step uses the automation owner's connection.