> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/value-stream-modeller/settings-and-configuration/admin.md).
# Admin
The configuration of your VSM tenant is related to setting up relevant access controls and connections. This can be done in the **Admin** section of Value Stream Modeller.
To access the **Admin** section, log in to **Management Dashboard**, go to **VSM** -> **Admin**.
In the **Admin** section, you can find your Make settings, **OE Tenant ID**, and configuration tabs related to **Datasources** and **Access Links**.
## Settings
The **Settings** tab contains tenant-level configuration that connects VSM with Make and external event sources.
### Make Team
The **Make Team** field specifies which Make team your VSM tenant uses for scenarios and integrations. All value stream steps that run Make scenarios are executed within this team.
By default, there is always one team created for every Make organization. All users initially belong to this default team. However, you can create additional teams to logically separate Make scenarios and users according to the needs of the business. You can configure VSM to point to any Make team you want.
To set the Make Team for a tenant enter the name of your Make team in the **Make Team** field.
To join Make and be a member of the Make Team, users must be assigned to the user group that grants permissions to access Make. For details on user groups and roles, see the [Users and Roles](/value-stream-modeller/settings-and-configuration/admin/users-and-roles.md) documentation.
### OE (Orchestration Engine) Tenant ID
The **OE Tenant ID** is a unique identifier for your tenant. It is displayed as a read-only value and can be copied using the copy button next to the field.
You need the tenant ID when configuring connections in Make, for example when setting up a webhook or Orchestration module manually. The tenant ID is also the first part of a value stream instance ID and appears in the instance URL. For connection setup details, see [Configuring a connection between VSM and Make modules](/value-stream-modeller/value-stream-designer/configuring-make-connection.md).
### Event-Receiver Endpoint
The **Event-Receiver Endpoint** section provides the credentials required for external systems to send events to VSM.
* **Source** — the endpoint URL used to send events to your tenant. It is unique for every tenant and can be copied using the copy button.
* **Secret** — the HMAC secret used to authenticate incoming event requests. Use the visibility toggle to reveal the secret when you need to copy it.
These values are required when configuring CloudEvents connections, for example in Postman or Make modules. For step-by-step instructions on establishing and testing the connection, see [Events Authentication and Configuration](/value-stream-modeller/settings-and-configuration/events/events-authentication-and-configuration.md).
## Datasources
The **Datasources** tab lets you manage data connections used by your value streams. Use this tab to configure and maintain integrations with external data sources that your processes rely on.
The Datasources tab where you select a datasource type and configure connection settings such as environment URL and token
Select the **Datasource type** from the drop-down menu and provide the required connection details. For example, to connect Celonis, enter the **Environment** URL and **Token**, then save your changes.
## Access Links
Access links let external users open their **Task Inbox** without logging in to the Management Dashboard. For an overview of how the Task Inbox works for internal and external users, see [Task Inbox and Tasks](/value-stream-modeller/settings-and-configuration/admin/task-inbox.md).
### Generating an access link
External users who do not have access to the Management Dashboard can access their Task Inbox with access links generated in VSM.
To generate an access link:
{% stepper %}
{% step %}
#### Open Access Links
Go to **VSM** → **Admin**, and open the **Access Links** tab.
{% endstep %}
{% step %}
#### Create access link
Choose **Create access link**.
{% endstep %}
{% step %}
#### Select recipient and expiry date
Select the recipient from the list and pick the link expiry date.
{% endstep %}
{% step %}
#### Save the link
Choose **Save** to create an individual link. The link ID number appears after successful creation.
{% endstep %}
{% endstepper %}
The Task Inbox is available outside the Management Dashboard so you can share the link with an external user. Each user gets a unique access link that allows them to view their inbox without authenticating or logging in to the Management Dashboard first.
### Revoking access
For each access link, you can assign an expiry date upon creation. For security reasons, you might want to withdraw access earlier, for instance if a user leaves the company.
{% stepper %}
{% step %}
#### Open Access Links
Go to **VSM** → **Admin**, and open the **Access Links** tab.
{% endstep %}
{% step %}
#### Revoke access
Pick the user's email for which you want to revoke Task Inbox access and choose the **Trash** icon.
{% endstep %}
{% endstepper %}
From this point on, the person is not able to access their external Task Inbox and you can see the status `revoked`.
The Access Links tab listing generated links with user email, expiry date, status, and options to revoke or open each link
{% hint style="info" %}
For details on how to manage and use the configurations of the **Admin** section, see:
* [Task Inbox and Tasks](/value-stream-modeller/settings-and-configuration/admin/task-inbox.md)
* [Users and Roles](/value-stream-modeller/settings-and-configuration/admin/users-and-roles.md)
* [Events Authentication and Configuration](/value-stream-modeller/settings-and-configuration/events/events-authentication-and-configuration.md)
Additionally, in the **Administration** module of Management Dashboard, you can set up settings for tenant users and their permissions. For details, see the [Users and Roles](/value-stream-modeller/settings-and-configuration/admin/users-and-roles.md) documentation.
{% endhint %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://developer.emporix.io/value-stream-modeller/settings-and-configuration/admin.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.