Google Workspace
Connecting Google Workspace gives the agent access to two Google surfaces: Google Drive (under a deliberately narrow scope) and Google Calendar. That's it for now — Gmail, Docs, Sheets, and Slides are not part of this integration today.
The Drive caveat — read this
Magister requests the drive.file scope, which is a deliberately limited Drive scope. In plain English:
The agent can only read, edit, and manage files that it created itself through Magister. It cannot see or touch files you already have in your Drive that weren't created through the agent.
This is a privacy and safety decision: the broader "full Drive" scope would give Magister access to every file in your Google account, including things completely unrelated to marketing work. We opted for the narrower scope on purpose.
In practice
- Ask the agent to "create a new file in Drive with the positioning statement" → works, and the agent owns the file for future edits.
- Ask the agent to "open the positioning doc my cofounder sent me last week" → will not work. The agent can't see it.
- Workaround: upload a copy of the existing file to Magister's Files directly, and the agent can read it from there.
Calendar — the Calendar scope is separate from Drive and not subject to the drive.file caveat. The agent can read events and work with your calendar normally.
Disconnecting — revokes both Drive and Calendar access at once. Re-connecting re-prompts for the same set of scopes.