> For the complete documentation index, see [llms.txt](https://documentation.ardoq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ardoq.com/shiftx/configuring-shiftx.md).
# Configuring ShiftX
A guide on connecting ShiftX to your Ardoq organization and linking the relevant components for use in ShiftX.
ShiftX processes are built on the foundations of the Ardoq graph database. Processes and relationships created in ShiftX are available to Ardoq and, similarly, Ardoq components and fields are accessible to ShiftX.
To make effective use of ShiftX, we first need to define what components and references we want ShiftX to work with.
## Step 1 — Creating the Process Workspace
When you use ShiftX for the first time, you'll be prompted to create a new process workspace. If you have an existing process workspace, you can choose to use it instead.
By default, ShiftX will create a **Business Process** workspace with the **Process** component type.
Click **Create and configure new workspace** to finalize the configuration.
You can always review and change your configuration by clicking the :gear: (Settings) icon in the bottom-left corner and going to the **Process setup** tab.
Mapping to an Existing Workspace
1. Select your desired Workspace, we recommend using a name such as business process workspace
2. Choose an Ardoq component type that represents your processes
3. Create references: Define the relationships you want to see between processes and sub-processes within ShiftX. For example, `Process → Supports → Sub-process.`
4. Select fields: Ensure the workspace selected includes fields for:
1. **Status**: To track the current state of processes. Must be a text field.
2. **URL**: A navigable link to go between Ardoq and ShiftX.
{% hint style="info" %}
You will need to create these references and fields in Ardoq.
{% endhint %}
## Step 2 — Mapping Ardoq Components to ShiftX
When modelling processes in ShiftX, you use your components from Ardoq to enrich your processes. ShiftX uses
You can map your components by clicking the :gear: (Settings) icon in the bottom-left corner and going to the **Manage components** tab.
ShiftX Component Group Types
ShiftX uses the following group types for modelling processes and you can map as many of them as you need for your use cases:
* **Person**: a specific named person in your organization
* **Role**: job title and positions in the organization not corresponding to a specific person
* **Organizational Unit**: a division within your organization that contributes to processes
* **Application**: enterprise software, SaaS software, and cloud services
* **Agent**: an AI agent (chatbot, copilot) that contributes to your processes
* **Resource**: general non-software resources like tools and equipment
Click **Create component group** for your selected group type to begin mapping Ardoq components to ShiftX.
As an example, we'll configure an **Applications** component group by selecting applications in the previous step.
We'll begin by synchronizing components from Ardoq by clicking **Create configuration**.
We'll select the **Applications** workspace, the **Application** component type, and the **Is Supported By** reference type. The reference type will define how ShiftX attaches applications to its processes.
{% hint style="info" %}
ShiftX will preview the component available in the workspace and selecting a component from the preview will use it for further previews in reference selection.
{% endhint %}
Click **Save configuration** to save your changes.
You can return to the **Manage components** tab to review your configurations. If you're following [Ardoq Solutions](https://documentation.ardoq.com/ardoq-use-case-solutions), ShiftX will suggest automated mappings for you — you can use the **Quick create** button to create standard configurations.
You can configure several component types to a single component group in ShiftX in cases where you want to differentiate similar component types, for example Applications and Application Modules.
## Deleting Mappings
Once a component group configuration has been created, only the reference type can be updated while the workspace and component types are locked in. If you need to update the component group, we recommend deleting it and creating a new mapping.
