> For the complete documentation index, see [llms.txt](https://docs.nlx.ai/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nlx.ai/platform/nlx-platform-guide/intro-to-agentic-cx-designer/workspace-access.md).

# Workspace access

## **Access & Workspaces**

Agentic CX designer is accessed through **Connect Customer** and organized into **workspaces**.

A workspace is a standalone environment where teams build and manage conversational AI applications. Each workspace has its own applications, flows, integrations, knowledge bases, guardrails, analytics, users, roles, and settings.

Because workspaces are separate, resources and permissions are not shared automatically across them. Changes made in one workspace do not affect another workspace.

***

### **How access works**

Access to agentic CX designer starts from Connect Customer.

* Select your Connect Customer instance.
* From your instance, select **Agentic CX designer.**

<figure><img src="/files/lGXtDxsV2vYHk7r5Cyrz" alt=""><figcaption></figcaption></figure>

Users can launch agentic CX designer from the Connect Customer console.&#x20;

Account administrators can access the **Admin Hub** in **agentic CX designer** to create one or more workspaces and assign users to those workspaces.

When adding users, Account Administrators select from user profiles already available in the connected Connect Customer instance.

After a user profile is added to a workspace, the Account Administrator assigns that user a workspace role. The role determines what the user can view, create, edit, or manage inside that workspace.

***

### **Access**

1. Open the Amazon Connect Customer console. &#x20;
2. Select **Agentic CX designer**.&#x20;

If a user cannot access the expected workspace, they should contact an Account Administrator to confirm that their Connect Customer user profile has been added to the workspace and assigned the correct role.

***

### **Workspace resources**

Inside a workspace, users can create and manage resources such as:

| Resource                      | What it is used for                                                                       |
| ----------------------------- | ----------------------------------------------------------------------------------------- |
| **Applications**              | The conversational AI experiences users interact with.                                    |
| **Agentic CX designer flows** | The conversation paths that guide users through tasks.                                    |
| **Canvas**                    | The visual builder used to create and connect flow nodes.                                 |
| **Integrations**              | Connections to external tools, APIs, and services.                                        |
| **Knowledge bases**           | Trusted content the AI can use to answer questions.                                       |
| **Variables and slots**       | Dynamic values captured, remembered, or referenced during a conversation.                 |
| **Guardrails**                | Safety, brand, and compliance controls.                                                   |
| **Analytics**                 | Performance data used to monitor and improve experiences.                                 |
| **Users and roles**           | Access controls that determine what each person can view or manage within that workspace. |

***

### **Switching workspaces**

If you are an Account Administrator or have been assigned a role in more than one workspace, you can switch between workspaces from the workspace dropdown in the upper-left corner of an agentic CX designer workspace.

When you switch workspaces, you are changing which set of resources you are viewing and editing.

Only workspaces you have permission to access appear in the dropdown.

***

### **Workspace separation**

Each workspace is separate.

This means:

* Applications in one workspace do not appear in another workspace.
* Flows, integrations, knowledge bases, guardrails, and analytics are managed independently.
* Users must be assigned to each workspace where they need access.
* A role in one workspace does not automatically grant the same role in another workspace.
* Changes made in one workspace do not affect resources in another workspace.

Workspace separation helps teams organize work safely and keep resources permissioned appropriately.


---

# 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://docs.nlx.ai/platform/nlx-platform-guide/intro-to-agentic-cx-designer/workspace-access.md?ask=<question>&goal=<endgoal>
```

`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.