docs(spec): presets have no access control of their own

Preset routes need no RBAC permission; a submit made from a preset is
checked like any other submit.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-10-13 03:33:25 +00:00
parent e48d36054d
commit 7382e94d24
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
2 changed files with 12 additions and 8 deletions

View file

@ -654,8 +654,9 @@ defaults a profile does not (everything but default reservations):
into its own local file, so a server preset being removed never affects
users. `preset diff` / `pull --force` are user-initiated.
- User-to-user sharing by `preset export` / `import` (file, mail, git).
- Presets carry no privilege: `queue:submit` (later `app:use`), the profile's
essentials, queue ceilings and project quotas still apply at submit.
- Presets have no access control of their own (user, 2026-10-12): the
preset routes need no RBAC permission, and a submit made from a preset is
checked like any other submit. Presets carry no privilege.
### Dispatch record
Decided 2026-10-12 (user): what a job was scheduled and started with is