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 for guidance on what belongs at Project level versus in a Skill.

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;

• Archive project — retires the Project when it should no longer be active.

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.

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.

The Project's landing page is configured under Navigation → Customise Sidebar, rather than on the General tab.

Use Members and Roles and Permissions 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.