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

# Deployment Checklist

> Step-by-step checklist for bringing Serval live in your organization, with links to the detailed setup guide for each area.

# Deployment Checklist

Use this page as your checklist for bringing Serval live in your organization.
Work through the steps in order — each links to the detailed setup guide for that
area.

<Info>
  Have self-hosting requirements? Read the [Self-Hosting Options](/sections/self-hosting/index) page first.
</Info>

## Go-live checklist

<Steps>
  <Step title="Choose your front door">
    Decide where employees reach Serval — [Slack](/sections/integrations/slack)
    (channels and [direct messages](/sections/documentation/helpdesk/interacting-with-serval-in-slack#direct-messages-dms)),
    [email](/sections/documentation/helpdesk/email), or
    [Microsoft Teams](/sections/integrations/microsoft-teams). A web portal is
    available automatically. See [Channels](/sections/documentation/helpdesk/channels#available-channels)
    for the full list.

    <Check>Employees can reach Serval through at least one channel.</Check>
  </Step>

  <Step title="Connect your core integrations">
    Connect your identity provider, communication tools, device management, and any
    existing ticketing or other systems you want Serval to work with. After
    connecting each app, open its **Settings → Sync History** to confirm syncs are
    completing cleanly.

    * [Browse integrations](/sections/integrations/overview) and review [Sync History](/sections/integrations/overview#integration-sync-history)
    * [Connect your identity provider](/sections/access-management/configuration/connect-idp) (Okta, Microsoft Entra, Google Workspace, Rippling)
    * Device management — Jamf, Kandji, and Mosyle

    <Check>Each core integration shows recent, successful syncs.</Check>
  </Step>

  <Step title="Configure ticketing">
    Set up the building blocks, then use them to route work:

    * [Categories](/sections/documentation/ticketing/ticket-configuration/categories), [labels](/sections/documentation/ticketing/ticket-configuration/labels), [priorities](/sections/documentation/ticketing/ticket-configuration/priorities), and [statuses](/sections/documentation/ticketing/ticket-configuration/statuses)
    * [Schedules](/sections/documentation/ticketing/ticket-configuration/schedules) and [SLAs](/sections/documentation/ticketing/ticket-configuration/slas)
    * [Assignment rules](/sections/documentation/ticketing/ticket-configuration/assignment#how-assignment-rules-work), built from the items above

    <Check>New tickets are categorized, prioritized, and routed automatically.</Check>
  </Step>

  <Step title="Install workflows">
    Automate common requests. Install [pre-built workflows](/sections/documentation/workflows/Configure/installable#how-it-works)
    for your connected apps, or [build your own](/sections/documentation/workflows/create-your-first-workflow).
    Browse [examples by integration](/sections/documentation/workflows/Configure/installable#example-workflows-by-integration)
    for ideas.

    <Check>Your highest-impact requests have a workflow in place.</Check>
  </Step>

  <Step title="Populate the Knowledge Base">
    Give the agent reference material to answer from:
    [connect a documentation source](/sections/documentation/knowledge-base/overview)
    (Notion, Confluence, Google Drive, SharePoint, ServiceNow, and more) or add a
    [custom ingestion workflow](/sections/documentation/knowledge-base/overview#path-2-use-a-custom-knowledge-ingestion-workflow).
    Knowledge is what the agent *knows*; [skills](/sections/documentation/skills-vs-knowledge)
    are how it *acts*.

    <Check>The agent can answer questions from your own content.</Check>
  </Step>

  <Step title="Test before launch">
    Send representative requests through your front door and confirm routing, answers,
    and workflows behave. At a minimum,
    [submit a test ticket, verify user sync, and run a test automation](/sections/documentation/overview/day-1-setup#post-setup-verification).

    <Check>An end-to-end request works, from submission through resolution.</Check>
  </Step>
</Steps>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Why do some pages — or parts of a page — get stuck loading?">
    This usually means a security proxy or WAF on your network is buffering or
    inspecting Serval's streaming responses, so the live part of a page never loads.
    See [Streaming pages behind a WAF or proxy](/sections/administration/network-security-and-firewalls#streaming-pages-behind-a-waf-or-proxy)
    for the fix.
  </Accordion>
</AccordionGroup>

## See also

* [Day 1 setup](/sections/documentation/overview/day-1-setup) — the guided quickstart companion to this checklist.
* [Self-Hosting Options](/sections/self-hosting/index) — choose a delivery model if you're running Serval yourself.