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

# Global Settings

Open Global Settings in YouDesign Command and find the right section to configure Command for everyone in your organization.

{% hint style="info" %}
You need the **Command Admin** role, or the **Command Editor** role and a persona that grants the section on its [Admin Settings](https://docs.ins-pi.com/command/the-portal/personas.md#admin-settings) tab. Without either, **Global Settings** does not appear in the menu.
{% endhint %}

Global Settings is where a Command administrator configures YouDesign Command for the whole organization: the shared Portfolio, personas, forms, approvals, measures and more. Changes apply to everyone.

Someone working in a persona that grants sections sees only those sections. If they open a link to another one, Command says **You don't have access to this section**. **License**, **Persona** and **Import / Export** are always for Command Admins only.

## Open Global Settings

1. Click **Open menu** (☰) in the top left corner of the header.
2. Click **Global Settings** to expand it.
3. Choose a section. It opens in a tab named *Global Settings ·*.

To move between sections, use the tabs across the top of the page.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-e69db84f23214c318d9e7f78ca2cbd6e71dbbe32%2Fcommand-settings-menu.png?alt=media" alt="The menu open on the left, with Global Settings expanded to list its sections, License among them."><figcaption><p>Global Settings in the menu</p></figcaption></figure>

## Sections

| Section                     | What you configure                                                                                                    | Read more                                                                                        |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| **General**                 | Switches and values the rest of Command builds on (see below).                                                        |                                                                                                  |
| **License**                 | The Command license: install or remove it, its timeline, what it includes, where your data goes and who uses Command. | [License](https://docs.ins-pi.com/command/administration/license.md)                             |
| **Portfolio**               | The shared folder tree of tables, dashboards and links every user sees under Portfolio.                               |                                                                                                  |
| **Approvals**               | Approval policies: the ordered steps and approvers an action must pass.                                               |                                                                                                  |
| **Architecture Governance** | Governance processes and stages, governance bodies, standards and automation.                                         | [Architecture Governance](https://docs.ins-pi.com/command/features/architecture-governance.md)   |
| **Assessments**             | Which questionnaire Command asks for, in which situation.                                                             | [Assessments](https://docs.ins-pi.com/command/features/assessments.md)                           |
| **Data Governance**         | Charters: which records are in scope, who answers for them and what must be true.                                     | [Data Governance](https://docs.ins-pi.com/command/features/data-governance.md)                   |
| **Forms**                   | The sections and fields of each record type's Form.                                                                   |                                                                                                  |
| **Measures**                | Measures, their families and subtypes, and value references such as actual and planned.                               | [Measures](https://docs.ins-pi.com/command/features/measures.md)                                 |
| **Lifecycle & Milestones**  | Lifecycle definitions, stages, types, scopes and milestone subtypes.                                                  | [Lifecycle](https://docs.ins-pi.com/command/features/lifecycle.md)                               |
| **Persona**                 | Personas: their content types, left-hand menus and who can use them.                                                  | [Personas](https://docs.ins-pi.com/command/the-portal/personas.md)                               |
| **Landing pages**           | A prepared Home page for a person, shown until they make their own.                                                   | [Prepare landing pages](https://docs.ins-pi.com/command/administration/landing-pages.md)         |
| **Relationships**           | Relationship fields and how the Relationship Editor behaves.                                                          | [Relationship settings](https://docs.ins-pi.com/command/administration/relationship-settings.md) |
| **Scoring**                 | Scores: weighted judgments built from your measures and fields.                                                       | [Scoring](https://docs.ins-pi.com/command/features/scoring.md)                                   |
| **Import / Export**         | Package tables, configuration and My Space content into one file and restore it on another instance.                  |                                                                                                  |

## General

**General** lists every Command setting as a row, with its name, type, description and who changed it last. Search with **Search settings**.

| Setting                               | Default                                                                                  | What it changes                                                                                                                                                                                                         |
| ------------------------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **My Tasks sources**                  | Command tasks, incidents, catalog tasks, requested items, change tasks and problem tasks | Which kinds of task appear in everyone's **My Tasks**. Command tasks are always included.                                                                                                                               |
| **Show approvals with tasks**         | On                                                                                       | Shows the approvals waiting for each user in **My Tasks**.                                                                                                                                                              |
| **Making Future State plans current** | Create rights, for every record type                                                     | Whether a planner makes a planned record real themselves, or asks for approval first, per record type (see below).                                                                                                      |
| **Command SLM assistant**             | On                                                                                       | Turns the Command Dialog assistant on or off for everyone (see below). The assistant runs in your browser and on your ServiceNow instance.                                                                              |
| **MCP Connector**                     | Off                                                                                      | Lets people connect Claude or another AI assistant to Command. It reads only what each person can already see, and cannot change anything. Using it sends that data to the AI provider the person connects (see below). |
| **cm.content.trash.retention\_days**  | 30 days                                                                                  | How many days deleted content stays in **Trash** before it is removed for good, from 1 to 3650.                                                                                                                         |

### Change a setting

1. Find the row and change its value.
2. Click **Save** on that row. **Reset** puts back the saved value.

Each row saves on its own. A setting that has never been saved uses its default; your first save stores it.

Someone granted **General** through their persona sees only **My Tasks sources**, **Show approvals with tasks** and the Trash retention. The other rows, such as **Making Future State plans current**, **Command SLM assistant** and **MCP Connector**, are for Command Admins only.

Other users see a change the next time they open Command, or within a minute.

### Turn the assistant off

1. Find **Command SLM assistant**, switch it off and click **Save**.
2. The assistant panel, its rail button and the **Start in chat**, **Discuss in chat** and **Resolve in chat** buttons disappear for everyone.

Nothing is deleted: reports, roadmaps and other content made with the assistant stay, and so do Data Governance, Measures, Scoring and Lifecycle settings. Switch it back on to bring the assistant back.

### Switch the MCP Connector on

The **MCP Connector** is off until a Command Admin switches it on. Its description ends with a warning about where data goes, and the same warning is what you confirm. Read [Where your data goes](https://docs.ins-pi.com/command/administration/license.md#where-your-data-goes) first.

1. Find **MCP Connector**, switch it on and click **Save**. The dialog **Switch the MCP Connector on?** opens.
2. Read the warning.
3. Click **I understand, switch it on**. Command records your confirmation in the license log, then saves the setting.

Click **Cancel** to leave the connector off. Switching it off needs no confirmation: switch it off and click **Save**.

### Choose how planned records become real

A planner can turn a planned record from the [Future State Repository](https://docs.ins-pi.com/command/features/future-state-repository.md#make-a-planned-record-real) into a real one. **Making Future State plans current** decides how, for each record type:

| Choice            | What the planner does                                                                                                            |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Create rights** | Makes the plan real themselves, when they are allowed to create that kind of record (or to change the record the plan is about). |
| **Approval**      | Asks for approval. An approver's yes makes the plan real, even when neither of them could create the record directly.            |

1. Find **Making Future State plans current**.
2. In **Every other class**, choose the choice most record types should use.
3. To treat a record type differently, choose it under **Set a class differently**, then choose its mode in its row. Its more specific types follow it, unless you list them too.
4. Click **Save**.

An **Approval** row with no approval policy for it says *Approval, but no approval policy matches, so create rights apply.* Planners of that record type then use create rights until you add a policy.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-f259014c8d78821e907cf70954201c86ede58dde%2Fcommand-settings-materialize-entitlement.png?alt=media" alt="The Making Future State plans current setting, with a default of Create rights and two record types set to Approval, one of them marked as having no approval policy."><figcaption><p>Choosing how planned records become real</p></figcaption></figure>

### Require approval for a record type

Set the record type to **Approval** first (see above), then add the policy that says who approves.

1. Open **Global Settings > Approvals** and click **Add Policy**.
2. Give it a **Name**, and choose **Make a Future State plan current** as its **Consumer**.
3. In **Record table**, choose **Future State Element**.
4. Add the approvers under **Steps**, as for any approval policy.
5. Under **Scope**, click **+ Add scope**, choose **Class, as listed in the setting**, and choose the record type. Without a scope, the policy applies to every record type set to **Approval**.
6. Click **Create Policy**, then **Activate**.

Back in **General**, the record type's row now says how many approval policies apply.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-44db70434df79ce81058a284f915884a316e7e3a%2Fcommand-settings-general.png?alt=media" alt="The General section of Global Settings, listing settings as rows with their descriptions, including the Command SLM assistant switched on and the MCP Connector switched off."><figcaption><p>Global Settings, General</p></figcaption></figure>

## Good to know

* Every section saves on its own, with its own **Save** button. Leaving a section with unsaved changes loses them.
* Some settings are still made in ServiceNow, such as roles and the notification retention period. See [Roles & Groups](https://docs.ins-pi.com/command/prior-v26.0/configuration/roles-groups.md).
* The descriptions of **Command SLM assistant** and **MCP Connector** each end with a sentence about where data goes. The **License** page shows the same two sentences: see [Where your data goes](https://docs.ins-pi.com/command/administration/license.md#where-your-data-goes).
* Settings move between instances with **Import / Export**, under **Configuration > Global settings**.
* Approval for planned records needs a one-time setup on the instance before **Make a Future State plan current** appears as a consumer. See [Set up approvals for planned records](https://docs.ins-pi.com/command/get-the-app/future-state-approvals.md).

## Related

* [License](https://docs.ins-pi.com/command/administration/license.md)
* [Personas](https://docs.ins-pi.com/command/the-portal/personas.md)
* [Future State Repository](https://docs.ins-pi.com/command/features/future-state-repository.md)
* [Roles & Groups](https://docs.ins-pi.com/command/prior-v26.0/configuration/roles-groups.md)
* [Installation & Setup](https://docs.ins-pi.com/command/get-the-app/installation.md)
* [Connect Claude to Command](https://docs.ins-pi.com/command/get-the-app/connect-an-ai-assistant.md)


---

# 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.ins-pi.com/command/administration/global-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.
