> For the complete documentation index, see [llms.txt](https://docs.aisuru.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisuru.com/en/sharing/sharing-layouts/manage-multiple-layouts.md).

# Manage multiple layouts

You can create **multiple sharing layouts for the same Agent**.

Each layout has its own configuration and link, allowing you to adapt the same Agent to different channels, audiences, and use cases without creating multiple copies of the Agent.

### When to use multiple layouts

Multiple layouts are useful when you want to adapt the experience for:

* different websites;
* mobile experiences;
* customer areas;
* employees;
* partners;
* events;
* physical devices;
* campaigns;
* testing different configurations.

#### Example

The same Agent could use:

* `WEBSITE_ASSISTANT` on your company website;
* `CHAT` inside your customer portal;
* `TOTEM` during a trade show;
* `FULLPAGE` for a sales demo.

All four experiences can point to the same Agent.

### Each layout has its own link

Every sharing layout has a dedicated link.

Users opening that link access the Agent using the configuration associated with that specific layout.

This means you can distribute different links to different audiences without changing the other layouts.

💡 Use clear layout names so you can easily identify where each configuration is being used.

For example:

* `Main website`
* `Customer portal`
* `Sales demo`
* `Event 2026`
* `Internal team`

### Set a default layout

You can select one layout as the **default layout** for an Agent.

Only **one default layout** can be configured at a time.

The default layout is automatically used when:

1. someone opens the Agent's main link without specifying a particular layout;
2. you use the **Try** button from the Agent management interface.

Setting a default layout therefore lets you control the standard experience shown when no specific layout has been requested.

### What happens if there is no default layout?

If no layout is configured as default, the Agent's main link uses the basic experience provided by AIsuru.

The **Try** action also opens the basic Agent experience rather than one of your customized layouts.

💡 **Set a default layout if you want users and Agent managers to consistently see the same customized experience.**

### Example configuration

Imagine an Agent called **Company Assistant**.

You could organize its layouts like this:

| Layout           | Type                | Use case          | Role          |
| ---------------- | ------------------- | ----------------- | ------------- |
| Main website     | `WEBSITE_ASSISTANT` | Company website   | Visitor       |
| Customer support | `CHAT`              | Customer portal   | Customer      |
| Expo 2026        | `TOTEM`             | Event touchscreen | Event visitor |
| Sales demo       | `FULLPAGE`          | Shared sales link | Prospect      |

You can choose one of these as the default while keeping all the others available through their dedicated links.

### Modify an existing layout

Changes made to a layout affect that specific configuration.

Before changing a layout that is already being used, check where its link or integration is currently published.

For example, the same layout may already be used in:

* a website;
* a campaign;
* a QR code;
* an event installation;
* documentation or onboarding material.

If you need a significantly different configuration for a new use case, creating a **new layout** is often clearer than reusing an existing one.

### A simple naming strategy

As the number of layouts grows, consistent naming makes them easier to manage.

A useful pattern is:

**Channel — Audience — Purpose**

For example:

* `Website — Public — Support`
* `Portal — Customers — Assistance`
* `Event — Visitors — Product demo`
* `Sales — Prospects — Demo`

This makes it immediately clear why each layout exists.

Once your layouts are ready, you can decide [**how to publish them**.](/en/sharing/publish-your-agent.md)