Channel-Based Rank/Authorization #12
Labels
No labels
Bug
Cleanup/Refactor
Core Feature
Documentation
Feature
Performance Improvement
Security Improvement
UX/Accessibility
Unreproducable Bug
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: rainbownapkin/canopy#12
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Including UI on channel settings page to manage channel ranks
added #6 as parent issue
changed the description
Started work on implementing channel based rank/permissions:
8384e732f3Added channelPermissionSchema and api routes to get/set channel permissions.
Channel rank, permissions checks, or auth middleware yet to be implemented.
Added channel overrides section to adminPanel page:
33026a1265Started work on chan rank, new channels start with founding user as admin. '/api/channel/rank' route added to get user rank list based on channel name:
057537341aChannel Rank/Auth back-end components now functional. Chan Ranks/Perms can only be set by those authorized by channel. Chan auth middleware written. Chan rank now injected into connectedUser object under activeChannel:
61fab57a6dStill need to implement channel rank/perms frontend in chan settings page, as well as dedicated perms for "change rank" and "change perm" both in site-wide and chan perms.
Channel rank and authorization frontends finished, among other improvements to channel settings page:
796bb033a7