# Your workspace and AI apps

The dashboard is your management workspace. A connected AI app helps with supported setup and management tasks; it does not replace customer-facing Iris or automatically connect your business channels.

## Find the right dashboard page

Open the [dashboard](https://dashboard.flowlith.com/profile) on a desktop or laptop. Check the selected business before changing anything.

| Page | What you manage |
| --- | --- |
| **Home** | Approval, launch status, activity, credits and next steps |
| **Connections** | Instagram, Messenger and WhatsApp authorization |
| **API keys** | The secret your website backend uses to call Iris |
| **Billing** | Available credit purchases, plan and payment history |
| **Actions** | Customer preview, reference assets, skills and external systems |
| **About business** | Business information, called Info in some AI tools |
| **Memory** | Shared business notes, not individual customer records |
| **Settings** | Account email, sign-out, knowledge export and deletion |

## Teach a procedure and add references

1. In **Actions → Your skills**, select **Teach a skill**. Explain when to use it, what to do, what needs confirmation and when your team should step in.
2. Add relevant supporting material. Skill attachments accept PDF, Word (.docx), Markdown or text: up to five files of 1 MB each. Upload success alone does not prove accurate reading; test a question that requires the material.
3. For reusable references, use **Assets → Upload Markdown**. Assets are UTF-8 Markdown, up to 200 KB per file and 20 assets. Assets and skill attachments share a 3.5 MB budget.
4. Use public HTTPS reference links without passwords, query strings or access tokens. Adding a link does not connect an account or guarantee its contents can be read.
5. Save the draft, review all pending changes, then select **Apply to Iris**. This publishes the whole saved set of assets, skills and associated access keys. Current replies finish first; new replies may pause briefly.
6. Wait for **Applied to Iris**, then test a relevant question. Apply does not send a test automatically.

Replace this fictional outline with your business’s real process. Do not claim a refund or notification was sent unless a working integration confirms it.

```markdown
# Explain our returns process

## When to use this
A customer asks whether an item can be returned.

## Steps
1. Ask which product they mean and when it was received.
2. Read the current returns policy asset.
3. Explain the conditions without inventing an exception.
4. For a case needing review, give our approved support route.

## Boundaries
- Do not promise a refund before the team approves it.
- Do not ask for passwords, login codes or full card details.
- Do not say a request was submitted without a confirmed result.

## Example
Customer: Can I return a gift?
Iris: I can help check the policy. Which item is it, and when was it received?
```

For API or tool access, follow [External APIs and Actions](https://docs.flowlith.com/actions). Keep credentials in the dedicated access-key form or secure link, never in instructions, attachments or chat. “Key saved” is not “connection tested.”

## Preview Iris as a customer

**Customer preview** uses your currently applied knowledge, not unsaved or pending drafts. It is a separate conversation, not an administrative chat or a way to read customer records.

Each answered preview uses one credit. Enabled external tools can change real data. Use fictional details and test connections, and check external results yourself. A preview cannot confirm that your WhatsApp, Instagram, Messenger or website integration delivers messages; test that channel separately.

## Connect your AI workspace

For the full owner-sign-in flow, external tool-server requirements and tested configuration examples, read [How MCP connects](https://docs.flowlith.com/mcp).

Use an AI app that supports remote MCP with browser OAuth. Custom connections may depend on its plan and workspace policy. A public client package or successful custom connection does not imply a marketplace listing.

1. In your app’s custom connector or remote MCP settings, name the connection **Flowlith**.
2. Enter the public server address below and choose browser OAuth.
3. Complete Flowlith sign-in in your browser using your account email, enter the email code there, and review **Allow**. Do not put an Authorization header, password or login code into chat or configuration.
4. Enable the connection in your AI conversation if required, then ask for a read-only check.

```text
https://mcp.flowlith.com/mcp
```

```text
List my Iris businesses. Do not change anything or begin onboarding.
Tell me whether Flowlith is connected and signed in.
If I have more than one business, ask which one I mean.
```

An empty list is valid for a new account. Tool discovery alone is not proof that sign-in or business access succeeded. If the AI app cannot call Flowlith, reconnect and finish browser sign-in before continuing.

Clients that accept remote MCP JSON configuration can use this credential-free example. Other clients use their connection form instead.

```json
{
  "mcpServers": {
    "iris": {
      "url": "https://mcp.flowlith.com/mcp"
    }
  }
}
```

The [public Flowlith client package](https://github.com/jubsnfzm/iris-plugin) has client-specific guidance. Imported copies may require the app’s update action; publishing a package update does not automatically refresh an existing import.

## What to ask your connected assistant

For setup:

```text
Help me set up Iris for my business. First list my businesses and confirm
which one we are working on. Ask one onboarding question at a time.
Show proposed business information before saving it.
Wait for Flowlith approval before proposing launch, and ask me first.
Never request keys or verification codes in chat.
```

For external tools:

```text
Help Iris [describe one customer task] using [system name].
Read the public integration docs or tool list before choosing a setup.
Use a secure key-entry link if credentials are needed.
Show the exact Preview. Explain any real effect and ask before Test.
After a successful Test, ask before enabling that exact Action version.
Do not automatically repeat a sent write with an uncertain outcome.
```

A connected assistant can review status, update business information, prepare skills and assets, apply an approved teaching revision, configure supported Actions, launch an approved business and run an approved customer preview. Settings, shared Memory editing, website API keys and Meta sign-in remain browser steps. Ask for the relevant dashboard link instead of sending private information in chat.

## Account-wide controls

**Settings** covers your account, not just the selected business. Changing your email requires verification of both addresses and signs you out everywhere. **Sign out everywhere** ends account access sessions; it does not stop Iris. Reconnect AI apps when authorization is no longer valid.

**Export knowledge** downloads saved business knowledge as JSON, not a complete backup. It excludes credentials and conversation history. Treat exports as private: they can contain your own confidential business material.

**Delete account** is a separate, irreversible action covering all owned businesses. Review the list and notice carefully. It stops Iris and revokes website API access; it does not delete your external Instagram, Facebook or WhatsApp accounts. Cleanup can take time, and external providers’ retention rules still apply.

[Business information](https://docs.flowlith.com/info) · [Shared Memory](https://docs.flowlith.com/memory) · [Troubleshooting](https://docs.flowlith.com/troubleshooting)