After your admin adds a source in Settings → Sources, connect your own account in Integrations. This applies to admins too. A service source usually still requires your personal connection.
Connect and verify
- Join the Sim organization through its invitation or SSO. Use the verified email required by the provider connection.
- Open Integrations, select the app, and choose Connect in its header.
- Complete authorization in the new tab. If the popup is blocked, allow it and select Connect again.
- Return to Search or Search → Assistant and search for content your account can open. Read a result and follow its source link.
Your organization currently supports one connected account per provider. Open the app to see that account's permissions and connection actions.
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.
You do not choose repositories, channels, labels, or an indexing method during personal authorization. Member mode uses your provider access; service mode further restricts results with the admin's source settings.
Provider exceptions
Gmail, Calendar, and Drive have separate grants. Connecting one does not authorize the others. Except for GitLab's permission model, a service account restricts resources rather than replacing your personal connection.
Creating Jira sprints requires the Jira sprint permission. If your account was connected before sprint actions were added, reconnect it to grant that permission. Existing Jira operations continue to use their existing permissions.
Tool permissions
Open the app in Integrations and select your account. Tool permissions appear in its details when the app has supported Assistant tools available to you. Hover over or focus the info button beside a tool to read its description. Set a preference for each operation or use the Read-only tools and Write tools group controls:
Read-only operations default to Allow; write operations default to Ask. An organization can require review even when you select Allow. A group-level Allow covers the currently listed operation versions; newly added or changed operations still ask.
These preferences belong to your account. They cannot grant access to another person's credentials or bypass an administrator's source restrictions. If a related app uses a restricted Search source, direct operations remain unavailable; Assistant can search and read within the configured scope.
Search sources and apps used for actions share the same Integrations list. An admin makes the app available in organization source settings, then each member connects their own account. Configured apps remain visible when disabled; their connection actions are unavailable, and existing accounts can still be inspected or disconnected.
Reconnect or disconnect
Open the app and select the account, then choose Reconnect in the header when a grant expires, is revoked, or needs more scopes. Reconnect with the same provider account; switching identities on an existing connection is not supported, including after disconnecting. A temporary provider outage does not necessarily require reconnecting.
Choose Disconnect in the same header to stop future use of the grant. This can affect workflows sharing the account. Review the confirmation before removing it. Disconnecting does not remove your Sim membership.
For an account-connection request, sign in as the verified Sim user associated with the requested email, then authorize the provider. The request does not invite you into the organization; membership and Search access are still required.
Find missing results
- Confirm the connected account can open the original content.
- Ask an admin to check service-source filters when that mode is selected.
- Check scope errors, rate limits, and incomplete-coverage status.
- Try the query in the provider's search; its limitations still apply.
Live Search calls the provider for each request. Waiting for a Sim sync or retrying document indexing will not resolve a live Search failure.