- Context Voyager receives
- Google Calendar events and availability, Google Drive files, Google contacts and, subject to Google's verification requirements, Gmail messages, for the accounts and scopes you authorize.
- Actions, where authorized
- Where the granted scopes and your authority policy allow, Voyager can act back through Google Workspace, for example proposing or applying a calendar change or preparing a reply for approval.
- Permissions and scope
- Access follows the Google account or administrator authorization, the scopes granted and the features enabled for your deployment. Voyager does not see accounts or data outside that authorization.
- Workflows it supports
- A client email that moves a deadline, a rescheduled meeting that affects a delivery date, a revised document that needs review, and contacts kept consistent with relationship records.
- Voyager's own equivalent
- Voyager's inbox and Discuss, Schedule, the Vault document library and Relations contacts.
- Keep it, replace it, or both
- Most organizations keep Google Workspace for email, calendar and files and use Voyager for the work around them. Selected communication, scheduling or document work can move into Voyager later.