> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/kb/the-basics/appmixer-interfaces.md).

# Appmixer interfaces

[As outlined in the previous section](/kb/master.md), Appmixer consists of three main interfaces: Appmixer Studio, Backoffice, and SDK Demo.

* **Appmixer Studio** is the environment where the flow configuration happens, Besides flow creation, you can manage your connected accounts, troubleshoot errors, view insights and set up custom key-value data stores.
* **Backoffice**, being the most technical part of Appmixer, serves similarly like an admin panel. Here, you can grant access to other users, manage access control lists, register third-party apps etc.
* **SDK Demo** helps you preview what your end-users see and interact with. As you already know, Appmixer is an embedded (white-label) solution that lives inside your software. The SDK Demo serves as an inspiration for your developers on how they can use the Appmixer JavaScript SDK to embed Appmixer in your product.

Let's explore all the interfaces one by one.

{% content-ref url="/pages/-MfHXW-ZVozesewksnSa" %}
[Appmixer Studio](/kb/the-basics/appmixer-interfaces/appmixer-studio.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MfHXPr8s0eSjSU8TYKk" %}
[Backoffice](/kb/the-basics/appmixer-interfaces/backoffice.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MflNr--yvAf-9h-CRGt" %}
[SDK Demo](/kb/sdk-demo/workflow-automation.md)
{% endcontent-ref %}


---

# 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.appmixer.com/kb/the-basics/appmixer-interfaces.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.