# Create administrators from the staff workspace

Sign in as staff, then open User Accounts & Security Logs and choose Add account and select Administrator. Enter the full name, email, active campus, password and matching password confirmation. After creation the account appears in the refreshed account list. The administrator signs in with their email and assigned password. Share credentials securely; they can change their password from My Profile.

Only authenticated staff may call this action. It uses the existing CSRF validation, validates active campus and unique email/username, hashes passwords and creates the user and administrator campus record in one transaction. Passwords are not returned in the API response or audit message. No email delivery is implied. The account page now correctly displays accounts instead of accidentally selecting audit records.

No SQL migration is required. Apply shared/api/module.php, shared/lib/admin_accounts.php, shared/js/module.js and shared/views/module_shell.php, or the full package preserving local configuration and uploads. Refresh with Ctrl+F5.

Automated checks cover validation, hashing, successful inserts and rollback on invalid campus, duplicate accounts and failed administrator-profile insertion. These use a database test double; a live XAMPP database was not available here.

## Staff accounts
Accounts → Add account now offers Administrator or Staff. Staff accounts additionally require a unique staff number and active department; designation is optional. Department names are resolved on the server from the selected department. Both types require active campus, name, email and matching passwords. Staff details are created atomically with the login record. No new SQL required.

## Global staff access (current behaviour)
Staff accounts automatically use All campuses and All departments. New staff records store NULL campus and department rather than inventing IDs. Administrators still require a specific active campus. Existing staff gain global guideline browsing and department-file access without changing their stored employment details. Staff see published campus notifications and broadcast departmental notifications across the system; personal messages to other recipients remain private. Staff account creation remains staff-only, and collaboration project membership rules are retained. No SQL migration is needed.
