> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/developers/settings.md).

# Settings

When setting up Umbraco Engage on your Umbraco project it is important to get the configuration right. Learn more about the different options in this section.

In this section, you can find information about configuring different parts of Umbraco Engage.

## **Goals Configuration**

Users can set goals to track important actions or A/B test results. These goals help monitor performance and effectiveness.

You can also find an article on [setting up custom Goal Scoring](/umbraco-engage/developers/settings/custom-goals-scoring.md).

## [Configuration](/umbraco-engage/developers/settings/configuration.md)

While most configurations and settings will be visible in the Umbraco backoffice, they can only be changed in the `appSettings.json` configuration file. The configuration file article provides an overview of the available settings.

## **Permissions**

Administrators can assign different permissions to control access to marketing and workspace views, based on user roles or Document Types.

These settings allow users to manage and fine-tune their marketing efforts, ensuring data accuracy and access control.


---

# 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.umbraco.com/umbraco-engage/developers/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.