Thegram web and apps
Use the web for immediate access and provider authorization, or a native app for the device’s document, sharing and system integrations. Connecting an external AI to Thegram does not require a desktop app running in the background.
Web workspace
Section titled “Web workspace”Open Thegram and sign in. Select the intended workspace before working with its documents. The product switcher separates thegram documents and storage from thegram AI chats and projects.
- Documents and storage: locate the right source, open the document, and use the document, dashboard or graph view that answers your question.
- AI chats and projects: start with a question, select the relevant context and inspect the sources in the answer. A proposed external action still needs review.
- Connected Services: authorize an external service in the browser and verify the intended account. The organization label alone is not a grant to every document.
- AI permissions: review which Thegram resources an AI connection may read or write. Do not broaden access to make a connection check pass.
iPhone and iPad
Section titled “iPhone and iPad”Use the Thegram App Store page for the public app, or an explicitly approved build supplied by your organization. Your device and account permissions remain authoritative.
These are new captures from native source, not responsive-browser mockups or reused marketing images. Capture build: app 1.2.0, UI 3.64.0, 25 October 2026. A capture build is not a claim that a new App Store version has been published, or that physical-device behavior has been certified.
First sign-in
Section titled “First sign-in”- Open the app and choose your normal sign-in method. Complete provider checks yourself; do not give an assistant your password, verification code or API key.
- Confirm the account before selecting the intended organization. Signing in identifies the person; access still depends on membership and resource permissions.
- Open an existing permitted document and read its current state before editing. Local-device files and Cloud vaults are different storage locations.
- If an app update is offered, let the verified update finish before relying on the new interface. Do not install an unrelated package or disable signature verification.
For device-specific guidance, see iPhone and iPad. Authorize new work-service connections through the web connector flow, then return to the app.
Use the current native build supplied by your team. The native shell provides its own account sign-in, windows, printing and system integrations; it is not a required proxy for Cloud MCP. Do not follow archived DMG or desktop-socket setup instructions to connect an AI.
Sign in through the app’s normal account flow and select the intended workspace. A successful compilation is not proof of a connected session: if the app reports an unavailable release, network error or failed sign-in, resolve that state before editing or sharing. If no current Mac build has been supplied, the web remains the documented access route.
Keep the boundaries clear
Section titled “Keep the boundaries clear”| Task | Correct place |
|---|---|
| Authorize Notion, Slack, Drive or another work service | Web → Settings → Connected Services |
| Connect ChatGPT, Claude or Grok to Thegram | The AI provider’s OAuth connector flow |
| Connect a coding agent | Its plugin installer and a privately entered, scoped Thegram API key |
| Review an AI’s Thegram access | Settings → AI permissions |
| Read or edit a document | The app or web, with the correct source and permissions |
| Send, post or change an external resource | Review the precise provider, account, target and arguments first |
See service connectors, AI setup and connection troubleshooting for the next step.
Sources for this guide
Something different from this guide? Report a docs issue · Troubleshooting
Review and send the email yourself. Do not include API keys or private document content.