> ## 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.

# End user

> Request access and services through Flow and channels, and follow progress as a requester.

## The requester experience

You can contact Flow through one of the following channels your organization configured:

1. **Slack**: start or continue a direct message or channel thread
2. **Microsoft Teams**: start or continue a supported channel conversation
3. **Email**: send a new request or reply to the existing thread

A **catalog item** may be one of the following:

* An **access request**: asks for approval and may provision entitlements after decision
* An **automation service**: starts an automation that fulfils the request

Both create trackable work the responsible team can see in **Conversations**.

You do not need to choose a queue or know the underlying process. Stay in the channel conversation.
Flow asks for the details it needs and coordinates the next step.

## Start a request

<Steps>
  <Step title="Describe what you need.">
    From Slack, Microsoft Teams, or email, describe the service or access you need and who it is for if not yourself.
  </Step>

  <Step title="Answer follow-up questions from Flow.">
    Provide justification, duration, or other details when Flow asks.
  </Step>

  <Step title="Track the outcome.">
    After submission, follow confirmation, approval, and fulfillment updates in the same thread.
  </Step>
</Steps>

Exact intake behavior depends on how your team configured channels under **Settings → Chat**.

## What explanation-only messages do

Asking what Flow can do, or telling it not to create anything, keeps the exchange read-only. A
tracking number exists only after Flow confirms that tracked work was created.

When human investigation is needed, Flow can collect the details and escalate to a configured
service desk. You receive confirmation only after the handoff is created.

## Following up

| Channel | What to do |
| - | - |
| **Slack or Teams** | Reply in the conversation Flow opened |
| **Email** | Reply to the existing email thread |

You cannot edit a submitted request in place. Add context by replying on the thread.

## When Flow cannot submit the request

Try once more with the service, recipient, and business need. If Flow still cannot find a
requestable service or safe action:

* Use the Slack, Microsoft Teams, or email channel your organization provided for the team.
* Ask an administrator whether the service has been published for you and which team channel to
  use.
* Contact the team through that channel if Flow returns an unexpected error.

Do not open a duplicate when Flow already created a conversation.

## Fields Flow may collect

| Field | Meaning |
| - | - |
| Requested for | Who receives the access or service |
| Target team | Team that owns fulfillment |
| Justification | Business reason for reviewers |
| Requested duration | Time-bound access when your org uses expiring grants |

Exact fields depend on each catalog item your builders published.

## Related topics

* [Channels](/setup/channels/overview)
* [Request tracking](/setup/request-tracking)
* [Access](/setup/access)


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