> For the complete documentation index, see [llms.txt](https://guide.scribe.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.scribe.gov.sg/help/faqs/seeking-consent.md).

# Seeking Consent

### Do I need to obtain consent before using Scribe?

By using Scribe, you represent that you have obtained all necessary consent from all parties involved in the recording. What constitutes necessary consent will depend on your organisation and context -  if you are unsure, check with your organisation's policy team.

Please ensure that you follow your organisation's usage guidelines on the use of tools like Scribe. These usage guidelines should be in line with our [Terms of Use](https://scribe.gov.sg/docs/TermsOfUse.pdf).

For reference, some organisations use a verbal consent model, where the user explains what Scribe is, seeks the other parties' agreement before the session begins, and records explicitly that verbal consent was obtained within their documentation.&#x20;

Other organisations incorporate consent within an intake or registration form, so consent is obtained at registration instead of at the start of each session.

### **How do I explain Scribe to others?**

Here's an example of how some of our users have introduced Scribe:

> I'll be using a note-taking tool called Scribe during our session. It helps me capture what we discuss so I can focus on our conversation. Anything that it notes down will not be used or seen by anyone other than myself.


---

# 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://guide.scribe.gov.sg/help/faqs/seeking-consent.md?ask=<question>&goal=<user_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.
