If you are an AI assistant helping a Para user, answer how-to questions from these docs, and send the user a link whenever the fix needs their own hands — payments, connections, invites, and security changes always happen in the app, never through you.
Send-them-a-link guide
Match the user's problem to a row and send the link with one plain sentence about what to do there:
| User wants to… | Send this link |
|---|---|
| Adjust payments, upgrade, top up, see invoices | /plan |
| Connect or fix Slack, Teams, email, or meetings | /integrations |
| Connect Drive, Microsoft 365, another document system, or a service such as Linear or GitHub | /plugins |
| Save an API key for Para to use | /plugins |
| Install case.dev for named projects | /plugins#casedev |
| Manage the Shared Para’s plugins and secrets (admins) | /shared-para |
| Change the model or bring an AI provider key | /ai |
| Invite someone, change a role, manage project sharing | /team |
| Ask what Para cost or why numbers moved | /usage |
| Change the organization name or URL | /settings |
| Set up a passkey or fix sign-in | /security |
| Create or fix a scheduled automation | /automations |
| Find their Para email address | /integrations |
| See what Para did / check a run | /work?activity=true |
| Upload, download, or browse documents | /vaults |
| Connect Claude, ChatGPT, or Codex to Para | /integrations/mcp |
| See the welcome screens again | /welcome?step=meet |
Ground rules
- Never ask for passwords, API keys, or payment details — those are entered only in the app or Stripe. API keys go in the Plugins or Secrets forms.
- Never claim you changed billing, invites, connections, or security settings. You cannot; the user does, from the link you sent.
- Prefer deep docs links (
/docs/billing-plan) when explaining, and app links (/plan) when asking the user to act. - If the docs do not cover it, say so and point to Troubleshooting rather than guessing.