> For the complete documentation index, see [llms.txt](https://help.sequorplatform.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sequorplatform.io/documentacao/documentation-en/registrations/registrations-backoffice/skills-registration.md).

# Skills Registration

#### Skill Management in Sequor MES

The **Skills Registration** aims to record and organize the **technical competencies, certifications, and qualifications** necessary to carry out production activities within Sequor MES.

This information is used in the registrations of **People** and **Teams**, ensuring that only properly qualified employees perform specific operations.

#### Purpose of the registration

Standardize the control of **qualifications, certifications, and mandatory training**, promoting safety, traceability, and compliance with internal standards and labor regulations (such as NRs).

With skills registration, it is possible to:

* Register and classify different types of skills;
* Define which certifications require supporting documentation;
* Control the active/inactive status of each skill;
* Make it easier to link skills to people and teams.

> 💡 **Tip:** keep skills always updated as new training or technical standards are implemented.

## 1. Access to the module

In the Sequor MES main menu, go to:\
**Registrations → Skills**

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FvdmJ3m8y9iztU2sV0vWN%2F1%20-%20Icone.png?alt=media&amp;token=616147bf-5b74-4686-9544-492e58fe5c7a" alt=""><figcaption><p>Skills Registration Icon</p></figcaption></figure>

### 1.1. Initial listing screen

When accessing Skills Registration, the main screen provides an overview of all skills registered in the system.

| Field              | Description                                                                                       |
| ------------------ | ------------------------------------------------------------------------------------------------- |
| **Skill Category** | Group or classification to which the skill belongs (e.g.: NRs, Driver’s License, Certifications). |
| **Skill**          | Name of the skill or certification (e.g.: NR10, Driver’s License Type B).                         |
| **Description**    | Additional details about the skill.                                                               |
| **Status**         | Indicates whether the skill is active and available for use.                                      |

At the bottom of the screen, the **total number of records** and the **loading time** of the query are displayed.

> ⚙️ **Tip:** use the search filter to quickly locate specific skills, especially in environments with a large volume of records.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FvzxcJoaC828ObtLiRpB9%2F2%20-%20tela%20criteria.png?alt=media&amp;token=e1154a2f-c6b6-4a05-a75e-40046658c56b" alt=""><figcaption><p>Criteria screen - Skills Registration</p></figcaption></figure>

#### Action buttons

In the upper right corner of the screen, the main actions are available:

| Icon | Function                |
| ---- | ----------------------- |
| ➕    | **Add new skill**       |
| ✏️   | **Edit existing skill** |

> ⚠️ **Attention:** avoid deleting skills that are already linked to people or teams — this may impact traceability and qualification reports.\
> Prefer using the status **Inactive** to keep the history.

## 2. Tab **General**

The tab **General** concentrates all the skill registration fields.

| Field                        | Description                                                                                               |
| ---------------------------- | --------------------------------------------------------------------------------------------------------- |
| **Skill Category**           | Defines the group to which the skill belongs (e.g.: NRs, Licenses, Internal, etc.).                       |
| **Skill**                    | Name of the skill or certification.                                                                       |
| **Description**              | Brief explanation or detail about the skill content.                                                      |
| **Mandatory Document**       | Defines whether the skill requires an attachment of proof (e.g.: scanned certificate, license, document). |
| **Status (Active/Inactive)** | Defines whether the skill is enabled for selection in the People and Teams registrations.                 |

> 💡 **Tip:** use the option **Mandatory Document** for regulated certifications, such as NR10, NR12, NR18 and others that require formal proof.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2F6qB3JMvovG9ZkxvyuceG%2F3%20-%20aba%20geral.png?alt=media&amp;token=9e2435c5-36fd-4a76-aa11-5a5e741a91c0" alt=""><figcaption><p>General Tab - Skills Registration</p></figcaption></figure>

## 3. Best practices

* Use standardized categories to organize skills (e.g.: **NRs**, **Operational**, **Internal**, **Safety**).
* Periodically review the status of skills and **deactivate** those that are no longer applicable.
* For internal audits, keep the **mandatory skills with supporting document attached**.
* Always link the correct skills to **people and teams registrations**, ensuring complete traceability.
