You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d072e72
Browse filesBrowse the repository at this point in the historyBrowse files
feat(search): identify managed MCP accounts to allow several per connector
Read the signed-in account through each connector's documented identity tool
during OAuth completion and key connections on it, sharing one set of account
rules with OAuth providers. Notion, Granola, Fireflies, Coda, and HubSpot now
allow several accounts; connectors with no identity tool stay at one.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/search/connect-your-account.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,9 @@ After your admin adds a source in **Settings → Sources**, connect your own acc
22
22
variant="overview"
23
23
/>
24
24
25
-
To connect another account of the same app, such as Google Drive for two different work accounts, open the app and choose **Add account**, then pick the other account when the provider asks. You can connect up to five accounts per app, and Search looks across all of them. Slack accounts must belong to your organization's connected workspace. Managed connections such as Coda, Notion, Granola, and Fireflies currently support one account. Open an account to see its permissions and connection actions.
25
+
To connect another account of the same app, such as Google Drive for two different work accounts, open the app and choose **Add account**, then pick the other account when the provider asks. You can connect up to five accounts per app, and Search looks across all of them. Slack accounts must belong to your organization's connected workspace. Zoom, Lucid, and Databricks allow one account because Sim cannot yet tell their accounts apart. Open an account to see its permissions and connection actions.
26
26
27
-
Reconnecting keeps the same account. To use a different one, add it as a new account or disconnect the old one first. Your organization and the provider must allow each account to authorize Sim.
27
+
Reconnecting keeps the same account. To use a different one, add it as a new account or disconnect the old one first. If you connected Coda, Notion, Granola, Fireflies, or HubSpot before multiple accounts were available, reconnect that account once before adding another. Your organization and the provider must allow each account to authorize Sim.
28
28
29
29
The connection is usable when authorization completes; no initial indexing run is required. If a provider is missing, ask an admin to add it in **Sources**. `Not configured` means its app or deployment setup needs an admin's attention.
`Expected exactly one organization MCP connection; found ${result.mcpConnections.length}${result.hasMore ? '+' : ''}. Check the email, provider, and connection status.`
164
+
`Expected exactly one organization MCP connection; found ${result.mcpConnections.length}${result.hasMore ? '+' : ''}. Check the email, provider, and connection status. A person with several accounts of one provider needs List Organization MCP Connections to choose between them.`
Copy file name to clipboardExpand all lines: apps/sim/lib/credential-groups/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Credential Groups remains available whenever its organization feature is enabled
10
10
11
11
An allowed workspace grants every normally authorized manual and deployed workflow access to every active contribution in this pool. There is no per-workflow resource-policy grant and no per-person filtering for workflow execution. Keep ordinary workspace/workflow authorization and deployment authority: an allowlist entry alone cannot authorize running a workflow. Nested workflows use their actual execution workspace. A workspace move, revocation, inactive enrollment, removed provider, disabled group, or unavailable org entitlement blocks subsequent use.
12
12
13
-
Standalone Chat uses the signed-in person’s own connections. Invited contributors do not need organization membership. Redemption requires a verified Sim email matching the invitation; the enrollment is then bound permanently to that user ID. An email change cannot transfer an enrollment. People can connect any provider account they can authorize, even when its email differs from their Sim or invitation email. One person may connect several accounts of a provider from **Integrations**, identified by the provider's subject and tenant, up to five live accounts per provider. This applies to every OAuth provider; Slack accounts must belong to the organization's configured workspace. Reconnect stays bound to the account it was started from; disconnecting releases the slot, and the same identity returning restores its credential. An invitation link only refreshes the account already connected. Managed MCP connections remain one per server because those credentials hold no provider identity. OAuth callbacks require the same verified signed-in user who started authorization. Search requires current organization membership and applies document permissions using the viewer's own verified provider identities; workspace access to the shared credential pool does not grant access to other people's Search documents.
13
+
Standalone Chat uses the signed-in person’s own connections. Invited contributors do not need organization membership. Redemption requires a verified Sim email matching the invitation; the enrollment is then bound permanently to that user ID. An email change cannot transfer an enrollment. People can connect any provider account they can authorize, even when its email differs from their Sim or invitation email. One person may connect several accounts of a provider from **Integrations**, identified by the provider's subject and tenant, up to five live accounts per provider. This applies to every OAuth provider; Slack accounts must belong to the organization's configured workspace. Reconnect stays bound to the account it was started from; disconnecting releases the slot, and the same identity returning restores its credential. An invitation link only refreshes the account already connected. Managed MCP connections follow the same rules for connectors with a vendor-documented identity tool (Notion, Granola, Fireflies, Coda, HubSpot): the account is read through that tool during OAuth completion. An unidentified connection keeps working but blocks adding another until it is reconnected. Zoom, Lucid, and Databricks have no such tool and stay at one per server. OAuth callbacks require the same verified signed-in user who started authorization. Search requires current organization membership and applies document permissions using the viewer's own verified provider identities; workspace access to the shared credential pool does not grant access to other people's Search documents.
14
14
15
15
Disconnect revokes the local grant and invalidates pending invitation-based authorization. Administrators can revoke an enrollment; the person cannot restore it themselves. Removing workspace access stops future authorized calls, but cannot recall a provider request already in flight or erase data already returned to a workflow. Full-pool sharing includes public, scheduled, and webhook deployments that otherwise pass workflow authorization.
0 commit comments