docs: correct admin role references across all documentation#31
Merged
pkmaster21 merged 1 commit intomainfrom Apr 20, 2026
Merged
docs: correct admin role references across all documentation#31pkmaster21 merged 1 commit intomainfrom
pkmaster21 merged 1 commit intomainfrom
Conversation
The admin role is not implemented in v1 — memberRoleEnum is ['owner', 'member']. Remove all references to admin as an existing role and update permission descriptions, API table auth columns, and the roles section to reflect the actual two-role model. Note admin as a planned v2 feature.
Deploying tabby with
|
| Latest commit: |
77ca2cb
|
| Status: | ⚡️ Build in progress... |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
memberRoleEnumin the Drizzle schema is['owner', 'member']— there is no admin role in v1. Several docs described admin as an existing, implemented role, which would be misleading to anyone reading the codebase.What was wrong:
DELETE /groups/:id/members/:memberIdas requiringAdmin+— the actual middleware isrequireOwnerdocs/design-spec.mdData Model showedrole (owner | admin | member)in the Member table descriptionDESIGN.mdbadges listed(owner, admin)as badge variantsv*tagWhat was fixed:
docs/FUTURE.md(which already correctly tracks it as a v2 feature)owner | memberv*tag with the full deployment pipeline descriptionDESIGN.mdbadge variant corrected to(owner)onlydocs/FUTURE.mdanddocs/TODO.mdrequired no changes — both were already accurate.