> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/administration-and-configuration/governance.md). # Governance Feedback from Mercina for this page: how do access which reports to be able to manage content. For e.g. Is adding a governance cycle to all objects necessary? What are the different relationships or associations that are possible within the tool? * Settings and preferences → Environment Standard for each module. How to setup different users? * How to setup different users? So this is all the roles to be able to use across the tool. I don't know how it is in the IMS currently - but for EPC we need Authors, Approvers, Endorsers (if required), etc., * Who are actors in an org? customers, suppliers, employees, * Solution design in it's basic sense * pre-setups before Integrations, and different types of integrations --- # 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://interfacing.gitbook.io/interfacing-help-files/administration-and-configuration/governance.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.