For teams

Build AI with your whole team.Keep production in safe hands.

Bring everyone into one organization to work on the same projects and workflows. Four roles decide who can test, edit, publish and manage billing, and protected projects stay out of reach of accidental changes.

A team working on laptops around a shared wooden table

How teams work in ModelRiver

One organization holds your projects, workflows, keys and logs. The people you invite work inside it, each with the access their role allows.

  1. 01

    Invite your team

    The Owner invites people by email from Team members and picks Admin, Editor or Viewer for each. New invites start as Editor.

  2. 02

    Protect what’s live

    An Owner or Admin marks a production project as protected. Editors can still test it, but they can’t change its keys, workflows or webhooks.

  3. 03

    Review before you publish

    Edits are saved to a Draft, so production doesn’t change. An Owner or Admin compares it with Live, publishes it, and can roll back.

  4. 04

    Require two-factor

    Turn on one setting and every member has to set up an authenticator app before they can use the console.

Who can do what

Roles apply to every project in the organization. Pick one when you invite someone; the Owner can change it later.

ActionOwnerOrg and billingAdminAll projectsEditorBuild and testViewerRead only
Build and ship
See every project, its workflows and logsAllowedAllowedAllowedAllowed
Test workflows in the PlaygroundAllowedAllowedAllowedNot allowed
Edit workflows, API keys, provider keys and webhooksAllowedAllowedUnprotected onlyNot allowed
Publish and roll back workflow releasesAllowedAllowedDrafts onlyNot allowed
Import workflows into a projectAllowedAllowedNot allowedNot allowed
Projects and records
Create projects, change their settings and protect themAllowedAllowedNot allowedNot allowed
View and export the audit log Scale and EnterpriseAllowedAllowedNot allowedNot allowed
Download request logs as CSV or JSONL Scale and EnterpriseAllowedAllowedNot allowedNot allowed
Access and the organization
Require two-factor for every memberAllowedNot allowedNot allowedNot allowed
Set up and require single sign-on Scale and EnterpriseAllowedView onlyNot allowedNot allowed
Invite and remove members, change rolesAllowedNot allowedNot allowedNot allowed
Billing, plan and organization settingsAllowedNot allowedNot allowedNot allowed

Every action is checked on our servers, not just hidden in the console. Read the full rules

What each plan gives your team

Free is for one person. Every paid plan has roles and protected projects, and larger plans add the records and commitments security reviewers ask for.

Compare plans and prices

Security and contracts

What your security and legal reviewers will ask for, and where to find it. We list what we don’t have yet too.

Frequently asked questions

How many people can I add?

Free is for one person. Pro includes 10 team seats and Scale has unlimited seats.

What’s the difference between an Owner and an Admin?

Admins can do everything with projects: create them, change their settings, protect them, import workflows, and publish or roll back releases. Only the Owner invites and removes members, changes roles, and manages billing and organization settings. Invites hand out Admin, Editor or Viewer, never Owner.

Can I give someone access to just one project?

No. Roles apply to every project in the organization. To stop Editors from changing a project, have an Owner or Admin protect it.

Does protecting a project stop production traffic?

No. Requests made with the project’s API keys keep running, and logging, usage and spend tracking carry on. Protection only blocks changes to how the project is set up.

Can Viewers use the Playground?

No. Viewers can look at every project but can’t run tests or change anything. Give someone the Editor role if they need the Playground.

How long does an invite stay valid?

7 days. The Owner can resend or cancel a pending invite from the Team members page.

Can I require two-factor authentication for everyone?

Yes. The Owner can turn on one setting that makes every member set up an authenticator app before they can use the console. It works for people who sign in with Google or GitHub too.

Can we sign in through our identity provider (SSO)?

Yes, on Scale and Enterprise plans. Connect Okta, Microsoft Entra ID, Google Workspace or another OpenID Connect provider and verify your email domain. The Owner can then require single sign-on, so someone you remove at your identity provider loses access within 12 hours. Your applications keep calling the API with API keys.

Can I see who changed what?

Yes, on Scale and Enterprise plans. Owners and Admins can open the organization menu and select Audit log to see sign-ins, invitations, role changes, project changes and protection, API key and provider key changes, and workflow publishes and rollbacks. You can filter it and download any date range as CSV. Activity is recorded on every plan and kept for 12 months (24 on Enterprise), so it’s there when you upgrade.

Can we export our request logs?

Yes, on Scale and Enterprise plans. Owners and Admins can open Request Logs in a project, select Download, pick a date range and choose CSV or JSONL. Prompts and responses are left out unless you include them, and every download is recorded in the audit log.

Bring your team into one workspace

Start free on your own, then move to Pro to invite up to 10 teammates. Need more seats or custom terms? Tell us what you’re building.