Roll out tutors to your team

2026-07-07 · The Alltutors.ai team

What you'll set up

You've built a tutor and it works. Now someone else needs in. A hiring wave is landing, and right now a new hire's first month rides on which manager they drew. Or a recert deadline just hit your desk and "everyone clicked through it" won't survive the audit. Either way the tutor stops being a one-person project, and you need three things: a workspace, roles, and analytics that tell you whether people are ramping. One more angle if a senior person is about to leave: capture what they know into a tutor once, so every new hire learns the same thing instead of a coin flip on their buddy.

Step 1: Understand your workspace

Every account gets a workspace the moment you sign up, named after you, so you can start building alone with nothing to set up. When you're ready to bring people in, you invite them straight into that workspace: a shared home where teammates see and build tutors together. Need to keep some work separate? You can create more than one workspace and switch between them.

Tip: one workspace is enough to start. Create a second only when you genuinely want a separate space, say a different team or client. Moving tutors between workspaces later is manual, so it's easier to decide upfront.

Step 2: Know the three roles

A workspace has three roles: owner, admin, and editor.

• An owner has full control: rename the workspace, invite or remove anyone, change anyone's role, delete the workspace, and everything an editor can do.
• An admin can invite people, manage most workspace settings, and do everything an editor can do, but can't do the things reserved for the last remaining owner (a workspace always needs at least one).
• An editor can build, edit, and use tutors and materials inside the workspace, but can't invite people, manage connectors, or change workspace settings.

One asymmetry to know: an owner can't just leave, since a workspace always needs at least one. They hand the owner role to someone else first, then leave as an admin. An admin can leave any time.

Step 3: Invite your teammates

From the workspace's members view, invite someone by email and pick their role: admin or editor. That creates a pending invite and sends them an email with the link; you also get the link to share directly, over Slack or wherever you'd normally reach them. The link is single-use and tied to that email address, and it expires after a set window if nobody accepts. You can invite several people at once, each with their own role.

Once someone accepts, they show up in the roster with their role attached. You can revoke a pending invite any time before it's accepted, and change or remove someone's role later if the team's shape changes.

One thing to size before a big rollout: provisioning is manual today. One invite, one link, per person. That's fine for a pilot cohort. There's no SCIM, HRIS sync, or LMS handoff yet, so pushing seats to a few hundred people is hand work for now. Factor that into your timing.

Tip: invite people as members first and promote to admin once you know they need to manage the workspace itself, not just build inside it. It's a smaller mistake to fix than the reverse.

Step 4: See whether the tutor is working

The owner analytics live behind your dashboard. Rolled up across the workspace and for every tutor individually, you get a completion rate, a session count, and average time spent, windowed to the last 7, 30, or 90 days. Drill into one tutor and you also get a recent-sessions list, so you can see which lessons people are actually opening.

Completion tells you people are moving through. For onboarding, map it to your 30/60/90 ramp: are new hires finishing the tutor in their first weeks, and do the same repeat questions stop landing in your managers' laps once they have. For a compliance or upskilling rollout, it's completion against the deadline.

Sessions and time spent are the numbers worth watching alongside completion. A slide deck tells you someone clicked through once; a session count and the minutes behind it tell you whether people are actually sitting with the material. It's a fuller picture than completion alone, and still a proxy: it measures engagement, not whether someone can apply what they studied on the job. When sessions taper off partway through a rollout, that's worth a look before the deadline, not after. We wrote more about why click-through completion is a weak signal in completion isn't competence, worth reading before you report these numbers to anyone above you.

Step 5: Report up

You're already looking at the numbers you'll report. For an L&D or compliance lead, lead with engagement, not just click-throughs. When the budget review comes and someone asks you to justify the line, sessions and time spent are the ROI story; completion alone reads as busywork. For an onboarding lead, show your Head of People that time-to-productivity moved: new hires finishing sooner and studying more consistently.

Set a baseline before you set a target. Raw numbers don't say much on their own; the trend against a starting point does. And the real bottleneck of most rollouts isn't reporting, it's adoption. Getting people to actually open the tutor is the work.

Tip: if completion stalls or sessions drop off partway through a rollout, treat it as feedback on the tutor's plan, not on the learners. Go back into the plan and ask the tutor to tighten pacing or add support around the point where people seem to lose momentum, then watch the numbers over the next window.

What isn't live yet

SSO and audit logs are planned for Team plans, not shipped today. Bulk provisioning is the same story, as covered above: seats go out one invite at a time.

That draws a clean line on what fits Alltutors.ai now. Onboarding, upskilling, and development rollouts work today, where the goal is consistent ramp and genuine engagement. For mandatory or regulatory training, harassment, security, AML/KYC, annual recerts, hold until audit logs and content-locking ship. You need a defensible per-employee record there, and click-through completion won't survive an audit. We won't pretend it does.

If you need data-processing terms for a school, company, or other organization, reach out. Our privacy policy covers how we handle organizational and learner data, and our security page covers how content is protected at rest. For what a larger rollout looks like end to end, our enterprise page is the place to start.

Where to go from here

If you haven't built a tutor yet, start with building your first tutor; everything here assumes you already have one to share. If a hiring wave is what brought you here specifically, our piece on designing a week-one onboarding tutor covers what to load and what to check before the workspace side even matters. Once your workspace and roles are set up, invite the people who need to build alongside you. Check back on the analytics after a week or two of real use. That's usually enough for completion and engagement to say something meaningful.

Start building, or read through what a full organizational rollout looks like if you're planning for more than a handful of people.