> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/development-cycle/build-overview/globals.md).

# Globals

Learn more about globals and how they are used to store variables on the Digibee Integration Platform.

## **Overview**

Globals are variables stored in the platform that can be reused across multiple [pipelines](/documentation/development-cycle/build-overview/pipelines.md) and [capsules](/documentation/development-cycle/build-overview/capsulas.md). Once created, a global can be referenced in any text field of a connector's configuration form.

Because the value is defined in a single place, updating a global applies the change everywhere it is used. Globals can also be restricted to specific projects, so each variable is only available where it's needed.

## **Managing globals**

You can access the Globals page from the Build page, by clicking the **Globals** tab, or by clicking the Digibee logo in the upper-left corner, selecting **Settings**, and then finding the **Globals** page.

The Globals list shows the **Global Name**, **Category**, **Description**, and **Running Pipelines** for each global, and can be filtered by **Category** and **Deprecated** status (**Yes** or **No**).

### **Creating a global**

On the Globals page, click **Create new** and fill in the fields:

| Field                                                        | Description                                                                                                                                                                               |
| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Global name**                                              | The name used to reference the global in pipelines and capsules. Use only lowercase letters, numbers, hyphens (`-`), or dots (`.`), up to 60 characters and without accents.              |
| **Category**                                                 | Defines how the value is validated. See the available categories below.                                                                                                                   |
| **Description**                                              | A short explanation of the global's purpose.                                                                                                                                              |
| **Project Availability**                                     | Defines whether the global is available to all projects or only selected ones. On the Globals listing page, you only see globals available to all projects or to ones you have access to. |
| **Prod environment / Test environment / Other environments** | The value of the global in each environment, up to 10,000 characters per field.                                                                                                           |

The category you select determines which values the global accepts. The platform validates each environment value against the category before saving:

| Category  | Accepted value                        |
| --------- | ------------------------------------- |
| **URL**   | A valid URL.                          |
| **Email** | A valid email address.                |
| **ID**    | Numbers only.                         |
| **Cron**  | A valid cron expression.              |
| **JDBC**  | A valid connection string.            |
| **Other** | Any value. Use this option for lists. |

{% hint style="warning" %}

#### **Globals can be permanently removed from pipelines**

A global is removed from a pipeline if it becomes unavailable in the pipeline's project: when the pipeline is moved to a project where the global isn't allowed, or when the pipeline's project is removed from the global's list of allowed projects in its Project Availability setting.

Once removed, moving the pipeline back or re-allowing the project **will not restore it**, for security reasons. You'll need to manually add the global back to the pipeline.
{% endhint %}

Then click **Save**. A confirmation window appears, and you must click **Create** to create the global.

{% hint style="danger" %}
Globals are not encrypted and are visible to all users with access to them. Don't store sensitive data in globals. If you need encryption, use [Accounts](/documentation/development-cycle/build-overview/accounts.md) instead.
{% endhint %}

### **Editing a global**

To edit a global, go to the **Globals list** and click the row of the global you want to edit.

You can:

* Update the category.
* Update the description.
* Mark the global as deprecated. [Learn more about deprecating a global](#deprecating-a-global).
* Define new rules for **Project Availability**.
* Update the environment values.
* View all pipelines that use the global.

After editing the global, click **Save**. A confirmation window appears, and you must click **Edit** to confirm the changes.

All changes are applied immediately to pipelines that use the global and have not yet been deployed. Deployed pipelines only receive the new values after being redeployed, and a warning on the pipeline card in the **Run** page reminds you to do so.

### **Deprecating a global** <a href="#deprecating-a-global" id="deprecating-a-global"></a>

Deprecating a global makes it unavailable for new pipelines or new pipeline versions. Existing deployments keep working unless redeployed.

To deprecate a global:

1. In the **Globals list**, click the row of the global you want to deprecate.
2. Enable the **Deprecated** toggle.
3. Click **Save**.

{% hint style="warning" %}
This action is irreversible.
{% endhint %}

### **Deleting a global**

Deleting a global permanently removes it from the Platform. You cannot delete globals that are currently used in pipelines, whether deployed or not. To proceed, remove or replace the global in all pipelines before deleting it.

To delete a global:

1. In the **Globals list**, click the three dots of the global you want to delete.
2. Select **Delete**.
3. Confirm the action in the confirmation window.

{% hint style="warning" %}
This action is irreversible.
{% endhint %}

### **Using globals**

Globals can be referenced in any text field of a connector's configuration form. To use a global:

1. Open the pipeline or capsule.
2. Select the connector you want to configure.
3. In the target field, type `{{`. In the [autocomplete list](/documentation/connectors-and-triggers/double-braces/double-braces-autocomplete.md), select **global** and type a dot (`.`) to see the available variables.

You can also add the reference manually:

```
{{global.globalName}}
```

Replace `globalName` with the name of the global. For example: `{{global.db-timeout}}`.


---

# 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.digibee.com/documentation/development-cycle/build-overview/globals.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.