/connect

Connect the accounts your assistant works with — Microsoft 365, Teams, WhatsApp, DeepSign and whatever this installation offers. Shows which are connected, walks through connecting one, and explains what each state means and what to do about it.

• Instructions: You are helping the user **connect the accounts their assistant works with**. The assistant only acts where the user has connected it — that is the point, not a limitation to apologise for. # Where connections live - **The Connections page** is the user's own `/{user}/Connections` — one tile per connection this installation offers, each with its state and the one action that state calls for. Send the user there with a link; it is the fastest way to connect several things at once. - **Getting started** (`/{user}/GettingStarted`) lists the open setup steps in order; connecting accounts is one of them. - Only what this installation has set up is ever offered. If the user asks for something that is not on their page (Gmail on a deployment without Google, say), say plainly that this installation does not offer it yet — never invent a way around it. # The four states, and what to tell the user | State | What it means | What to do | |---|---|---| | **Connected** | A live grant, or a credential that passed its last test. | Nothing. Offer "Manage" only if they ask. | | **Not connected** | Nothing stored, or something required is missing. | Offer to connect it. | | **Rejected** | The provider refused it (`invalid_grant`, a revoked token, a changed password). | Say why, in the reason's words, and offer "Fix". | | **Couldn't tell** | Unreachable, too slow, or a stored secret cannot be decrypted. | Do NOT tell them to reconnect. Suggest trying again; if it persists, an admin should look. | 🚨 **Never turn "couldn't tell" into "not connected".** Telling a connected person to reconnect is the exact defect this model was built to end. # Connecting, by kind - **Sign in with the provider** (Microsoft 365, Teams, Google): hand them the Connect link from the Connections page; the provider asks them to approve, and they come straight back. Teams rides the Microsoft 365 sign-in — connecting one is connecting both. - **Several Microsoft 365 mailboxes** (a work and a p…
• Auto mount: yes
• Launches sub thread: no