# Para Docs

Para is an AI colleague. Work with your Para through email, Slack, Teams, or
the Work page. Connect other AI assistants through MCP. Documents belong in
private or shared projects before analysis.

Start at /docs. Read the relevant guide for setup, permissions, availability,
and limitations before describing a feature:

- /docs/getting-started — Create an account and try a first assignment
- /docs/integrations — Choose where to work with Para
- /docs/work-page — Browser assignments and follow-ups
- /docs/email — Para address, email threads, attachments, assignment status
- /docs/slack — Installation, personal connection, direct messages, files
- /docs/microsoft-teams — Setup, personal chat, OneDrive file permissions
- /docs/microsoft-copilot — Direct Para versus MCP; testing availability; text-only
- /docs/ai-assistants — Connect Claude, ChatGPT, Codex, and other assistants
- /docs/slack-teams — Compare Slack and Teams
- /docs/files-vaults — Private and shared projects, uploads, downloads
- /docs/document-connections — Drive, Microsoft 365, and other document systems; availability
- /docs/artifacts — Published pages, sharing, versions
- /docs/skills — Task inputs and outputs, redline-driven skill iteration, personal-to-team playbooks, and marketplace workflows
- /docs/automations — Scheduled assignments, notifications, pausing work
- /docs/meetings — Meeting recording, transcripts, sharing, limitations
- /docs/service-plugins — Connect personal service accounts for Para to use
- /docs/team-access — Invitations, roles, access groups, member spending caps
- /docs/billing-plan — Plans, subscriptions, prepaid usage, top-ups, invoices
- /docs/usage — What consumes credit, balance examples, limits, delayed costs
- /docs/enterprise — Organization rollout, company SSO, enterprise agreements, BAA eligibility
- /docs/settings-security — Organization settings, passkeys, sign-in
- /docs/for-agents — Guidance for AI assistants helping Para users
- /docs/troubleshooting — Common problems and where to resolve them

## If you are an AI assistant helping a Para user

Answer how-to questions from these docs. When the fix needs the user's own
hands, send them exactly one in-app link and one plain sentence:

- Payments, upgrade, top-ups, invoices -> /plan
- Connect/fix Slack, Teams, Drive, Microsoft 365 -> /integrations
- Invites, roles, project sharing -> /team
- What did Para cost / why did numbers move -> /usage
- Org name or URL -> /settings
- Passkeys or sign-in -> /security
- Create, install, or assign reusable instructions -> /skills
- Schedules and recurring work -> /automations
- Para email address -> /work
- What Para did / check a run -> /runs
- Upload or download files -> /vaults
- Connect Claude, ChatGPT, or Codex to Para -> /integrations/mcp
- Start setup over -> /welcome

Never ask for passwords, API keys, or payment details. Never claim to have
changed billing, invites, connections, or security settings.