> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/fabric-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/fabric-knowledge-base/learn-the-application/destinations/preferences/users/utilising-security-levels.md).

# Utilising Security Levels

Security levels allow for further security across the catalog by restricting access to certain records based on their security level. Records are assigned a number, from 1 to 10, to determine their security level. In preferences, individual users are also assigned a security level to determine which records they can access. 

#### <img src="https://1453363788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPS7xvtVOuEwjKjl1m1Xs%2Fuploads%2FOpEILM9nwAhK3j2lM3BT%2FScreenshot%202024-04-23%20at%2010.50.14.png?alt=media&amp;token=9c0f7470-d4a7-4f74-b5e1-629fd0cf896e" alt="" data-size="line">  User Security Levels

Level 10 is the lowest level, with access to records with Security Level 10 only.\
Level 1 is the highest level, with access to all records (Security Levels 1 to 10).\
\
Level 2 gives access to records in Levels 2 to 10.\
Level 3 gives access to records in Levels 3 to 10, and so on.

### :key:   How to assign a security level to users and records

Fabric Studio’s Security Levels feature provides a scalable, user-centric way to control data access. By default, new records inherit the creator’s own, most restrictive security level. From there, users with appropriate permissions can adjust the record’s security level to ensure that sensitive content remains secure and accessible only to authorised individuals.&#x20;

By assigning the Creators most restrictive level by default, you reduce the risk of accidentally exposing confidential or sensitive information. It’s easier to dial permissions back and open access later, rather than try to contain a breach after the fact.

{% @arcade/embed flowId="WPDrRrwKyzORAnFUL62Z" url="<https://app.arcade.software/share/WPDrRrwKyzORAnFUL62Z>" %}

Best Practices

• Set a Restrictive Default: Leave the default security level as is for new records, then raise or lower it only when you’re sure who needs access.

• Review Access Regularly: Periodically review and adjust security levels to align with changes in team roles and responsibilities.

***

<details>

<summary>Related Articles</summary>

* [Role Management](/fabric-knowledge-base/learn-the-application/destinations/role-management.md)
* [Preferences](/fabric-knowledge-base/learn-the-application/destinations/preferences.md)
* [<mark style="color:blue;">Account</mark>](/fabric-knowledge-base/learn-the-application/destinations/account.md)

</details>

> We hope you found this article helpful.&#x20;
>
> If you have a technical problem that this article does not address, go to [<mark style="color:blue;">service desk</mark>](/fabric-knowledge-base/support/service-desk.md)<mark style="color:blue;">.</mark>
>
> Help us improve the Fabric Knowledge Base by giving feedback here: [FKB Feedback Form](/fabric-knowledge-base/feedback/fkb-feedback-form.md)