Access Rules

OAuth grants broad read-only provider access.

Index Lane then applies a second layer: saved access rules.

Those saved rules are the hard boundary used by:

• the web app
• the CLI
• the local MCP server

Why provider-native rules matter

Index Lane stores provider rules in the provider’s own language whenever possible.

Examples:

• Gmail: label IDs or native Gmail query syntax
• Google Drive: folder IDs, shared drive IDs, file IDs
• Calendar: calendar IDs
• Notion: page or database IDs when available

That makes the system:

• easier to debug
• closer to the provider model users already understand
• less likely to drift into an abstraction that behaves differently from the real API

Gmail examples

{"mode":"all"}

{"mode":"recent","recentDays":30}

{"mode":"labels","labelIds":["IMPORTANT","INBOX"]}

{"mode":"query","q":"label:important newer_than:30d"}

Drive examples

{"mode":"all"}

{"mode":"selected","folderIds":["folder-123"],"sharedDriveIds":["drive-456"],"fileIds":[]}

Calendar examples

{"mode":"selected","calendarIds":["team-calendar-id"]}

Notion examples

{"mode":"selected","selectedIds":["page-id","database-id"]}