30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
# 01 Admin and User Management Foundation
|
|
|
|
## Goal
|
|
|
|
Turn the existing starter authentication setup into the first KanbanGit user foundation with an application-level admin role and an admin-only user management area.
|
|
|
|
## Requirements
|
|
|
|
- Reuse the existing Laravel Fortify and Inertia authentication foundation instead of replacing it.
|
|
- Introduce an application-level admin capability that is evaluated separately from project permissions.
|
|
- Provide an admin-only area where admins can:
|
|
- list users
|
|
- view basic user information
|
|
- change whether a user has admin access
|
|
- Prevent non-admin users from accessing admin-only pages and actions.
|
|
- Keep the implementation ready for later team and project permission features.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- An authenticated admin can open a user management screen and manage admin access for users.
|
|
- A non-admin authenticated user receives a forbidden response or redirect when trying to access admin management routes.
|
|
- The code does not hard-code project permission logic into the user model in a way that would block future team-based permissions.
|
|
|
|
## Out of Scope
|
|
|
|
- Team management UI
|
|
- Project permission assignment UI
|
|
- Invitation flows
|
|
- Audit logs for admin actions
|