SUBTASK #86: Manage user accounts (admin)
Maintainers usually reply within 1 day
@Edgeless6 is already working on this.
Since Nov 2, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, python
- Domain
- authorization, backend, frontend
Research direction
Start in backend/services/access_control/access_control_service.py to add set_role, set_status and reset_password, each passing changed_by to UserStore.store, then read the tests in tests/services/access_control/. The API routes come from #50, and the Users page is frontend/app/src/pages/UsersPage.jsx. Done means a new viewer can sign in but not change anything, a disabled user gets 401 on their next request, and the audit log names the admin for each change. This issue depends on #89, #90 and #91, which are not yet finished, so check those first.
Written by the indexing model from the issue text.
Description
What to do
Let an admin list accounts, add one, change a role, disable or re-enable an account and reset a password, through the API and a Users screen. Let every user change their own password.
Background
- Spec SEC-03, POL-01, POL-02, CP-02
UserStore.store(user, changed_by)audits every change with the admin who made it, and records a password change as{"password_changed": true}, never the hash (#17)- Sessions reload the user on every request (subtask 4), so changes take effect on that user's next click
Steps
-
AccessControlService:set_role,set_statusandreset_password, each withchanged_by=the admin - Safety rules, each refused with a reason:
- An admin can't disable or demote themselves
- The last active admin can't be disabled or demoted (otherwise nobody could manage accounts again)
- API, every route
@requires(Permission.MANAGE_USERS):-
GET /api/users -
POST /api/userswith{username, password, role} -
PUT /api/users/<id>/role,PUT /api/users/<id>/status,PUT /api/users/<id>/password
-
-
PUT /api/me/passwordwith{current_password, new_password}for any signed-in user - Users screen at
/users, shown in the menu only to admins:- A table of username, role and status
- An add-user form, a role picker, Disable / Enable, and Reset password
- A Change password form in the header menu for every user
- Unit tests:
- Self-demotion and the last admin rules
- An editor gets 403 on every
/api/usersroute - Each change makes an audit entry naming the admin
- No response contains a hash
- A disabled user's next request gives 401
Where
backend/services/access_control/access_control_service.py- The Application Controller routes from #50
frontend/app/src/pages/UsersPage.jsx, and a change-password form in the headertests/services/access_control/andtests/controller/
Done when
- An admin can add a viewer, who can sign in and browse but not change anything
- Disabling that viewer signs them out on their next click
- The audit log shows each account change with the admin who made it
- All unit tests pass without a database
Depends on
- Sign in and account rules (#89), Sessions and route protection (#90), Login screen (#91)
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 8h 51m
- Merged PRs (30d)
- 39
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Bearkat-Professionals/Software-Engineering-Project
-
bug frontend help wanted High Priority
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Bearkat-Professionals/Software-Engineering-Project#98 ·
Maintainers usually reply within 1 day
-
SUBTASK #86: Password hashing (BB-5)Possibly taken @Edgeless6 claimed this 4 days ago. Openbackend Medium Priority subtask
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Bearkat-Professionals/Software-Engineering-Project#87 · 1 assignee ·
Maintainers usually reply within 1 day
-
Enhancement: Regression tests for Validate Input crash fixes (SH-1)Possibly taken @yoshi301 claimed this 3 days ago. Openbackend Low Priority
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Bearkat-Professionals/Software-Engineering-Project#59 · 1 assignee ·
Maintainers usually reply within 1 day
-
backend bug help wanted High Priority
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Bearkat-Professionals/Software-Engineering-Project#97 ·
Maintainers usually reply within 1 day
-
SUBTASK #86: Login screen and signed-in layoutPossibly taken @Solo-Her0 claimed this 4 days ago. Openfrontend Medium Priority subtask
Difficulty 4/5 3-5 days Newbie friendliness 28/100
Bearkat-Professionals/Software-Engineering-Project#91 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in Bearkat-Professionals/Software-Engineering-Project
Similar issues
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
strawberry-graphql/strawberry#4794 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dataforgoodfr/cetolog#21 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
btclib-org/btclib#2932 ·
Maintainers usually reply within 1 day