> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-hermes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/security-roles/knowledge-management-security-roles/knowledge-management-security-role-content-access-tab.md). # Knowledge Management Security Role: Content Access Tab Within the Knowledge Management Security Role, you can list all the Knowledge Profiles created on the system and identify whether Analysts with this security role can create or update knowledge entries with a given profile. {% hint style="info" %} ### Before you start You must have **Security Roles setup** selected in the Admin tab of your own **General Access security role** before you can assign or remove permissions for any security roles. {% endhint %} 1. Display the Knowledge Management Security Role details window, if it is not already on screen. 2. Select the **Content Access** tab. 3. **Content Access Security** is deselected by default and the role has access to all knowledge profiles. Select the option to restrict the security role to creating/updating particular knowledge profiles. 4. To add a profile to the role (that is, enable Analysts with the role to access the profile), select it in the **Select Profiles** table. 5. Select **Add to List**. 6. Set the access type for the form, by checking the appropriate tick box. 7. To enable permissions for a profile, select **Author** or **Editor**:
Author

Analysts can create and edit their own knowledge entries for the selected profile.

Author must be selected on the Options tab to make this option visible.

Editor

Analysts can create and edit all entries within the profile. Selecting this option automatically enables the Author option.

Editor must be selected on the Options tab to make this option visible.

8. If both options are cleared, Analysts can only search and view for knowledge entries within the selected profile. 9. To remove a profile from the role, select it in the **Selected Profile List** table, and select **Remove**. 10. Select ![](https://alemba.help/help/10.0/content/resources/images/save%20and%20close%20button.png) to save the changes and close the window. Provide the [Change Reasons](https://alemba.help/help/10.0/content/topics/general%20topics/change%20reasons.htm) if prompted to do so. Alternatively, select another tab, if appropriate. --- # 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://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/security-roles/knowledge-management-security-roles/knowledge-management-security-role-content-access-tab.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.