> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/people/dashboard-actions/manage-staff-and-organisational-configuration.md).

# Manage Staff and Organisational Configuration

Use the **Manage** actions in the People section to update and maintain staff records, scoping logic, onboarding workflows, background verification systems, and custom fields.

***

### 1. Manage Staff Information

You can view and update staff details directly in the **Staff** tab, depending on how the staff were added.

#### If added via HRMS:

* Staff details are managed in the HRMS.
* Fields like reporting manager, role, and joining date cannot be edited in Sprinto.
* To make changes, go to the HRMS and sync updates into Sprinto.

#### If added manually:

* Staff records can be edited within Sprinto.

1. Click on a staff member’s name.
2. Use the **Edit** buttons to update:
   * Personal details
   * Custom fields
   * Scope status
   * Reporting manager or job role

***

### 2. Manage Staff Scope

Use **Smart Scoping** or manual controls to define who is in scope for your security programme.

#### To manage scoping:

1. Go to **People > Configuration**.
2. In the **Mark staff as in scope** section, select one:
   * **All staff are in scope**
   * **Use smart scoping by staff groups**

If using smart scoping:

* Click **Select staff groups**.
* Choose specific groups that must be marked as in scope.
* All others will be marked as out of scope.

{% hint style="info" %}
You can also change scope for individual staff in the **Staff** tab.
{% endhint %}

***

### 3. Manage Org Chart Source

Choose whether to auto-generate the org chart or upload it manually.

#### To manage org chart:

1. Scroll to the **Org chart** section in **Configuration**.
2. Click **Manage**.
3. Choose one of the following:
   * **Auto-generate using reporting manager information**
   * **Periodically upload a chart** (with evidence and frequency)

***

### 4. Manage Onboarding Settings

The onboarding email is triggered once training, policies, and device tracking are configured.

#### To manage onboarding:

1. Go to **Staff onboarding** section in **Configuration**.
2. Complete all prerequisites:
   * Map training programmes
   * Assign policies
   * Configure device tracking
3. Click **Manage** to preview the onboarding email format.

***

### 5. Manage Background Verification Systems

You can manage connected BGV systems and manually upload reports when required.

#### To manage BGV providers:

1. Scroll to **Background verifications**.
2. Click **Manage**.
3. To remove or update an integration, click **Edit** next to the provider.

#### To upload BGV reports:

1. Go to an individual staff profile.
2. Click **Add report** or **Update report** under Background Verification.
3. Upload the relevant document and submit.

***

### 6. Manage Custom Fields

Custom fields help capture additional data per staff member.

#### To manage custom fields:

1. Scroll to **Custom Fields** in **Configuration**.
2. Click **Manage**.
3. You can:
   * Edit field names or types
   * Enable or disable fields
   * Reorder or delete fields (if not used)

{% hint style="info" %}
You can also access global field settings via **Settings > Custom Fields**.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sprinto.com/data-library/people/dashboard-actions/manage-staff-and-organisational-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.