> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/smart-views/smart-assist.md).

# Smart Assist

Smart Assist is a collection of several views or slider groups.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/Zf2Zxt3g6WdcJXFy4lUv/Smart%20Assist%20Hero.png" alt=""><figcaption><p>Smart Assist on a mobile phone</p></figcaption></figure>

The difference from [↗ slider groups](/collection/english-v14/documentation/smart-views/slider-gruppen.md) is in the following aspects:

* Smart Assist can consist of both views and slider groups
* Slider groups are intended for public use - Smart Assist is intended for individual users or user groups.
* Slider groups look the same for all users - Smart Assist can be customized for individual users
* Slider groups switch automatically between views - In Smart Assist, the user can switch between views independently.
* Slider groups can be password-protected or freely accessible - Smart Assist is always password-protected. A user logs in with their Eliona credentials to access "their" Smart Assist.
* Smart Views can also be viewed without an Eliona account - An Eliona account is always required for Smart Assist

## Access Smart Assist

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/eMRfQU7KxVDOv6Va4TGn/Smart%20Assist.png" alt=""><figcaption></figcaption></figure>

* Open the menu item **Smart View \[A]**\
  ▷ The "Smart Views" workspace opens.
* Click on **\[B]**\
  ▷ The window **"Smart Assist"** opens

Smart Assist can also be accessed by appending the suffix ***/sa*** to the URL of your Eliona instance.

A corresponding link might then look like this: [www.demo.eliona.i\&#x6F;\*\*/sa](http://www.demo.eliona.i\&#x6F;**/sa)\*\*

Which content a user sees in their Smart Assist depends on which views/slider groups are [↗ configured](/collection/english-v14/documentation/smart-views/slider-gruppen.md) for them.

## Configure Smart Assist for users

Proceed as follows to determine which views/slider groups a user sees when they access Smart Assist:

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/6nD8MMdk2qdNwFPJizRY/Smart%20assist%20menu.png" alt=""><figcaption></figcaption></figure>

1. Click on **Smart View \[A]**
2. Click on **Smart Assist menu \[B]**\
   ▷ The Smart Assist menu opens
3. Select in **\[C]** select one or more users.
4. In **\[D]** you can see a list of all available views and sliders. Enable the views/sliders here that the users should see **\[F]**, which you selected in step 3.
5. In **\[E]** you can use *Drag and drop* to change the order of the views.
6. Click on **\[H]**, to save.

## Operate Smart Assist

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/KUDWz7mdNfptIVYYBFg4/Smart%20Assist%20Hero_Erkl%C3%A4rung.png" alt=""><figcaption></figcaption></figure>

1. Access Smart Assist as [↗ here](#smart-assist-aufrufen) described
2. If necessary: log in with your credentials
3. In **\[H]** you see the widgets of the current Smart View
4. In **\[G]** you can switch between the available Smart Views


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/english-v14/documentation/smart-views/smart-assist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
