> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/service-automation/use-foundation-and-global-variables.md).

# Use Foundation and Global Variables

Open **Execute → Foundation** for shared configuration used by services at deployment. The current interface provides **Global Variables** and identifies other Foundation capabilities as **Coming soon**.

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2FZU8TiUxmPmUcqe7FIhM3%2Ffoundation.jpg?alt=media&amp;token=e23a291b-04ca-4998-95d0-62ed96f1e085" alt="Foundation capabilities and availability"><figcaption></figcaption></figure>

## Create a Global Variable

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2FpzBfaBb4FQIgQue4SQQ2%2Fglobal-variable-dialog.jpg?alt=media&amp;token=7d2b6444-8409-4882-ab73-f928b818a07a" alt="New Global Variable dialog"><figcaption></figcaption></figure>

1. Select **Manage variables →** on the Global Variables card.
2. Select **+ New Global Variable**.
3. Enter the fields below and review the key carefully.
4. Select **Create** when the value is ready to be shared with bound services.

| Field               | Behavior shown in the dialog                                                           |
| ------------------- | -------------------------------------------------------------------------------------- |
| **Display name**\*  | Human-readable name.                                                                   |
| **Key**\*           | The variable's identity. Saved as an uppercase identifier and cannot be changed later. |
| **Type**\*          | `string`, `number`, `array`, `object`, `boolean`, `data table`, or `date`.             |
| **Sensitive value** | Optional setting described by the dialog as masked in the UI and encrypted at rest.    |
| **Value**\*         | The value every bound service will read.                                               |

The dialog states that after saving, **only the name and value can change**. Choose the key and type before creation; do not plan a later rename of the key.

## Example shared support team label

Suppose several request-intake services should use the same non-secret team label. Create one shared variable rather than copying the label into every Work Item.

| Field           | Example value                     |
| --------------- | --------------------------------- |
| Display name    | Example support team              |
| Key             | `EXAMPLE_SUPPORT_TEAM`            |
| Type            | `string`                          |
| Sensitive value | Off; this example is not a secret |
| Value           | `Demo Service Desk`               |

1. Search for `EXAMPLE_SUPPORT_TEAM` before creating it. Reuse an existing intended definition; choose a different example key if that name is already used for another purpose.
2. Create the variable with the values above, then reopen the list and find its saved key and display name.
3. In a test service deployment, inspect the input binding for the Work Item that needs the team label. Select the corresponding global-variable source using the binding controls available in that deployment.
4. Run the test deployment through its normal development entry and inspect the resolved Work Item input. Check that it receives `Demo Service Desk`.
5. Record the service version and package alongside the result so the next operator can identify which configuration used the value.

### Read back the saved example

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2Fn0FtvIIz14Zie4pj0tGC%2Fglobal-variable-form.jpg?alt=media" alt="Global Variable creation form with non-secret Example support team, EXAMPLE_SUPPORT_TEAM and Demo Service Desk."><figcaption></figcaption></figure>

In the documented environment, Example support team was saved on 13 October 2026 with key EXAMPLE\_SUPPORT\_TEAM, type string and value Demo Service Desk. The saved list showed Used in: Unused. This verifies creation and readback; it does not mean a deployment has consumed the value yet.

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2FLqBWgwuCDsufkGYJFkse%2Fglobal-variable-saved.jpg?alt=media" alt="Saved Global Variable EXAMPLE_SUPPORT_TEAM with value Demo Service Desk and Used in Unused."><figcaption></figcaption></figure>

### Prepare a real consuming input

Use a separate local test Work Item for the shared-label exercise. The earlier fixed-string request-summary Work Item has no inputs; select a version with an explicit input before expecting a binding field.

1\. In the test Work Item, add a String variable named support\_team and enable Use as Work Item Input. Use that input as the value consumed by a local String Assign action.

2\. Save and release the Work Item. Add that released version to the test service, publish the service version and reopen its development deployment.

3\. Find the support\_team input in the selected Work Item. Use the global-variable source to select EXAMPLE\_SUPPORT\_TEAM. Selecting the source keeps a reference to the shared value; typing Demo Service Desk into a literal field is a different configuration.

4\. Save the draft and reopen it to check the selected source. Invoke that draft once and inspect the matching Work Item action input. The expected consuming value is Demo Service Desk.

5\. If the input is missing, check the released Work Item and pinned service version first. If the value is wrong, inspect the selected binding and saved Global Variable before changing a shared value.

This exercise checks a shared value entering one Work Item. It does not require exporting that Work Item’s output. Keep tenant-specific values out of this shared example.

This example is useful when the value is intentionally shared. A customer-specific credential, requester or routing decision should remain associated with its intended tenant or request. Before changing a shared value, identify the bound deployments and check when your current version resolves changes for future and existing work.

## Understand references and scope

Foundation describes Global Variables as reusable values owned in MSP Hub, with scope across tenant deployments. Services reference the **key**, not a copied value. The Global Variables page summarizes this as one key and one value available to every tenant deployment.

Use a global value only when it is intended to be shared. Before changing one, identify the services that bind to it and assess the impact. This guide does not imply that every user or edition has access to MSP-wide administration.

## Handle a sensitive value

When **Sensitive value** is selected, the UI says secrets are never shown again after saving. For an existing secret, it instructs you to leave the value as bullets to keep the current secret.

Treat the displayed wording as the product's description of the setting; it is not a separate security certification or a complete account of runtime logging. Do not copy secret values into documentation, prompts, screenshots, or troubleshooting messages.

## Search existing variables

The list provides **Search by name, key or value…**. Find the existing key before creating a similar variable so services can reuse one intended definition.

## Features marked Coming soon

| Foundation area       | Purpose described in the interface                           | Current availability |
| --------------------- | ------------------------------------------------------------ | -------------------- |
| **Approval Policies** | Reusable approver resolution for Govern work.                | Coming soon          |
| **Access Policies**   | Who may start or continue a service after identity is known. | Coming soon          |
| **Time & SLA**        | Shared calendars and clocks across service cases.            | Coming soon          |

These cards describe planned capabilities; they are not configuration instructions for available controls. In particular, the current Service Flow designer says identity and access policy are outside this version.
