OAuth and Scopes

Tento Google centralizes OAuth token handling and scope declarations for Google Calendar and Gmail integrations.

Scope constants

Use library-owned scope groups instead of spelling raw scope strings in application code:

• READ_CALENDAR
• WATCH_CALENDAR
• READ_EVENTS
• EDIT_EVENT_SCOPES

GoogleScope owns the string representation for individual scopes and GoogleScopes handles parsing, set conversion, and assertion helpers.

Boundary

Provider scopes belong in this crate because they are part of Google's API contract. Product-level permission decisions belong in the host. The host can ask for one of these scope groups, but it should not duplicate Google's literal URLs or independently parse scope strings.

api::Client::new_from_handle can assert that an acquired OAuth handle has at least one required scope before exposing service clients.