Shared integrations
A team leader can publish one of their own integrations to the team, and members can request access to it — so you connect QuickBooks or Microsoft once rather than every member doing it separately.
What can be shared
Section titled “What can be shared”Integrations that use app-level credentials the team can inherit:
The Shared Integrations panel on the team dashboard shows what you have available to share.
Sharing one
Section titled “Sharing one”-
Connect the integration on your own Integrations page first.
-
On the team dashboard, find Shared Integrations → Your integrations.
-
Click Share with group.
It moves into the published list. Stop sharing unpublishes it.
How members get access
Section titled “How members get access”-
A member sees the shared integration and clicks Request access.
-
The request appears in Members request access on your panel, and you get an email.
-
You approve or deny it.
-
On approval the member connects and can use it.
While a request is outstanding the member sees Awaiting approval.
Managing access afterwards
Section titled “Managing access afterwards”| Action | Effect |
|---|---|
| Approve | The member can connect and use the integration |
| Deny | The request is refused; the member is emailed |
| Disable | Access already granted is switched off; the member sees “Access disabled” |
| Regrant | Restores access you previously disabled |
| Stop sharing | Unpublishes it for everyone |
Members are emailed on approval, denial, and disabling — so nobody is left wondering.
When not to share
Section titled “When not to share”Sharing suits integrations where one organisational connection genuinely serves everyone — a single QuickBooks file, one Microsoft tenant.
It doesn’t suit anything personal. Nobody should share a Mailchimp connection tied to their own newsletter list, or a Stripe account that receives their gifts. Those belong to the individual.