gmail.settings.basic scope missing from auth login scope picker — cannot create Gmail filters

Open Beginner friendly
#668 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust

Research direction

Start at the scope definitions and selection flow used by gws auth login; the issue does not name a file or test. Reproduce the login scope picker and then run the documented gws gmail users settings filters create command. Done means gmail.settings.basic is selectable or included with gmail.modify, and the filter command no longer fails for insufficient authentication scopes.

Written by the indexing model from the issue text.

Description

Description

The gmail users settings filters create command exists in gws and is correctly documented, but it cannot be used because gmail.settings.basic is not available as a selectable scope in gws auth login.

Steps to reproduce

  1. Run gws auth login — the scope picker shows 9 scopes, Gmail is represented only by gmail.modify
  2. Authenticate with all available scopes selected
  3. Run:
    gws gmail users settings filters create --params '{"userId": "me"}' --json '{"criteria": {"from": "example@domain.com"}, "action": {"addLabelIds": ["Label_1"]}}'
    
  4. Receive:
    {"error": {"code": 403, "message": "Request had insufficient authentication scopes.", "reason": "insufficientPermissions"}}
    

Expected behaviour

gmail.settings.basic should be available in the scope picker (or included alongside gmail.modify), so that users.settings.filters.* commands work.

Environment

  • gws version: latest
  • OS: macOS (darwin 25.4.0)
  • Account type: personal @gmail.com
Dominant language
Rust
Stars
31.1k
Forks
1.8k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleworkspace/cli

All issues in googleworkspace/cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.