Possession
- Dominant language
- Kotlin
- Stars
- 25
- Forks
- 6
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 9
Description
US: As a SUPERUSER user I want to change my session to someone I select from a list to see how they might see the admin panel or the frontend.
AC:
- Have an option to "possess" users.
- Make sure the audit log shows the real user (eg. User Admin - as Possessed User)
- Have an option to change it back to the original user
- Optional: Have an option for regular admins to use it if they have the right somehow.
NOTE:
Might want to create a new User for that.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the admin-panel/frontend user-selection flow, session handling, and audit-log entry points; the issue names no files or tests. Define the possession and return flows, access rules, and audit identity behavior against the acceptance criteria, including whether regular-admin access and a separate User are in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, react, spring-boot
- Domain
- authentication, authorization, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100