# Goal settings Each section of a goal's Settings page, what it controls and who can change it, including feature flags. Canonical page: https://app.auto-lab.ai/docs/goals/settings **Settings** is the last row in a goal's sidebar. It opens the goal's configuration, with one section per row on the left. This page walks through the sections in that order and links to the page that covers each in depth. ## Who can open Settings The **Settings** row shows to people who can configure the goal: goal admins, and organization owners and admins. Inside, each section checks your rights again. A section you cannot read is hidden, and one you can read but not change is shown without its controls. The page lives at `/projects//customize/settings`. The older address `/projects//settings` opens the same page. A link that names a personal tab, such as `/projects//settings/profile`, opens your personal settings over the goal instead. ## General - **Goal name** and **Icon**: how the goal appears in the switcher and on the Goals home. Changing them needs permission to edit the goal. - **Goal brief**: the answers from setup, which the agent reads each time it drafts a plan. The rows are read-only here. **Edit goal** opens setup in edit mode, or **Edit in setup** for goals set up with the form, or **Start setup** if setup never started. See [Set up and launch a goal](/docs/goals/setup#edit-the-goal-later). - **Danger zone**: **Delete goal**, the same action as [Archive](#archive). ## Access The people and groups who can open this goal, their roles, pending invitations and requests for access. Invite someone, change a role or remove access here. Seeing the list needs permission to see members; changing it needs permission to manage members, which goal admins have. See [Roles and access](/docs/organization/access). ## Autonomy How much the agent does on its own, in four cards: | Card | What it controls | Read more | |---|---|---| | **Delegation** | The same dial as on the Overview: **Ask first**, **Within policy** or **Act freely**. | [Approvals and autonomy](/docs/goals/approvals) | | **Learning** | On goals that run in Chat: **Off**, **Ask me first** or **Learn on its own** (the default). | [Learning](/docs/brain/learning) | | **Automation** | **Approve website login use**, **Sandbox minutes per day** (120 by default) and **New sessions per day** (20 by default). Limits reset at midnight UTC. Older goals also have **Daily reflection** here. | [Usage and limits](/docs/organization/usage) | | **Action audit** | A history of connector actions and approval decisions, filtered by result. It needs audit access. | [Approvals and autonomy](/docs/goals/approvals) | Each card checks its own permission. Goal admins can change all four. ## Channels Link the goal to Slack and, when they are switched on for the goal, Microsoft Teams, iMessage and email. This is also where you see which Slack workspace or inbox the goal uses. Changing channels needs permission to manage connectors. See [Channels](/docs/connect/channels). ## Connectors The same page as **Brain › Connectors**: the apps, MCP servers and API keys the goal can use, and the rule for each tool. Changing them needs permission to manage connectors. See [Connectors](/docs/connect/connectors). ## Secrets The same page as **Brain › Secrets**: encrypted values, such as API keys, that the goal's agents can use. Changing them needs permission to manage secrets. See [Secrets](/docs/connect/secrets). ## Triggers The same page as **Brain › Triggers**: schedules and webhooks that start work, including **Daily digest** and **Escalate what needs you**. The gear (**Trigger settings**) holds **Pause all triggers**. Adding a trigger needs permission to create triggers. See [Plans, schedules and triggers](/docs/goals/schedules). ## Git repo The goal's repository and who can reach it: - the **Repository** and its **Status** - the **Base branch**: new sessions and change requests start from it - the **Manifest file**: the goal manifest, `kortix.yaml` by default - **Work on this locally** and **Use your own Git client**: commands and a clone address for developers - **People with access**: for a repository Auto Lab created, invite someone by GitHub username with **Can edit** or **Can view**. For one Auto Lab did not create, use **Manage on GitHub**. Seeing this section needs permission to read the repository; changing it needs permission to push. See [The goal's repository](/docs/developers/repository). ## Sandbox templates The recipe for the machine a session runs on, and a record of each time one was prepared. Anyone who can open Settings can read it; changing it needs permission to configure the goal. See [Sandbox templates](/docs/developers/repository#sandbox-templates). ## Feature flags Some features can be switched on for one goal before they are generally available. **Feature flags** lists them. Each row has the feature's name, one sentence about it, whether it is on by default or set for this goal, and a switch. - A switch changes this goal only, straight away. Other goals and other organizations are not affected. - The setting is kept by Auto Lab, not in the goal's repository, so it does not travel with a copy of the repository. - A flag appears only when your Auto Lab deployment supports it. If the deployment does not offer a feature, its row is hidden, whatever the goal chose. - Anyone who can open Settings can see the list. Turning a flag on or off needs permission to configure the goal, which goal admins have. Flags a goal owner is most likely to meet: | Flag | What it turns on | Default | |---|---|---| | **Apps** | The **Apps** row in the goal's sidebar, for publishing sites and services at stable addresses. | Off | | **Microsoft Teams** | Teams as a channel for the goal. An admin of your Microsoft 365 tenant also has to grant consent. | Off | | **iMessage** | An iMessage line for the goal, once the line and its keys are added. | Off | | **AgentMail Email** | Email as a channel: an inbox for the goal whose threads reach the agent. | Off | | **Review Center** | The review inbox in **Brain › Review**, and its link on the Overview. | On | | **Harness v2 thread** | Chat as one conversation for the goal, with its schedules. | On | Leave **Harness v2 thread** on. Without it, Chat opens a separate session for each conversation instead of the goal's one thread. The list also shows other flags, such as **Marketplace** (the Brain tab of that name), **Warm Sessions** and **Network-Enforced Secrets**. Leave any flag you do not recognize as it is. Setting up each channel is covered in [Channels](/docs/connect/channels). ## Upgrades Changes an agent makes to the goal's setup for you. Each run opens a change request for you to review, and nothing merges on its own. A known upgrade shows here only while it applies, such as **Upgrade to v2** for a goal whose manifest still uses the first version. While one is waiting, the **Upgrades** row shows a dot. You can also describe a one-off change for an agent to make. See [Goal manifest](/docs/developers/manifest). ## Archive **Delete goal** removes the goal for everyone. You type the goal's name to confirm, and it needs permission to delete the goal. The goal's git repository is kept. See [Delete a goal](/docs/goals#delete-a-goal).