> For the complete documentation index, see [llms.txt](https://manual.harpe.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.harpe.io/start/getting-started/set-up-your-isms.md). # Set up your ISMS Welcome to Harpe - lets get you set up Welcome to our automated Information Security Management System (ISMS) setup page! Our SaaS tool is designed to help you establish and maintain an effective ISMS that ensures the confidentiality, integrity, and availability of your organisation's information assets. With our easy-to-use setup process, you can quickly configure the system to align with your specific information security policies and regulatory requirements. Whether you're a small business or a large enterprise, our ISMS setup page has everything you need to get started on the path to robust information security. In this section you will complete the following steps: * [ ] Add employees * [ ] Complete management details * [ ] Add your first asset * [ ] Add your first supplier * [ ] Add your first risk * [ ] Add your first CAPA * [ ] Add your first incident * [ ] Review your documents tab * [ ] Assess your compliance * [ ] Configure your Harpe feed --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://manual.harpe.io/start/getting-started/set-up-your-isms.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.