Skip to main content
This checklist gets a small team from zero to a credible pilot: verified accounts, a safe place to collaborate, and one integration proving data can flow in and out. Adjust order if your security team requires SSO before invites.

Before you begin

  • A verified email you can access
  • Admin access if you are enabling SSO later
  • Rough idea of who belongs in the pilot (five to fifteen people is typical)
If you are migrating from another tool, keep a CSV of users and roles handy—you will move faster than recreating access from memory.

Steps

  1. Create your organization — Pick a name your team will recognize in notifications. Avoid internal codenames if customers might see the name on shared artifacts.
  2. Invite teammates — Start with a small pilot group before rolling out widely. Ask them to accept within a week so you are not debugging expired invites during launch.
  3. Connect one integration — Choose Slack or your CRM to see data flow end to end. Validate credentials in a sandbox or test channel first.
  4. Create a first project — Use it as a sandbox for workflows and permissions. Seed a few realistic tasks so demos feel grounded.

Time checks

If any step waits on IT (DNS, SSO metadata, firewall rules), parallelize what you can—draft project structure while tickets move.

Next steps

Review sign-in and security and explore the workspace guides when you are ready to tighten access. Consider a short retro after week one: what confused newcomers, which doc they opened first, and whether search surfaced the right page.