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

# Before you start

> How to get a Ravenna organization: reach out to the team, then have Slack admin access, a first team, and your knowledge sources ready for setup.

Ravenna is set up with you, not around you. Every organization is provisioned by the Ravenna team, so getting started is a conversation rather than a form to fight through: what you are trying to fix, which team goes first, and where your answers already live.

<Card title="Ready to start?" icon="handshake" href="https://ravenna.ai/contact" cta="Request access" arrow="true">
  Tell the team which department you want to launch and they will provision your organization.
</Card>

<Callout icon="link" color="#6B7280">Already have an organization and an invitation email? Skip ahead to [Day one](/guides/day-one/overview)</Callout>

## How it works

<Steps>
  <Step title="Reach out" icon="send">
    Say which team you want to launch and which tools they live in. That is enough to start.
  </Step>

  <Step title="Meet on a call" icon="phone">
    The team learns what you are trying to fix, provisions your organization, and points the first workspace at the right channels and knowledge.
  </Step>

  <Step title="Sign in and build" icon="key-round">
    An invitation lands at the email address you gave, and the [Day one](/guides/day-one/overview) track picks up from there.
  </Step>
</Steps>

## What to have ready

None of this is required to reach out, but having it settled makes the difference between finishing setup on the call and finishing it a fortnight later.

<AccordionGroup>
  <Accordion title="Slack admin access" defaultOpen>
    Installing the Ravenna Slack app is an org-wide action, so someone who can approve app installs needs to be available. It happens once, no matter how many Ravenna workspaces you end up with.

    On Microsoft Teams instead? Ravenna supports Teams, and setup follows the same shape. Say so on the call so the right app gets installed first.

    <Callout icon="link" color="#6B7280">Learn more about the [Slack app](/integrations/slack/setup) and the [Microsoft Teams integration](/integrations/microsoft-teams/overview)</Callout>
  </Accordion>

  <Accordion title="Which team goes first, and who runs it">
    Pick one team, not three. IT and People Operations are the usual starting points because their request volume is high and repetitive, which is exactly what an AI agent is good at.

    That team becomes your first [workspace](/documentation/platform/workspaces/overview), and others can be added later without redoing anything. Decide who administers the organization and who administers that first workspace. They are separate roles, and the second one is the person who will actually configure forms, knowledge, and agents day to day.

    <Callout icon="link" color="#6B7280">Learn more about [roles and access](/documentation/platform/roles-access)</Callout>
  </Accordion>

  <Accordion title="Where requests arrive today">
    Ravenna meets people where they already ask. Have an answer for each of these:

    * Which Slack channel do people currently use? Ravenna connects to the channel you already have.
    * Is there a shared inbox, such as `it@yourcompany.com`, that should also create tickets?
    * Do you have staff who do not use Slack? They get the [Portal](/documentation/platform/portal).
    * Are you migrating from another tool, such as Zendesk or Jira Service Management?
  </Accordion>

  <Accordion title="Where your knowledge lives">
    The AI answers from your documentation, so knowing which sources matter shortens setup considerably. Ravenna indexes Slack, Notion, Confluence, Google Drive, GitHub, Coda, Guru, Zendesk Help Center, and public websites.

    Bring the two or three that hold your real answers, along with someone who can authorize the connection.

    <Callout icon="link" color="#6B7280">Learn more about [knowledge sources](/documentation/automate/knowledge/overview#knowledge-sources)</Callout>
  </Accordion>

  <Accordion title="An identity provider, if access requests are in scope">
    If you want Ravenna to grant and revoke application access rather than just track the request, you need an identity provider connected, typically Okta, Entra ID, or Google Workspace.

    This is worth flagging early because it usually involves a second team.

    <Callout icon="link" color="#6B7280">Learn more about [access provisioning](/documentation/automate/access-provisioning/overview)</Callout>
  </Accordion>
</AccordionGroup>

<Card title="Day one" icon="arrow-right" href="/guides/day-one/overview">
  Nine steps from an empty workspace to a live AI service desk.
</Card>


## Related topics

- [Set up your first channel](/guides/day-one/set-up-first-channel.md)
- [Guides](/guides/overview.md)
- [Employee offboarding](/guides/playbooks/hr/employee-offboarding.md)
- [Set up your first workspace](/guides/day-one/set-up-workspace.md)
- [Slack Workflow Builder](/integrations/slack/workflow-builder.md)