# Database Structure Summary - Phase 1

## Core Tables
- `users`: authentication identity and account state.
- `roles`: role master data (Super Admin, HR, Project Manager, Developer, Tester, Designer, Employee).
- `permissions`: permission master data for future granular RBAC.
- `role_user`: many-to-many user-role mapping.
- `permission_role`: many-to-many role-permission mapping.
- `employee_profiles`: profile attributes for employees.
- `activity_logs`: user action audit trail.
- `settings`: key-value system settings.
- `notifications`: reusable app notifications (extended with `title`, `read_at`, soft deletes).

## Relationships
- User `belongsToMany` Roles via `role_user`.
- Role `belongsToMany` Users and Permissions.
- User `hasOne` EmployeeProfile.
- User `hasMany` ActivityLogs.
- User `hasMany` Notifications.

## Soft Deletes
- Applied to `roles`, `permissions`, `employee_profiles`, `activity_logs`, `settings`, and `notifications`.
