> For the complete documentation index, see [llms.txt](https://docs.pulseinsights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulseinsights.com/configuring-pulse-insights-console/editor/general.md).
# General
## Survey Tags
You can optionally add tags to your survey for organizational purposes. You can filter by specific tags in the survey dashboard. For example, you can tag a survey with "Staging" to indicate a survey that is being QA'd on your staging site.
To apply a tag to a survey, click on the input area and select your desired tag from the dropdown menu. You can apply more than one tag to a survey. The dropdown menu will only show existing tags.
To create a new tag click "Manage Tags", then "New Tag". Enter the name of the tag and hit "Save". The newly created tag will now show in the dropdown and as a filter option on the survey dashboard page.
Select tag(s) from the dropdown menu
Selected tag is applied to the survey
You can filter down surveys displayed in the survey dashboard by selecting a Tag
## Audit Log
You can view recent activity for a particular survey by going in the editor, clicking the "General" tab in the right side panel. The last few changes are displayed in the "Audit Log" section.
Click the "More" button to see up to the last 10 changes. Click "See All" in the modal to see all changes in the Audit Log.
{% hint style="info" %}
Please see the section on [Activity Log](/configuring-pulse-insights-console/account-level-settings/activity-log.md) for more details.
{% endhint %}
---
# 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.pulseinsights.com/configuring-pulse-insights-console/editor/general.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.
