Folder-scoped read-only service accounts or automation tokens for Proton Drive
Please support non-human automation identities for Proton Drive.
A service account or token should be:
- restricted to one explicitly shared folder and all descendants;
- read-only or read/write according to granted scope;
- unable to enumerate or access other Drive areas;
- revocable independently from a human user account;
- usable non-interactively by approved automation;
- auditable as a distinct automation identity;
- manageable with expiration and rotation.
Use case:
Scheduled inventory, backup verification, metadata comparison, compliance checks, and integrity monitoring without using a person’s primary Proton account or retaining a browser-authenticated session on an unattended system.
Current workaround:
Create a separate Proton account and share one folder with it. This is not equivalent to a service account because it still requires a normal Proton account, browser login, session storage, and account-level security management.