riyadhafraa
a772607636
Replit-Commit-Author: Agent Replit-Commit-Session-Id: 77cfe984-2c65-4152-bb7a-0df28274fe66 Replit-Commit-Checkpoint-Type: full_checkpoint Replit-Commit-Event-Id: 025835eb-6650-4735-a92c-18a34e17ee07 Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/c3c252e4-c83d-40ca-9fff-99a3ea60701e/77cfe984-2c65-4152-bb7a-0df28274fe66/VRpzQEA Replit-Helium-Checkpoint-Created: true
95 lines
2.1 KiB
Plaintext
95 lines
2.1 KiB
Plaintext
Update the admin system to support User Management with submenus:
|
|
- Users
|
|
- Groups
|
|
|
|
Requirements:
|
|
|
|
1. Admin menu structure:
|
|
Inside User Management, create two submenus:
|
|
- Users
|
|
- Groups
|
|
|
|
2. Users page:
|
|
Create a proper users management page that includes:
|
|
- list all users
|
|
- search/filter by:
|
|
- name
|
|
- username
|
|
- email
|
|
- group
|
|
- active/disabled status
|
|
- create new user
|
|
- edit user
|
|
- activate/deactivate user
|
|
- delete user
|
|
- assign one or more groups to the user
|
|
|
|
Display in users table:
|
|
- full name
|
|
- username
|
|
- email
|
|
- preferred language
|
|
- active status
|
|
- groups
|
|
- actions
|
|
|
|
3. Groups page:
|
|
Create full group management:
|
|
- create group
|
|
- edit group
|
|
- delete group
|
|
- search groups
|
|
- show group name
|
|
- description
|
|
- number of users
|
|
- allowed apps
|
|
|
|
Each group must support:
|
|
- name
|
|
- description
|
|
- assigned users
|
|
- assigned apps
|
|
|
|
4. Access model:
|
|
Users should get access to apps based on their group assignments.
|
|
Do not rely only on individual user roles.
|
|
Support one user belonging to one or more groups.
|
|
|
|
5. Database:
|
|
Add tables if not already present:
|
|
- groups
|
|
- user_groups
|
|
- group_apps
|
|
|
|
Suggested structure:
|
|
- groups: id, name, description, created_at, updated_at
|
|
- user_groups: user_id, group_id
|
|
- group_apps: group_id, app_id
|
|
|
|
6. Business use case:
|
|
We want to create a group called "TeaBoy" that receives service orders only.
|
|
There may be multiple groups in the future.
|
|
Example:
|
|
- TeaBoy group can access incoming orders app
|
|
- Admin group can access full admin system
|
|
- other groups can access different apps
|
|
|
|
7. UI:
|
|
- Arabic-first
|
|
- RTL friendly
|
|
- clean admin layout
|
|
- use clear labels for groups and applications
|
|
|
|
8. Important:
|
|
- show group membership clearly in user details
|
|
- show app access clearly in group details
|
|
- make this scalable for future groups and apps
|
|
|
|
After implementation, provide a precise report:
|
|
1. files changed
|
|
2. database tables added/updated
|
|
3. pages added
|
|
4. API endpoints added
|
|
5. how group-to-app permission works
|
|
6. how users are assigned to groups
|
|
7. what still remains incomplete |