> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/systems/roles/adding-a-new-permission.md). # Adding a new permission This page describes how to add new permissions into the game To add a new permission into the game go to **Assets/Content/Data/Traits/Identification/Permissions**, right click and go **Create -> Inventory -> Traits -> Permission**, just name it accordingly. To add the permission into a role, just add it to the Role Data's permission list ![](https://3495811604-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F95OhrYYgKj0eUTnfM9sL%2Fuploads%2FGQZXgVn49IAreIhUqYwD%2Fimage.png?alt=media\&token=cebcf242-1313-4b46-85d8-02ffffee6cb8) This permission can be checked inside of a script throught the Inventory class, by using the **HasPermission** function. \ \ For example, the Security Locker currently checks for a **Security** permission to be both locked and unlocked. the **Unlock Locker** interaction checks for the permission by getting the player's inventory:

Here we get the player's inventory through the hands that executed the interaction, with it we have access to the HasPermission function, we then check if it has the "permissionToUnlock" permission.

The permissionToUnlock field is set via the inspector.

--- # 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, and the optional `goal` query parameter: ``` GET https://ss3d.gitbook.io/systems/roles/adding-a-new-permission.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.