> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/settings.md).

# Settings

Configure project identity, Agent behaviour and the navigation shown to people using the project.

Settings contains project-level configuration that shapes how the Project and Agent are presented and how the Agent is instructed at the start of a session.

Only a **Project Owner** or **organisation Owner** can currently change these settings. A Builder can open the page but receives a permission message rather than editable controls.

If you are setting up an Agent, start with [Build an Agent → Instructions and behaviour](/build-and-improve/overview/instructions-and-behaviour.md) for guidance on what belongs at Project level versus in a Skill.

![The current Project Settings surface showing Project title, Project description, Agent tone, organisation branding and the default page.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2F6e9EpuVOTrMot8saYbM3%2Fsettings-agent.png?alt=media)

## General settings

The current General surface includes:

* **Title** — the Project name and the name shown for its Agent;
* **Project description** — describes the Project **and instructs the Agent at the start of every session**;
* **Agent tone** — the response style used by the Agent, currently Crisp, Balanced or Warm;
* **Apply Organisation branding** — applies configured organisation branding to the Project experience;
* **Default page** — chooses where people land when they open the Project.

There is **not a separate current Agent Instructions field**. Use the Project description for durable Project-level instructions, then put task-specific methods, rules and checks in [Skills](/build-and-improve/intelligence/skills.md).

For example, a Project description can establish both the operating area and standing behaviour: what the Project is for, which sources should be trusted, and what the Agent should never invent. A Skill can then define the exact method for a recurring task such as processing an EDI order or checking an invoice exception.

## Navigation, Pins and Members

Settings also exposes dedicated tabs for **Navigation**, **Pins** and **Members**. These control how the Project experience is organised for users; they are not a substitute for access permissions.

Use [Members](/administer-and-govern/control/members.md) and [Roles and Permissions](/administer-and-govern/control/members/roles-and-permissions.md) when the question is who is allowed to operate, build or administer the Project.

## Organisation context is a separate layer

Broader organisation and user context can also be captured outside this Project settings page. Do not duplicate organisation-wide facts into every Project unless they materially affect the work.

Keep Project-specific operating behaviour explicit in the Project description or the Skill where it applies.

Review Settings when an Agent changes responsibility, is handed to a new operational owner, or is prepared for wider operator use.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lleverage.ai/administer-and-govern/control/settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.