> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/readme/secoda-as-an-admin/populate-questions-with-faqs.md).

# Populate Questions with FAQs

Use our Questions feature to add frequently asked questions that might help your members navigating the workspace.

Before rolling out the tool to a larger group, we recommend populating the Questions section with some FAQs for your users. This will help users see the value in how Questions can save them time.

Read up on Secoda's Questions feature here:

{% content-ref url="/pages/HULyNz3XAdIdtpsA2VKE" %}
[Questions](/features/ask-questions-in-secoda.md)
{% endcontent-ref %}

Some example questions that we have seen from customers:

* Where can I find this data?
* How is our team's data organized?
* What is the number of new customers from last month?
* What is the difference between how we use these two datasets?


---

# 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://docs.secoda.co/readme/secoda-as-an-admin/populate-questions-with-faqs.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.
