Skip to main content
All documentation

People, teams and recruitment

Administer staff access, departments, vacancies, applications and referrals while keeping personal data in protected workflows.

Workflow
  1. Choose the people workflowUse Users and Roles for accounts, Departments for team records, and Recruitment for vacancies, questions, applications and referral codes.
  2. Check permission and purposeGeneral admin roles can manage many staff lists; God-only actions exist for selected destructive or archive operations. Use only the access needed.
  3. Update the correct recordConfirm the record and current state, enter required names, status, dates, currency or notes, and avoid copying personal data into unrelated fields.
  4. Save or transitionSave the edit or use the specific status action. A job application status, vacancy publication and user account status are separate state changes.
  5. Verify and protectRe-open the record and confirm the resulting status. Keep application documents, contact details and notes inside their restricted screens.

Users and account status

User Management lists accounts and supports viewing, creating, editing, exporting and selected bulk actions. Status toggling changes whether an account is active; role assignment changes what the account can do and should be reviewed separately. The user detail view can include sensitive profile and financial information. Wallet credits are a distinct financial operation and should follow the commercial process, not routine staff maintenance. Use a verified record and the narrowest change needed.

  1. Search for and open the exact account record using the approved identity check.
  2. Edit only the authorised profile, role or active-state fields and confirm any bulk selection.
  3. Reload the account detail to verify the saved role and status; route wallet adjustments through finance controls.

Roles and permissions

Role Management displays roles and allows authorised staff to edit permission assignments. Use it to review or adjust an existing role, not to infer that a title such as manager grants access to every team record. Privileged capabilities are checked by server policy as well as by sidebar visibility. Changes to a shared role affect every user assigned to it, so check membership and expected access impact before saving.

  1. Open the role and review its current permission set and assigned users.
  2. Compare requested duties with permissions; remove unrelated capabilities and retain required protections.
  3. Save and verify the intended dashboard access with an authorised account, without impersonating a real user to test.

Departments and teams

Departments supports create, edit, detail, preview, export and bulk actions, with ordering and active-state controls. Version rollback, merge, duplication, archive and restore are available for specific cases, with some operations reserved to God. Preview a department before a rollback or merge and check records that may be affected. Merge is not a cosmetic rename: verify the destination and impact before confirming. Use archive rather than deletion where the workflow calls for preserving history.

  1. Open the department list and inspect the status, order and existing version for the target team.
  2. Edit or preview the intended change; use merge or archive only after confirming the target and affected records.
  3. Verify the department page, order and active status after saving or restoring.

Vacancies and application questions

Recruitment manages job categories, positions and their application questions. Position records include public vacancy details and may include salary range, supported salary currency (GBP, USD or EUR), negotiability, vacancy count and deadline. Questions can be added, edited, deleted and reordered. Before making a position live, check that category, location, deadline and application questions are complete and consistent. A disabled or expired position is not available for new applicants.

  1. Choose a category, then create or edit the position with accurate public details and allowed salary currency.
  2. Review each application question for clarity, necessity and order; remove questions that no longer apply.
  3. Toggle the position status and inspect the public vacancy page to confirm availability and deadline.

Applications and candidate records

The applications list and detail pages contain candidate information and supporting files. Staff can update application status, add an internal note and view/download protected media. Status transitions should follow the organisation’s recruitment process; notes must be relevant and professional. Deleting an application is a separate destructive action. Do not export, download or retain candidate data unless needed for the authorised decision and approved retention process.

  1. Open the application record and verify its vacancy and current workflow status.
  2. Update the status or add a relevant note using the dedicated controls; access files only when required.
  3. Return to the application list and confirm the new status while keeping candidate data within the authorised system.

Referrals and employee records

Referral administration lists and edits referral codes and their associated public referrer information. A referral code can be verified by the careers flow, so check the code’s active details and public biography before saving or removing it. The dashboard also supports generation or regeneration of an employee code from the user profile flow; those controls belong to the authenticated account owner and should not be treated as a staff roster editor. This implementation does not expose a general employee directory for arbitrary edits.

  1. Open Recruitment Referrals and inspect the current code and linked public information.
  2. Create or edit a referral using the approved code and accurate biography; remove only obsolete entries.
  3. Verify the referral page or public careers flow, and direct employee-code changes to the owner profile controls.

Frequently asked questions

Is there a general employee directory?

The dashboard has Users, Roles and Departments; employee-code generation is in the profile flow. Do not assume a separate staff roster editor exists.

What currencies can a vacancy use?

The recruitment form accepts GBP, USD or EUR. Use one of those values and verify the displayed salary range.

Can every admin archive a department?

No. Some department archive, restore and duplicate operations are restricted to God.

Where should candidate notes go?

Use the application detail note control and keep notes relevant, professional and limited to the recruitment decision.

Can I remove an application?

The application workflow exposes a separate delete action. Use it only when authorised and consistent with retention requirements.

Does changing a role only affect one user?

No. Editing a shared role can affect all users assigned to it. Review its membership and permission impact first.

Related pages