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

# Set up your workspace

> Set up your first Flow team and verify that a requester can get help.

## Quick setup

Use this procedure to launch one team before expanding to more teams or services.

<Steps>
  <Step title="Complete Quick setup.">
    Open **Settings → Quick setup** and work through the activation checklist. Use it while onboarding is in progress.
  </Step>

  <Step title="Invite operators.">
    Under **Settings → Users**, invite the people who need browser access and assign organization administrators. Chat requesters do not need an invitation.
  </Step>

  <Step title="Configure your team.">
    New workspaces include a **Flow Admin** team. The founding administrator is its **Manager**. In **Settings → Flow Teams**, configure that team or create another team for your service. Add members, choose their roles, and enable the capabilities the team needs. See [Teams](/setup/teams).
  </Step>

  <Step title="Choose a requester channel.">
    Every team has an email inbox, but email from new requesters requires Directory Sync. Complete it under **Settings → Identity** before sharing the address (see [Email prerequisites](/setup/channels/email) for the existing-member exception). Slack, or Microsoft Teams, can accept requests without Directory Sync; connect the organization's primary chat provider and link the team to a channel. Connect Directory Sync when approvals or membership need manager, employee, or group context. See [Directory Sync tradeoffs](/setup/administration/identity-and-directory#when-to-connect-directory-sync). Set up at least one route and tell requesters which to use. See [Channels](/setup/channels/overview).
  </Step>

  <Step title="Connect only the systems needed for the first service.">
    Use [Integrations](/integrations) for identity, knowledge, assets, ticketing, and automation provider connections. After connecting a knowledge source, run the initial sync and confirm that content is available before relying on it. See [Automation integrations](/automations/connectors) for the actions and permissions available to automations.
  </Step>

  <Step title="Confirm a requestable service is available.">
    Before testing, ensure that the team has at least one published catalog item. For access requests, review the catalog item, approval policy, and fulfillment connection in [Access](/setup/access) and [Application access](/setup/applications).
  </Step>

  <Step title="Run a controlled requester test.">
    Ask for the published service through the connected requester channel and answer the follow-up questions. Then have an operator open the resulting conversation, check its status and related approval or automation run, and confirm the team can reply through the selected channel. See [End user](/setup/end-user), [Help desk](/setup/help-desk), and [Request tracking](/setup/request-tracking).
  </Step>
</Steps>

## Readiness checklist

Your workspace is ready for the first team when:

* Quick setup shows its activation checks passed.
* The team has members, appropriate roles, enabled capabilities, and a known requester channel.
* The required integration or source connection is ready.
* At least one catalog item is published for the team.
* A requester test creates a conversation that an authorized operator can review and follow through its approval or automation work.

## Related topics

* [Teams](/setup/teams)
* [Identity and directory](/setup/administration/identity-and-directory)
* [Channels](/setup/channels/overview)
* [Day 1 setup](/setup/day-1-setup)


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