Skip to content

v0.5.2

Choose a tag to compare

View all tags
@FalconiZzare FalconiZzare released this 16 Oct 05:55
v0.5.2
db5a59b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Members of a disabled organization can no longer manage its invites. App admins still can.

Fixes

  • Platform controls: Disabling an organization already blocked new invites and redemptions, but its owners and admins could still manage the invites it had already sent. They could list them (with invitee emails), read seat usage, resend one with a fresh token, revoke it, or delete it. These calls now fail with ORG_DISABLED:
    • invite.list
    • invite.org.usage
    • invite.resend
    • invite.revoke
    • invite.delete
  • Someone outside the org still gets ORG_INVITE_NOT_ALLOWED, so they can't tell whether the org is disabled.
  • App admins can still list, revoke, and delete a disabled org's invites while they look into it. See Platform controls.

Migration notes

No schema changes, no new error codes, and no response-shape changes. If your UI lets org members manage invites, handle ORG_DISABLED on these calls the same way you already do at create and redeem.

Full changelog: v0.5.1...v0.5.2

Assets 2
Loading