VELORA CONNECTIONS
Connect deliberately.
Velora works with tools you choose. A linked account belongs to its authorizer; a room link does not hand its credentials to every member. Sharing external content with a room will require an explicit, permissioned snapshot or source grant.
Available = in a public buildRestricted pilot = limited accessPlanned = roadmapHeld = blocked on acceptance
| Connection | Status | Current or intended use |
|---|---|---|
| Local repositories and files | Available | Choose a workspace or attach a file for Code work. Selected-folder Brain indexing is planned. |
| GitHub | Available | Use the existing GitHub tools and selected repository workflows. Deeper organization sync is planned. |
| MCP servers | Available | Connect supported tools through Velora’s approval-aware registry. Review each server’s permissions. |
| Supabase and Vercel | Available | Connect the existing development tools when you choose to use them. |
| Google Drive, Docs, Sheets and Calendar | Restricted pilot | Selected account surfaces remain closed to general public access while OAuth review and live tests continue. |
| Slack | Planned | Select channels for room context; posting will require approval. |
| Notion and Linear | Planned | Start with selected page, project and issue reading with citations. |
| Airtable and Microsoft 365 | Planned | Follow the same permissioned connector model after Records is stable. |
| Gmail and mailbox playbooks | Held | Business mailbox actions are not in a public release while controlled live acceptance is pending. |
How a room connection will work
- 1. Choose
Select a file, repository, channel or calendar. - 2. Review
See its audience, permission and freshness before publishing a room snapshot. - 3. Revoke
Stop future retrieval and mark affected citations stale.
This room source flow is planned. Existing connectors retain their current permissions.
Read the Google pilot guide, approval guide, or public changelog.