> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences.md).

# Interfaces and End-User Experiences

An interface defines how people or applications use a workflow. Choose chat for conversation, a form for defined inputs, batch processing for multiple rows, or an API for another application.

These guides explain input and output mapping, access controls, branding, feedback, and conversation management. They also cover the published agent catalog and supported messaging deployments.

Interface edits save automatically to the draft. Check the saved status, then complete the project's publication process before expecting users to receive the changes. Builder access and published interface access use separate controls.

{% hint style="info" %}
Your working draft saves automatically as you edit. See [Autosave and concurrent editing](/technical-reference/releases-and-environments/autosave-and-concurrent-editing.md) to check the saved status, review detailed changes, and handle updates from another session.
{% endhint %}

### Guides in this section

* [Publish a Chat Assistant](/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-chat-assistant.md)
* [Let an agent work with uploaded files](/guides-and-quickstarts/interfaces-and-end-user-experiences/let-an-agent-work-with-uploaded-files.md)
  * [Troubleshoot uploaded files and downloads](/guides-and-quickstarts/interfaces-and-end-user-experiences/let-an-agent-work-with-uploaded-files/troubleshoot-uploaded-files-and-downloads.md)
* [Interface authentication and access](/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-authentication-and-access.md)
* [Interface branding and feedback](/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-branding-and-feedback.md)
* [Use a published chat](/guides-and-quickstarts/interfaces-and-end-user-experiences/use-a-published-chat.md)
* [Share a conversation](/guides-and-quickstarts/interfaces-and-end-user-experiences/share-a-conversation.md)
* [Build a Form interface](/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-form-interface.md)
* [Batch execution](/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-batch-interface.md)
* [Expose a project through API](/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-project-through-the-api.md)
* [Published Agents catalog](/guides-and-quickstarts/interfaces-and-end-user-experiences/published-agents-catalog.md)
* [Manage the Published Agents catalog](/guides-and-quickstarts/interfaces-and-end-user-experiences/manage-the-published-agents-catalog.md)
* [Conversation manager](/guides-and-quickstarts/interfaces-and-end-user-experiences/conversation-manager.md)
* [Slack integration](/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-slack-bot-interface.md)
* [Microsoft Teams integration](/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-microsoft-teams-interface.md)


---

# 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.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences.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.