> For the complete documentation index, see [llms.txt](https://cleyrop.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cleyrop.gitbook.io/docs/documentation-fr-en/data-governance/permissions-dacces-aux-donnees.md).

# Data access permissions

Access permission management allows **Platform Managers** to control projects' access to sensitive or restricted datasets and data sources.

This governance ensures that only authorized teams can use potentially confidential data, while maintaining traceability and justification for each decision.

***

## Request access

When a user or project wants to access a Data Source or Dataset classified *sensitive* or *restricted*, an approval request is automatically generated.

This action can be performed directly from:

* The Catalog page, by clicking on **Add to a project** from the Dataset details page.
* The project library (for a dataset or a Datasource), by clicking Request access in the desired resource.

This request must be approved by a Platform Manager before access is granted.

Once the request is submitted:

* It is automatically sent to the resource owner or the Platform Manager for validation.
* A notification is displayed in the requester's notification center indicating that the request is being processed.
* The request status changes to *Pending approval* until a decision is made.

Access requests are centralized in a table listing:

* Resource type (Dataset / Datasource)
* Resource name
* Requesting project
* Status (Pending / Accepted / Rejected)
* Request date

## Approve or reject a request

When an access request is created: a **notification** appears in the Platform Managers' notification center.

Only the **Platform Managers** can manage requests. To approve or reject an access request:

1. Go to Administration → Permissions.
2. Select the request from the list.
3. Click **Manage the request**.
4. Choose Accept or Reject.
5. Add a **justification** explaining your decision (optional but recommended).

{% hint style="warning" %}
All **project members** current and future will have access to the validated data sources and datasets
{% endhint %}

Once the request is processed:

* The requester receives a notification and a confirmation email.
* The resource status is updated in the relevant project and becomes available for use by all members.

## History and traceability

All governance actions are tracked in the History tab of the *Approval management*.

Each history row contains:

| Request ID          | Unique identifier of the request.          |
| ------------------- | ------------------------------------------ |
| Resource type       | Dataset or Datasource.                     |
| Resource name       | Full name of the data concerned.           |
| Project / requester | Project that initiated the request.        |
| Date                | Creation and decision date.                |
| Status              | Accepted / Rejected.                       |
| Justification       | Comment left during approval or rejection. |

By clicking the icon <i class="fa-circle-info">:circle-info:</i>, it is possible to display the full request details, including:

* The exact subject of the request (project name, targeted resource).
* The justification provided by the approver.
* The name of the decision-maker and the validation date.

***

### Governance best practices

* **Justify** your decisions systematically to ensure full traceability.
* Regularly monitor the **notifications** to avoid project blockages.
* Maintain consistency between the **sensitivity policies** and the **approvals**.
* Designate a **primary approver by domain** (HR, Finance, Production, etc.) to streamline management.