Scholarly Teams

Scholarly Teams is one shared workspace for a group: a shared Library of your organization'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.

Start with the free trial

A new team workspace starts as a free trial with up to 3 seats. That is a real workspace, not a preview: you can invite 2 teammates by email or join link right away, assign them Member or Admin, and build a shared Library together before you pay anything.

During the trial, each person's AI models and usage limits come from their own personal plan. There is no team plan applied yet.

Then choose a paid plan

When you're ready, the owner or an admin 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.

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, during the trial, of each person'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.

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.

During the trial there is no team plan yet, so every person — including invited teammates — runs on the models and limits of their own personal Scholarly plan. Buying Premium or Laureate for Teams is what 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 adoption reporting shows counts rather than content.

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 behavior is separate from Teams and does not change either self-serve Teams plan. For a larger organization, school, or district, contact us from the Teams page.

Related

• Getting Started with Teams — setup, invitations, and a shared Library.
• Managing Your Team — seats, roles, model policy, billing, and Activity.
• Your Team Library and Team Projects — the shared Library and team-owned projects.
• Data, Privacy, and Model Controls in Teams — what a security reviewer will ask about.
• Rolling Scholarly Out to Your Team — a practical first-month plan.
• Plans and Limits — the Premium and Laureate limits each seat inherits.