Connected Workspaces
Gmail, Calendar, files, documents, tasks, and the systems that turn Viventium into more than a standalone chat window.
Why Connected Workspaces Matter
Real work rarely lives in one place.
Important context is usually split across:
- inboxes
- calendars
- documents
- spreadsheets
- files
- tasks
- search surfaces
Connected workspaces matter because Viventium gets much more useful when it can pull from the places where your actual work already lives.
What They Unlock
Connected workspaces let Viventium do more than reply from memory.
They make it possible to:
- gather the right context before answering
- prepare briefings and summaries
- revisit the same systems on a schedule
- feed projects with live workspace context
- reduce manual copy-paste between your tools and your AI
Google Workspace
The source repos point to broad Google Workspace support, including workflows around:
- Gmail
- Calendar
- Drive
- Docs
- Sheets
- Slides
- Tasks
- Forms
- Chat
That is why Google Workspace shows up so often in the docs and demos. It is one of the clearest examples of Viventium as a second brain instead of a standalone chat app.
Microsoft 365
Microsoft 365 matters for the same reason.
The public product story includes work around:
- Outlook mail and calendar
- OneDrive files
- Excel workbooks
- OneNote notes
- To Do and Planner tasks
- related organization surfaces where they fit
Good First Connections
If you are starting small, the highest-leverage connections are usually:
- inbox
- calendar
- the main document or file surface you already use
That gives Viventium enough live context to be useful without over-connecting everything on day one.
How Connections Work
Workspaces connect through Model Context Protocol (MCP) servers. Each MCP server:
- Bridges Viventium to one external system
- Exposes tools the main agent and background agents can call
- Runs locally as part of your stack
- Requires explicit user authorization before accessing any service
The flow:
- Connect the service in
Settings -> Connected Accounts - Authorize the specific permissions you want to grant
- Viventium's MCP server handles authentication and data retrieval
- All data stays in your local stack — Viventium does not proxy through external servers
Access Model
Good integration behavior should stay simple:
- Connect only what you actually need — start with inbox and calendar
- Let Viventium fetch context when it helps — no constant polling
- Keep write actions reviewable — Viventium asks before sending emails or creating events
- Disconnect access anytime — revoke permissions without breaking the system
Where This Becomes Powerful
Connected workspaces get much more useful when paired with:
- Background Agents — deeper retrieval and independent analysis of workspace data
- Scheduling — morning briefings that pull from inbox, calendar, and tasks automatically
- Projects, Workers & GlassHive — longer-running work fed with live workspace context
- Architecture Overview — where MCPs fit in the full system