> 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/manual/management/interested-parties/example-interested-parties.md).
# Example Interested Parties
Information Commissioner's Office
For this example, we will add the Information Commissioner's Office as an interested party.
**Name**
A name given for the individual interested party.
```
Information Commissioner's Office
```
**Contact Email**
The email address for the responsible person.
```
icocasework@ico.org.uk
```
**Contact Phone Number**
The telephone number for the responsible person.
```
0303 123 1113
```
**Description**
The description section offers a detailed and complete summary of the interested party, providing the reader with a clear understanding of what it entails.
```
The Information Commissioner's Office is for upholding data protection.
```
**Relevant Processes**
The processes that have an impact on interested party.
```
Data protection
```
**Action Required**
Actions required in relation to interested parties in an ISMS (Information Security Management System) include a number of steps that must be taken to manage the interests and expectations of the interested parties. These actions are critical to ensure that the ISMS is aligned with the needs and expectations of the interested parties, and that any concerns or issues are addressed in a timely and effective manner.
```
Notify them in the event of a breach
```
**Responsible person**
In relation to interested parties in an ISMS (Information Security Management System), a responsible person is an individual or a team who is accountable for identifying, analysing, and managing the interests and expectations of the interested parties. The responsible person is responsible for ensuring that the ISMS is aligned with the needs and expectations of the interested parties, and any concerns or issues are addressed in a timely and effective manner.
```
Frodo Baggins
```
---
# 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://manual.harpe.io/start/manual/management/interested-parties/example-interested-parties.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.