Google Workspace
Connecting Google Workspace lets Magister create and manage app-created files in Drive, including Google Docs, Sheets, and Slides, and work with Google Calendar. Gmail is a separate, send-only integration and does not grant inbox access.
The Drive caveat — read this
Magister requests the drive.file scope, which is a deliberately limited Drive scope. In plain English:
Magister can only read, edit, and manage files it created through the app-scoped flow. It cannot browse your existing Drive library as if it had full-drive access.
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 Google Doc with the positioning statement" → works, and Magister can manage the app-created file later.
- 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 Assets & Files directly, and the agent can read it from there.
Calendar — Calendar authorization is separate from the drive.file limitation. Magister can create and manage supported calendar events.
Disconnecting — revokes both Drive and Calendar access at once. Re-connecting re-prompts for the same set of scopes.