Skip to content
RolloutDocs
NL
Documentation for MSPs and administrators

Take Rollout live,
step by step.

From an empty database to your first client: in seven steps, with animations that show what happens and exactly what to enter where.

Start here Go to the checklist

Allow 1 to 1.5 hours for a complete go-live.

How Rollout fits togetherEmployees and clients only talk to the Rollout server, which calls the database with a secret key and reads from Microsoft 365. After signing in, engineers also work directly with the database, protected by Row Level Security. Calling the public functions directly without the key is refused.Engineerssign in with MicrosoftEmployeesand clients: booking, portalSomeone elsedirectly on the APIRollout serverdomain · CSP · gatewayDatabaseRow Level SecurityMicrosoft 365client tenants, read-onlykeyRLS

Going live in seven steps

Follow them in this order. Each step says what you need, what you do and how you check that it works.

  1. 1
    Set up the database
    Supabase project, migrations and the first administrator.
    Open →
  2. 2
    Sign in with Microsoft
    App registration Rollout – Login and the Supabase provider.
    Open →
  3. 3
    Connect client tenants
    Rollout – Readiness, federation and client consent.
    Open →
  4. 4
    Hosting on Vercel
    Project, region and environment variables.
    Open →
  5. 5
    Turn on the server gateway
    The database only accepts public functions from your own server.
    Open →
  6. 6
    Your own (sub)domain
    Connect rollout.company.com or company.rollout365.com.
    Open →
  7. 7
    Go-live checklist
    Tick everything off before the first client goes in.
    Open →

After going live

Day-to-day use, operations and the background of how Rollout protects your data.

Security centerSessions, Teams alerts, maintenance and GDPR.
One-click fixChanges in a client tenant, with four eyes.
LicenseHow the offline license works and what happens when it expires.
Updates and operationsUpdating, replacing secrets, incidents and offboarding.
How Rollout protects your dataThe security model in layers, with evidence.
Self-hosting (Docker)Behind your own firewall, with Caddy and a separate admin address.
TroubleshootingCommon messages and what to do about them.
Rollout Docs · Rollout Docs