> For the complete documentation index, see [llms.txt](https://help.genesis.autify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.genesis.autify.com/settings/workspace-settings/workspace-configuration.md).
# Workspace settings
The workspace settings screen lets you change a workspace's basic information, choose how skills are used, manage external MCP server connections, configure plugins, and manage workspace members. This article describes each tab and the steps for each task.
## Prerequisites
Changing workspace settings requires the organization **Admin** or **Owner** role, or the **Workspace Manager** role of the target workspace.
{% hint style="info" %}
The **Members** tab appears for **Admin**, **Owner**, and **Workspace Manager** roles. It does not appear for users whose workspace role is **Member**.
{% endhint %}
## Accessing the Settings Screen
1. In the left sidebar, click **Menu** next to the workspace name.
2. Click **Workspace settings**.
Workspace name menu
The settings screen has three tabs: **General**, **Integrations**, and **Members**.
Workspace settings tabs
## General Tab — Changing Basic Information
In the **Workspace details** section of the **General** tab, you can change the workspace name and description.
The **General** tab also includes a **Skills** section. Skills are reusable instruction packs discovered from uploaded `SKILL.md` files and connected codebases. This setting affects both AI Assistant chat and AI Agent blocks in workflows.
| Mode | Description |
| --------- | ---------------------------------------------------------------------------------------------------------- |
| Automatic | AI can see all skills and use relevant ones automatically. Typing `/skill-name` always applies that skill. |
| Manual | Skills are used only when you explicitly reference them as `/skill-name`. |
## Integrations Tab — Managing MCP Connections and Plugins
The **Integrations** tab consists of two sections: **MCP Server** and **Plugins**.
### MCP Server
Register and manage connections to external MCP (Model Context Protocol) servers used by this workspace. Connections registered here are available as tools from the AI Agent block in workflows.
Each connection card shows the connection name, authentication method (**OAuth** or **API Key / Headers**), server URL, and connection status.
#### Adding a Connection
1. Click **New connection**.
2. From the preset list, select the app to connect (such as GitHub Production), or select **Custom** to specify any MCP server URL.
3. In **Enter your server details**, fill in the following items.
* **Name** — Name to identify the connection (for example: JIRA Production).
* **URL** — Endpoint URL of the MCP server.
* **Authentication method** — Select **OAuth** or **API Key / Headers** with the radio buttons.
4. Click **Next**.
5. In **Credentials**, enter the following depending on the authentication method you chose.
* If you chose **OAuth**, you can usually proceed without entering any additional information. Open **Advanced (optional)** and configure the client ID, client secret, token URL, authorization URL, and scopes only when connecting to an MCP server that does not support dynamic registration.
* If you chose **API Key / Headers**, enter a **Header key** and **Value** (for example: `Authorization: Bearer ...`). You can add additional header rows as needed.
6. Click **Connect & Save**. If you chose **OAuth**, you are then redirected to the MCP server's authentication page to approve access.
{% hint style="warning" %}
For security reasons, MCP connections only support external HTTPS URLs. `http://` URLs, localhost, private IPs, link-local addresses, and other internal addresses cannot be registered. If you cannot connect, specify an HTTPS MCP server URL reachable over the network.
{% endhint %}
{% hint style="info" %}
Registered header values are masked on screen (●●●●●●●●). To change an existing value, delete it once and add it again.
{% endhint %}
{% hint style="info" %}
If an error occurs, check TLS/certificates, authentication headers, and network settings.
{% endhint %}
#### Editing a Connection
1. Click **Edit MCP connection** on the connection card you want to edit.
2. Change the **Name**, **URL**, authentication method, or credentials.
3. Click **Connect & Save**.
#### Deleting a Connection
1. Click **Delete connection** on the connection card you want to delete.
2. Click **Delete connection** in the confirmation dialog.
{% hint style="warning" %}
When you delete a connection, blocks in workflows that use it can no longer call the tool. Confirm the impact on workflows before deleting. Specifically, when you delete a connection, workflows that reference it fail pre-run validation (the error "This workflow uses an MCP connection that does not exist in this workspace" appears). Before deleting, either update the MCP connection in the target workflows or remove unused blocks.
{% endhint %}
#### Checking Connection Status
Click the status badge (**Healthy** / **Error** / **Checking…** / **Needs Authorization** / **Unknown**) on a connection card to immediately verify the connection to the MCP server.
| Status | Description |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Healthy | Connected successfully. |
| Error | A problem occurred while connecting to the MCP server. Check the following two points and then click the **Error** status badge to retry the connection. Verify the MCP connection URL. Verify that the authentication header (such as `Authorization: Bearer xxx`) is configured correctly. |
| Checking… | Verifying whether the connection is reachable. |
| Needs Authorization | The OAuth access token has expired and re-authentication is required. Click the status badge to re-run the authentication flow. |
| Unknown | Could not determine whether the connection is reachable. Click the **Unknown** status badge to retry the connection. |
#### Checking Available Tools
Click **List tools** on a connection card to view the tools provided by the MCP server. Tool name, description, and parameters are listed. You can search the list, confirm how many tools match the current filter, and expand **Input schema** only for the tools whose parameters you want to inspect.
### Plugins
Manage plugins used in this workspace. Configure per-workspace settings for Autify product integrations (Aximo) and external services connected at the organization level (Slack).
* **Aximo** — Register an Aximo API key so workflows can call Autify Aximo features.
* **Slack channels for this workspace** — Select which Slack channels this workspace's workflows and chat may post to and read from. If Slack is not connected at the organization level, click **Go to organization settings** to set it up. For the organization-level Slack connection procedure, see [Apps](/settings/connection-settings/integrations-hub.md).
## Members Tab — Managing Workspace Members
The **Members** tab manages which organization members can access this workspace.
{% hint style="info" %}
The **Members** tab appears for **Admin**, **Owner**, and **Workspace Manager** roles. Users with the organization **Owner** or **Admin** role automatically have access to every workspace. They are shown as "Organization Owner" or "Organization Admin" in the member list and cannot be removed on a per-workspace basis.
{% endhint %}
### Assigning Members
1. Click **Manage members**.
2. Enter a name or email address in the search form to filter target users.
3. Click the member you want to assign.
{% hint style="info" %}
The list shows only Member-role users in the organization who have not yet been assigned to this workspace.
{% endhint %}
### Removing Members
1. Click **Menu** in the row of the member you want to remove.
2. Click **Remove member**.
{% hint style="warning" %}
A member removed from the workspace can no longer access this workspace's files, chats, and workflows.
{% 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://help.genesis.autify.com/settings/workspace-settings/workspace-configuration.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.