Rolling Scholarly Out to Your Team

Buying seats is the easy part. This guide is about the part that decides whether a team workspace sticks: what goes in it, who starts, and how you know it's working.

It assumes you've already created a workspace. If you haven't, start with Getting Started with Teams — the free trial includes 3 seats, so you can run week one before paying anything.

Week 1 — Pick one job, not the whole company

The most common way a rollout stalls is starting with "everyone can use it for anything." Pick a single recurring job your team already does badly or slowly:

• Onboarding — turn the handbook, the policy PDFs, and a recorded walkthrough into a study pack and a quiz new hires actually finish.
• Product or sales enablement — turn release notes and spec docs into a short video explainer and a one-page brief per release.
• Training material — turn a subject-matter expert's recorded session into a lesson plan, a worksheet, and a set of flashcards.
• Client or research work — turn a stack of reports into a cited research summary the whole team can question.

Do that one job yourself, end to end, before inviting anyone. You'll produce the first useful artifact and learn what the shared library needs.

Week 1 — Seed the shared library

An empty library is the single biggest predictor of a rollout that doesn't take. Before people arrive, put real material in:

1. Create one folder for the job you picked.
2. Add the source documents, recordings, and decks people actually reach for — not summaries of them.
3. Open Share on the folder and choose Your team.

Share the sources, not just the outputs. A shared PDF can be turned into a dozen different things by a dozen different people; a shared summary can only be read.

See Sharing with Your Team.

Week 2 — Invite the right first people

Invite the two or three people closest to that job, not the whole department. Give at least one of them Admin so you're not the only person who can add seats or fix access.

Send invitations from Team → People, or create a join link and drop it in your team chat. Point everyone at the folder you seeded and one concrete thing to try: "make yourself a quiz from the onboarding folder" beats "have a play with it."

Week 2 — Set the guardrails once

Two admin settings are worth deciding early, in Team → Settings:

• Model access — which model tiers members can use.
• Require Zero Data Retention — if your organization has a data-handling policy, turn this on and only models on approved zero-retention routes stay available.

Then set up a Profile under Team → Profiles: shared instructions, a preferred model, and your visual identity. Every teammate's slides, documents, and videos come out looking consistent without anyone re-typing the brief.

See Managing Your Team for both.

Week 3–4 — Check adoption honestly

Open Team → Usage. You're looking for one thing: is more than one person creating?

• Several active members, steady creations — it's working. Add the next job and the next folder.
• Activity concentrated in you — almost always an empty or wrong-shaped library, not disinterest. Ask the quiet members what they were trying to do, and add the source they needed.
• People creating but not returning — the output was interesting rather than useful. Move to a job with a deadline attached to it.

Usage reporting is aggregated on purpose: it shows adoption, never the contents of anyone's work.

Then expand

Once the first job is running without you, repeat it: new folder, new job, invite the people who own it. Seats can be added at any time from Team → Billing, and pending invitations hold a seat until they're accepted.

Common questions

Do people need training? No. Point them at one folder and one task. The tools explain themselves once there's real material to point them at.

What if someone already pays for Scholarly personally? They keep whichever plan is stronger. Joining a team never downgrades anyone.

Can people see each other's private work? No. Content is private until someone explicitly chooses Your team, and admin reporting shows counts, not content.

What if we outgrow 29 seats? That's the self-serve ceiling. Contact us from the Teams page and we'll take it from there.

Related

• Getting Started with Teams — create the workspace and invite people.
• Sharing with Your Team — build the shared library.
• Managing Your Team — roles, model access, profiles, and reporting.
• Teams plans — trial, pricing, and what each seat includes.