Proton Drive CLI authenticates only via full user login. No scoped tokens, no service accounts. This prevents secure automation use cases like server backups.

Business customers need:

Scoped API tokens with folder-level access restrictions
Service accounts that don't consume user seats
OAuth2 with granular scopes (read-only, folder-specific)

Current workaround (dedicated user account) forces paying for an unused seat just to isolate access. (Or free accounts)

Security professionals and sysadmins need isolated identities for automation without exposing the full account.