feat(auth): introduce role-based access control with Roles decorator …#54
Merged
Uyoxy merged 1 commit intostellarspend:mainfrom Mar 5, 2026
Merged
Conversation
Contributor
|
lgtm |
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
2 participants
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.
Summary
Introduces Role-Based Access Control (RBAC) to secure admin-only endpoints.
Changes
Added role field (user | admin) to User entity
Created @roles() decorator
Implemented RolesGuard
Protected admin routes (analytics export, user suspension, system config)
Acceptance Criteria
Admin routes accessible only to admin users
Non-admin users receive 403 Forbidden
@roles() decorator works across modules
How To Test
Login as normal user → access admin route → expect 403
Login as admin → access granted