Getting Started with Teams

Setting up a team takes a few minutes and no sales call. Setup walks you through five steps in order — name your team, add your first source, invite teammates, choose seats, choose a plan — and you can step back through any of them without starting over.

If you already belong to another team, or a checkout is already in progress, finish or cancel that before starting a new Teams checkout.

1. Name your team

Choose Set up a team, name the workspace, and say what your team does. That answer matters: it decides what Scholarly drafts for you in the next step.

2. Add your first source

One file, link, or item from your library is enough. This is the step that makes the rest of setup worth doing.

From that single source Scholarly:

• creates a team-owned project carrying shared instructions, so it belongs to the team rather than to you;
• shares the source with the team, so it's in the Library before anyone arrives;
• drafts a first artifact matched to the job your team named — an SOP for onboarding and documentation, a report for research and marketing, a case study for client work.

The draft keeps building in the background while you carry on to invites, and it's shared with the team when it lands. You don't have to wait for it.

3. Invite teammates

The free trial includes up to 3 seats, so you can invite 2 people immediately — no payment first.

Enter email addresses, choose Member or Admin for each person, and send. You can also copy a join link and drop it into your own chat tool. Pending invitations hold a seat until they're accepted, revoked, or expire.

The invite step shows you what teammates will see on arrival, and offers to share something first if the Library is still empty. Invite emails list the most recently shared work as links — which is why adding a source before you invite is what makes the invite land.

During the trial, each person's AI models and limits come from their own personal plan. Buying a team plan is what gives every seat the same Premium or Laureate access.

See Joining a Team for what your teammates see.

4. Choose seats

Set how many seats you want. The paid seat count has to cover active members plus pending invitations, and seats can be changed later from Team → Billing.

5. Choose a plan

Pick Premium for Teams or Laureate for Teams, choose monthly or yearly billing, and review the per-seat total at checkout:

Yearly billing saves 20%. Teams is self-serve for 1–29 seats; for more than that, or for invoicing and purchase orders, contact us from the Teams page.

Or select Try the product first and come back to Team → Billing → Upgrade Team whenever you're ready.

Checkout upgrades the existing workspace in place: same content, same people, same projects. It does not change the personal plan on your account, and your private content stays yours. If you leave checkout part-way, the trial workspace stays exactly as it was.

What each paid seat gets

Every seat gets the full plan, not a cut-down team version:

• Premium for Teams — 15 AI Creation Credits each week, unlimited AI Chat, 20 meetings a week up to 10 hours each, uploads to 300 MB, 1,000-page PDFs, editable Word/PowerPoint/Google exports.
• Laureate for Teams — 80 AI Creation Credits each week, 100 meetings a week, uploads to 1 GB, 3,000-page PDFs, priority generation, and the Frontier models by name.

Both allowances reset every Monday at 00:00 UTC, and each person's are their own — there is no shared pot for the team to run down. Each member sees their own balance in Settings → Usage.

When someone runs out mid-week

A seat that uses all of its weekly AI Creation Credits is not stuck until Monday. The limit notice opens that person's usage and offers a credit pack, and an Owner or Admin can buy a pack for any member on the team's bill from Team → Overview or Team → Billing. Those credits go to that member, never expire, and are spent only after their weekly allowance. Nobody has to buy a second subscription to get past a wall. See AI Credit Packs.

Build out the shared Library

This is the step that decides whether a team workspace sticks. Upload the material your group actually reaches for — onboarding docs, product specs, policy PDFs, recorded calls and training sessions, the reports people keep re-reading.

Put related material in a folder, open Share, and choose Your team. Shared items land in the team Library, which is what teammates open when they arrive. Everyone can browse it and create their own grounded work from it, while ownership stays with the person who shared it. Nothing you keep outside the team is exposed by joining one.

A good starting shape is one folder or team project per recurring need — Onboarding, Product, Policies, Customer calls — rather than one per person.

Watch adoption

Open Team → Overview → Activity. It shows the last 30 days by default, and you can switch to the last 7.

It leads with completed creations broken down by type, then active members, AI generations, chat messages, and study sessions, with a per-member breakdown behind a disclosure. These are adoption signals, not a spend ledger; there is no shared wallet to run down. Each member sees their own limits in Settings → Usage.

If activity is concentrated in one or two people after the first fortnight, the usual cause is a thin shared Library rather than a lack of interest. See Rolling Scholarly Out to Your Team.

Related

• Scholarly Teams — trial, paid plans, pricing, seats, and roles.
• Managing Your Team — invitations, roles, model policy, billing, and Activity.
• Your Team Library and Team Projects — the Library tab and team-owned projects.
• Rolling Scholarly Out to Your Team — a practical first-month plan.
• Sharing with Your Team — build and use a shared Library.
• AI Credit Packs — topping up a member who has used their week's credits.
• Data, Privacy, and Model Controls in Teams — the answers a security or procurement review will ask for.