Manage Staff, Roles, and Branch Operations

/admin/staff is the starting point for user administration. It is used to invite staff, assign roles, define branch context, and review staff-specific activity. The page is currently split into Staff and Departments.

What the Staff Area Handles

• staff search
• branch filtering
• role filtering
• new staff invitation
• detail viewing and editing
• staff-specific recent activity review
• department management

Read the Staff List

The list typically shows:

• profile
• role
• license number
• branch
• joined date
• status

Veterinarian roles may show license data directly, so hospitals that care about clinical accountability should maintain that field carefully.

Invite a New Staff Member

Step 1. Enter the basics

• name
• email
• phone number

Step 2. Assign the role

Core role values include:

• super_admin
• admin
• vet
• manager
• receptionist
• staff

Step 3. Assign the branch

In multi-branch environments, branch assignment directly affects context and available work.

Tabs Inside the Staff Detail View

Within the Staff tab, the detail sheet usually exposes:

• Profile
• Permissions
• Activity

Profile

• name, email, phone
• role
• license data
• primary and assigned branches

Permissions

The current implementation behaves more like a summary or review tab than a full field-level RBAC editor. In practice, role and menu rules still drive most access.

Activity

This tab pulls recent activity logs from the audit log API for the selected user.

Departments

The Departments tab inside /admin/staff is where teams create department names, descriptions, membership, and active or inactive status.

Practical Role Guidance

admin

• admin menu access
• hospital settings, audit, integrations, and master data

vet

• clinical and treatment-centered work
• not normally the primary admin persona

receptionist / staff

• reception, appointment, and day-to-day operations

super_admin

• broadest operating authority

Branch Management Notes

• If the user's default branch and actual working branch are different, data can be entered under the wrong context.
• Multi-branch hospitals should define explicit branch switching and responsibility rules.
• Different facility enablement by branch can change what the same role can actually do.

When to Review Activity

• when a configuration change was made incorrectly
• when a data issue started after a specific point in time
• during offboarding or account deactivation

Practical Tips

• Keep role names standardized instead of reinterpreting them locally.
• Audit veterinarian accounts regularly through license and activity review.
• If access problems happen often, maintain Roles and Access Matrix as an internal reference.

Related Docs

• Configure Hospital Settings and Integrations
• Use Audit Logs
• Roles and Access Matrix