> ## Documentation Index
> Fetch the complete documentation index at: https://docs.letsflow.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Day 1 setup

> A guided first hour with Flow.

Follow these steps to make your first access or service request through Flow. Administrators should start with [Set up your workspace](/setup/admin-onboarding).

This guide covers the web app. To request help through a connected [Slack](/setup/channels/slack)
or [Microsoft Teams](/setup/channels/microsoft-teams) channel, message Flow there. By default,
you do not need to sign in to the web app or have a synced directory account first.

<Note>
  Requesting access or a service and don't have a Flow team or organization role? Go to
  [End user](/setup/end-user) instead. You do not need to sign in to the web app.
</Note>

## Before you begin

* Access to [https://app.letsflow.ai](https://app.letsflow.ai)
* An active role on at least one Flow team or organization-administrator access
* At least one requestable [catalog item](/setup/applications) published for your team (confirm with your admin)

## Getting oriented in the sidebar

The left sidebar is your primary navigation in the web app. It stays visible on every page and gives you one click into each area of Flow. The items you see depend on your role and the capabilities enabled for your team, so your sidebar may be shorter than the list below.

| Label | What it is |
| - | - |
| **Home** | Dashboard with conversations, approvals, and the Home prompt bar |
| **Conversations** | Full inbox for triage and resolution |
| Automations | Published automations (when enabled) |
| **Knowledge** | Knowledge articles synced from connected sources |
| **Assets** | Device and application inventory |
| **Integrations** | Connection to identity providers, knowledge sources, asset platforms, and ticketing systems |
| **Analytics** | Request handling, automation outcomes, knowledge answers, and connected discoveries |
| Settings | Admin configuration |

Team members use **Home**, **Conversations**, and the surfaces their role exposes. Requesters contact Flow through the Slack, Microsoft Teams, or email channel their organization configured.

## Make your first request

<Steps>
  <Step title="Sign in.">
    Visit [https://app.letsflow.ai](https://app.letsflow.ai) and sign in.
  </Step>

  <Step title="Review Home.">
    Review **Home**, the app landing page. You will see:

    * **Conversations**: open work assigned to you, your team, or unassigned
    * **My approvals**: pending decisions that need your review
    * A prompt bar: ask Flow questions or request access and services
  </Step>

  <Step title="Describe what you need.">
    Use plain language in the prompt bar, for example: "Request standard virtual private network (VPN) access for me" or "Start the laptop replacement automation."
  </Step>

  <Step title="Answer follow-up questions.">
    In the thread, reply to follow-up questions from Flow, such as justification, duration, target team, or who the request is for.
  </Step>

  <Step title="Track the outcome.">
    After submission, follow the conversation in the list or in **Conversations**.
  </Step>
</Steps>

When Flow submits a request via a catalog item, you get a tracking conversation or approval path depending on how that catalog item is configured.

See [End user](/setup/end-user) for channel-based intake and [Access](/setup/access) for approvals.

## Related topics

| Your role | Next chapter |
| - | - |
| Requester | [End user](/setup/end-user) |
| Help-desk operator | [Help desk](/setup/help-desk), then [Conversations](/setup/conversations) |
| Builder | [Automations](/setup/workflows) |
| Access manager | [Access](/setup/access), then [Application access](/setup/applications) |
| Integrator | [API Reference](/api-reference), [command-line interface (CLI)](/setup/cli), [Hosted MCP](/setup/mcp) |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.