diff --git a/attached_assets/Pasted-Update-the-admin-system-to-support-User-Management-with_1776841000012.txt b/attached_assets/Pasted-Update-the-admin-system-to-support-User-Management-with_1776841000012.txt
new file mode 100644
index 00000000..b7877aa6
--- /dev/null
+++ b/attached_assets/Pasted-Update-the-admin-system-to-support-User-Management-with_1776841000012.txt
@@ -0,0 +1,95 @@
+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
\ No newline at end of file