GuideTeams Overview

Scholarly Teams

Scholarly Teams is one shared workspace for a group: a shared Library of your organisation's documents, projects owned by the team, roles, adoption reporting, and a single bill. It is not a course platform or an LMS, it is the same Scholarly you already use, pointed at your team's material.

Teams is self-serve for 1–29 seats.

Before you choose a plan

A new team workspace has one seat, yours. You can name the team, add sources, and set up the shared Library, but there is no team plan yet: your AI models and usage limits come from your own personal plan, and the workspace adds no Premium or Laureate features.

Upgrade your team plan to unlock more: seats for teammates, invitations, and Premium or Laureate for every seat. Invites you add during setup wait and are sent once you choose seats.

Choose a team plan

When you're ready, the owner upgrades the same workspace in place, the content and the people stay exactly where they are. Checkout shows the exact plan, seat quantity, cadence, and total before payment.

Plan Monthly Yearly
Premium for Teams $35 per seat each month $336 per seat each year, about $28 per seat a month
Laureate for Teams $110 per seat each month $1,056 per seat each year, about $88 per seat a month

Every Premium seat gets Premium models, features, and weekly limits. Every Laureate seat gets Laureate, including its 80 weekly AI Creation Credits and the Frontier models by name.

Yearly billing saves 20%. The minimum is 1 seat, and the paid seat count has to cover active members plus pending invitations. These are the fixed USD price points; in supported markets checkout can charge the current equivalent in your local currency, and there is no lower country-specific Teams tier.

Owners and admins manage all of it from Team → Billing → Manage billing: seat quantity, payment method, invoices and receipts, and renewal terms. See Managing Your Team for seat mechanics.

Need more than 29 seats, a rollout across departments, or invoicing and purchase orders? Contact us from the Teams page.

What every seat includes

  • The AI models, tools, and usage limits of the team plan you bought (or, before you choose a team plan, the owner's own personal plan).
  • A shared team Library, everything anyone shares with the team, sources and finished work together, in one place every member opens.
  • Projects owned by the team rather than a person, so shared work survives whoever set it up.
  • Owner, Admin, and Member roles.
  • Team-wide model policy controls.
  • Adoption reporting over the last 30 days, or the last 7.
  • A per-seat subscription and a billing portal after checkout.

No shared wallet

There is no shared token pool, weekly team credit wallet, or separate cost per AI action. Each member has their own plan counters, uploads, PDFs, voice, study, and creations are tracked per person, so one teammate's activity never reduces another's allowance.

When a member runs out of weekly AI Creation Credits, an Owner or Admin can buy them a one-time credit pack on the team bill from Team → Overview or Team → Billing. Pack credits go to that member and never expire. See Managing your team.

If someone's personal subscription is stronger than the team plan, theirs still wins: Scholarly uses whichever entitlement is more capable. A member who has Laureate personally keeps Laureate's larger weekly allowance on a Premium team, and team checkout never changes anyone's personal plan.

Until the owner buys a team plan, the workspace has no team plan, so it runs on the owner's own personal Scholarly plan. Buying Premium for Teams or Laureate for Teams is what adds seats and lifts every seat onto the same plan.

Roles

  • Owner: full workspace and billing control.
  • Admin: can manage seats, invitations, roles, model policy, and billing.
  • Member: uses the team's Premium or Laureate access and the shared Library.

An account can be an active member of only one team at a time.

Data and model controls

Admins choose which AI models the team may use from Team → Billing → Plan & AI models, model by model or by tier, and can require Zero Data Retention routes for the whole team. Private content is not used to train general-purpose AI models by default, and usage reporting shows counts. Shared-lecture reports additionally show progress, completion, and question scores for video lectures and podcasts already shared with the team.

The full answer, training, hosting regions, what admins can and cannot see, and connected accounts, is in Data, Privacy, and Model Controls in Teams.

Enterprise

Standalone Enterprise agreements remain a separate, sales-assisted product and may retain their existing credit ledger. That legacy behaviour is separate from Teams and does not change either self-serve Teams plan. For a larger organisation, school, or district, contact us from the Teams page.

Was this helpful?