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 dff74b6
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: apps/docs/content/docs/search/ask-questions.mdx
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,19 +127,21 @@ Copy the reviewed draft into another app, or ask Assistant to create it using yo
127
127
128
128
When integration actions are enabled, Assistant can answer questions and take supported actions in the same conversation. For example, ask it to draft an email in Gmail or create a Jira issue using your own connected account.
129
129
130
-
Reads run without a prompt by default. Writes wait for review by default. Each proposal appears inline in the conversation with its app, account, destination, and proposed content. Edit the supported fields, then select**Allow** or **Cancel** for each action. After several proposals, **Allow N shown** or **Cancel N shown** applies your choice to that displayed batch. You can approve individual actions first, then cancel the remaining batch.
130
+
Reads run without a prompt by default. Writes wait for review by default. Each proposal appears inline in the conversation with its app, account, destination, and proposed content. Select **Edit** to change supported fields, then choose**Allow** or **Cancel** for each action. After several proposals, **Allow N shown** or **Cancel N shown** applies your choice to that displayed batch. You can approve individual actions first, then cancel the remaining batch.
131
131
132
132
<Image
133
133
src="/static/search/assistant-action-review.png"
134
-
alt="Inline Assistant action review showing the connected Jira account, exact site and project, editable issue summary and description, and Allow or Cancel controls"
135
-
width={705}
136
-
height={489}
134
+
alt="Compact inline Jira proposals showing the account, destination, proposed content, Edit, Allow, and Cancel"
135
+
width={1440}
136
+
height={1000}
137
137
variant="detail"
138
138
/>
139
139
140
+
Decisions remain in the conversation as expandable receipts after reload. **Approved** means review is complete; the status changes to **Running**, **Completed**, or **Failed** as execution proceeds. **Cancelled** records a skipped proposal. **Outcome unknown** means you should check the original app before repeating the action.
141
+
140
142
Each decision applies to that proposal. Changing its account or destination requires a new proposal. An action can still fail if your account is disconnected or an administrator changes access before execution. If the provider outcome is unknown, check the original app before asking Assistant to repeat a write.
141
143
142
-
Configure persistent **Allow**, **Ask**, or **Block** preferences under **Integrations → ⋯ → Tool permissions** for your account. See [tool permissions](/search/connect-your-account#tool-permissions).
144
+
Configure persistent **Allow**, **Ask**, or **Block** preferences under **Integrations → app → account**. See [tool permissions](/search/connect-your-account#tool-permissions).
Copy file name to clipboardExpand all lines: apps/docs/content/docs/search/connect-your-account.mdx
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,19 +10,19 @@ After your admin adds a source in **Settings → Sources**, connect your own acc
10
10
## Connect and verify
11
11
12
12
1. Join the Sim organization through its invitation or SSO. Use the verified email required by the provider connection.
13
-
2. Open **Integrations**, find the provider, and choose **Connect**from its **⋯** menu.
13
+
2. Open **Integrations**, select the app, and choose **Connect**in its header.
14
14
3. Complete authorization in the new tab. If the popup is blocked, allow it and select **Connect** again.
15
15
4. Return to **Search** or **Search → Assistant** and search for content your account can open. Read a result and follow its source link.
16
16
17
17
<Image
18
-
src="/static/search/connect-account-menu.png"
19
-
alt="The Confluence menu in Integrations with Connect available before an account has been authorized"
18
+
src="/static/search/connect-account-details.png"
19
+
alt="Coda integration details with Connect in the resource header and no account connected"
20
20
width={1440}
21
21
height={1000}
22
22
variant="overview"
23
23
/>
24
24
25
-
If your organization makes another connection available, choose **Add account**from the same menu.
25
+
If your organization makes another connection available, choose **Add account**in the header. When several accounts are connected, select an account to see its permissions and connection actions.
26
26
27
27
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.
28
28
@@ -38,15 +38,15 @@ You do not choose repositories, channels, labels, or an indexing method during p
38
38
| Confluence service account | Connect Confluence. Both your account and the service connection must read the selected content. |
39
39
| Coda | Connect personal Coda MCP. Service mode also verifies the parent document with its REST token. |
40
40
| GitLab | No personal connection. Your verified Sim email must match current GitLab identity and permissions, or the admin's CSV mapping and project grant. |
41
-
|[Generic Secrets, Member mode](/search/generic-secrets)|Select**Manage secrets** in Integrations and save your own values for organization Home conversations. |
41
+
|[Generic Secrets, Member mode](/search/generic-secrets)|Open**Generic Secrets** in Integrations and save your own values for organization Home conversations. |
42
42
43
43
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.
44
44
45
45
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.
46
46
47
47
## Tool permissions
48
48
49
-
When Assistant integration actions are enabled, open the app’s **⋯** menu in **Integrations** and select **Tool permissions** for your connected account. This option appears when the app has supported Assistant tools available to you. Set a preference for each operation or use the **Read-only tools** and **Write tools** group controls:
49
+
When Assistant integration actions are enabled, open the appin **Integrations** and select your account. Tool permissions appear in its details when the app has supported Assistant tools available to you. Set a preference for each operation or use the **Read-only tools** and **Write tools** group controls:
50
50
51
51
| Preference | Behavior |
52
52
| --- | --- |
@@ -66,13 +66,13 @@ These preferences belong to your account. They cannot grant access to another pe
66
66
variant="overview"
67
67
/>
68
68
69
-
Apps used only for actions appear under **Assistant apps**. An admin makes the app available in organization source settings, then each member connects their own account in Integrations.
69
+
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.
70
70
71
71
## Reconnect or disconnect
72
72
73
-
Choose **Reconnect** from the app’s **⋯**menu when a grant expires, is revoked, or needs more scopes. A temporary provider outage does not necessarily require reconnecting.
73
+
Open the app and select the account, then choose **Reconnect**in the header when a grant expires, is revoked, or needs more scopes. A temporary provider outage does not necessarily require reconnecting.
74
74
75
-
Choose **Disconnect**from the same menu 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.
75
+
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.
76
76
77
77
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.
text={`Disconnect ${account.displayName} from all ${integrationName} connections in this organization. Workflows using this account will also lose access. You can reconnect later.`}
0 commit comments