> 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/account-level-settings.md).

# Account Level Settings

<figure><img src="https://563760996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJBdddbwa2Hgh4yTRC5g%2Fuploads%2FNI7ee5ZrWs9zJ7v5boEz%2Fimage.png?alt=media&amp;token=710a44a3-9d77-41da-9c45-34f1b9b7cba6" alt=""><figcaption></figcaption></figure>

There is a “Setup” dropdown in the top navigation. From here you can choose the following:

* **Get Code Snippet** This is your unique code snippet for your Pulse Insights implementation. See implementation documentation [here](https://docs.pulseinsights.com/implementing-pulse-insights-dev/implementing-in-email.md#implement-tag).
* **Global Targeting** to manage impression frequency caps and IP suppression.&#x20;
* **Data & Integrations** Enable and manage survey callback code snippets: impression callback, viewed impression callback, Onanswer callback, Onclose callback and Oncomplete callback. See more information [here](https://docs.pulseinsights.com/implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/callbacks.md).
* **Data Restrictions** to manage data masking.
* **Themes** allow you to customize colors, fonts, and backgrounds via JSON “themes” so the formatting matches your brand.
* **Automations & Events**
* **Activity Log** to view a running log of all account changes, the time and date of the change, and the user who made the change.
* **User Management** to manage the users who have access to your Pulse Insights account, invite users, and assign access level. See the [User Management](https://docs.pulseinsights.com/configuring-pulse-insights-console/account-setup/inviting-collaborators.md) section for more details.&#x20;
* **Support** - If you need help, please contact <support@pulseinsights.com>.


---

# 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/account-level-settings.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.
