Skip to content

fix(docs): the shipped admin sets no longer carry the export wildcard #235

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-zhuang merged 2 commits into from
Aug 29, 2026
Merged

fix(docs): the shipped admin sets no longer carry the export wildcard #235

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
faff1a3
fix(docs): the shipped admin sets no longer carry the export wildcard
claude Aug 29, 2026
dc33caf
fix(docs): drop the unsourced "not overridable" clause from the expor…
claude Aug 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions content/docs/configure/permissions/permission-sets.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,10 +70,18 @@ objects: {

Three consequences worth planning for:

- **Package-shipped sets are re-seeded on upgrade**, so
`admin_full_access` and `organization_admin` carry `allowExport: true`
for you. **Environment-authored sets are not** — edit any custom set
whose users export.
- **No shipped set carries the grant — the upgrade is what takes it
away.** Package-shipped sets are re-seeded on upgrade, and since
ObjectStack 17.1 `admin_full_access`, `organization_admin` and the
derived `organization_admin_no_bypass` no longer grant export on the
`*` wildcard. There is deliberately no automatic replacement: export
is granted per object, in an app's own permission set. Grant
`allowExport` explicitly wherever admin export is intended, in a set
you author. **Environment-authored sets never carried it either** —
edit any custom set whose users export. Nothing fails at parse time,
so an upgrade that edits nothing is valid metadata whose
administrators have quietly lost export on every object no app set
names.
- **`member_default` deliberately does not carry the grant**, so ordinary
authenticated users lose export until an admin grants it. That is the
point of the flip, not an oversight.
Expand Down