TotalApp Docs
Ctrl K
EN | TR
Go to App

Staff & Multi-Hat Assignment

Assign roles to employees, let one person wear multiple module "hats", and auto-grant a role's capabilities the moment it's assigned.

Auto-Granting Capabilities

When you add or edit a person on an add-on's Staff screen and select a role, the role's capabilities are automatically attached to that employee as a domain "hat" — you don't have to send them to HR to grant permissions separately.

Add staff on /legal/staff → Pick role "Senior Partner" → Capabilities auto-attached → Person can access Legal

One step, not two

Assigning a role is the single action that both places the person on the team and grants them the module's permissions. Removing them from the team revokes that module's hat.

The Multi-Hat Scenario

A single person can hold roles across several modules at once — for example Legal: Senior Partner and Healthcare: Advisor. This is what the + Add Existing Employee button is for.

A person appears on a module's Staff screen when they hold a role in that module — not because of their HR department. Adding someone never changes their department, and a role is required to join a team.

  1. On the add-on's Staff screen, click + Add Existing Employee.
  2. Search and select a person who already exists in the company directory. The list shows only people who do not yet hold a role in this module.
  3. Assign them a role in this module. With Quick add (the default) you pick the role in the list and click Add to team; with Full form the person's details open on the roles tab and you save there. Choose between them in Settings → Preferences → Staff screens.

No duplicate records

Adding an existing employee to a second module does not create a new employee record — it attaches the new module's role/capabilities to their single profile. Their hats accumulate across domains.

Capabilities vs. Skills — Two Tabs

On a person's profile these are kept deliberately separate:

Capabilities tab

Shows the active module roles & capabilities the employee holds across domains (e.g. Legal: Senior Partner, Healthcare: Advisor). This drives access.

Skills tab

Personal, operational competencies managed by HR (Python, Laparoscopy, Contract Law). Used for search/matching — it does not affect access.

Lite vs. Full Employee Modal

The employee form adapts to where you open it from:

WhereModalTabs shown
HR (Organization / Employees)FullAll tabs — General, Work, Capabilities, Permissions, Skills, Certifications, Payroll, Assets, Documents
Add-on Staff (/{domain}/staff)LiteOnly General, Work, and the module's Roles & Capabilities tab (Payroll / Assets / Skills / Documents hidden)

The Lite modal keeps an add-on manager focused on the fields that matter to their team, while HR retains the complete record.

Removing Someone from a Team

Removing a person from an add-on's Staff screen only detaches that module's hat (your HR department is left as it is). The underlying employee record, their other modules' hats, and their HR history are never deleted.

Frequently Asked Questions

If I add someone who already works here to a second module, do I create a duplicate?
No. Use + Add Existing Employee — it attaches the new module's role to the existing person, so their hats accumulate without a duplicate record.
Do I need to visit HR to grant permissions after adding staff?
No. Selecting a role on the add-on Staff screen auto-grants that role's capabilities immediately.
Why can't I see Payroll or Documents tabs on the add-on staff form?
Add-on staff screens use the Lite modal by design. The full record — including Payroll, Assets, Skills and Documents — lives in HR.