DocsCatalogPricing
Sign inStart research

Start

Docs homeGetting started

Product

WorkspaceLibrary filesAbstractsPresentationsDashboards

Admin

OrganizationsSecurity & privacy

Developers

Developer APIMCP serverIntegrationsTool catalog

Documentation

Docs homeGetting startedWorkspaceLibrary filesAbstractsPresentationsDashboardsOrganizationsSecurity & privacyDeveloper APIMCP serverIntegrationsTool catalog
Documentation

Organizations & workspaces

How Cortexa separates your Personal workspace from team organizations: creating an org, inviting teammates, roles, switching workspaces, sharing, and team billing.

Organizations
Northstar Research Lab
4 members · owner-managed
JR
Jordan Rivera
Active
Owner
AK
Aria Khoury
Active
Admin
MS
Mira Solanki
Active
Researcher
DT
Devin Tran
Active
Researcher
RP
Riya Patel
Invitation sent · awaiting accept
Researcher
riya@northstar.bio
Invite
Plan
Team · Pro
Annual · renews Mar 2027
Seats
4 / 12
Step budget
12 / run
Roles
  • Owner — billing & org settings
  • Admin — keys & integrations
  • Researcher — sessions & library

Personal vs. organization workspaces

Every account has a Personal workspace and can belong to any number of orgs. You work inside one active workspace at a time — it decides where new work lands and whose plan it's billed to.
Personal
Your private space, billed to your own plan. The default until you switch.
An organization
Shared team space; new work is attributed to the org and billed to its owner.
Switching
Use the sidebar account menu. Instant, and the plan badge plus credits switch to that workspace's plan.

Where you start after joining

If you have never chosen a workspace, joining an organization puts you in it, so your work uses the organization’s plan rather than your own credits. If you have already switched workspaces at least once, you stay exactly where you are — joining a second organization never moves you out of the first. Either way the sidebar account menu switches you in a click. Creating an organization does not move you into it.

Create an organization

Any signed-in user can create one — and more than one.
1 · Open Organizations
Settings → Organizations → “New organization.”
2 · Name it
2–160 chars; optional billing email. A URL slug is generated for you.
3 · You're the owner
Invite teammates and manage the team; switch in from the sidebar.

Invite teammates

Owners and admins invite from the organization page — one person at a time by email, or a single link a whole group can join through.
Invite one person
Enter their email and pick Admin / Member / Viewer; a 14-day secure link is emailed (or copy it).
What the invitee does
Sign in with the invited email to join — it must match the invite.
Pending & revoking
Invites stay pending until accepted; revoke any time, links expire at 14 days.

Inviting a group at once

A shareable join link is made once and can be sent to everyone — pasted into Slack, an email, or a calendar invite. You choose the role and how many people may join through it (25 by default), and unlike an emailed invite there is no address to match: anyone who opens the link joins. Owners and admins can copy the link again at any time from the organization page, and raise the limit if it fills up, without sending anyone a new address. Everyone who joins can spend credits billed to the organization, so keep the limit close to the size of the group and switch the link off when the group is in. Turning a link off takes effect immediately — anyone who opens it afterwards is told it no longer works — and the link stays listed as turned off, showing how many people joined before you stopped it. People who already joined stay; only new joins are refused.

New to Cortexa?

Invitees without an account are sent to sign-up first, then land back on the invite automatically — see Getting started.

Roles & permissions

Each member has one role per organization — controlling who manages the team, who can run (and spend credits on) agent work, and who can only read.
RoleManage the orgRun agent workNotes
OwnerFull controlYesTransfer ownership · delete the org · only role that can't leave
AdminInvite, set roles, remove members, edit org name & billing emailYesCan leave · can't delete the org or transfer ownership
MemberNoYesCan leave the org
ViewerNoNo — read-onlyReads shared sessions & files · can't spend credits · can leave

Viewers are read-only

Viewers can open and read shared sessions and files, but can't run the agent or spend credits — ideal for stakeholders who need visibility without consuming the team's plan.

Connections require a separate grant

Organization owners/admins manage private connections. Members and viewers can discover or use a Postgres, BigQuery, Slack, GitHub, or future connection only when an owner/admin explicitly grants their user or role access. Removing the grant takes effect immediately across web, Slack, API, and MCP.

Sharing sessions & files

Work is private by default — even inside an org. Sharing is opt-in, per item.
Private by default
A new session or file is visible only to you, even in an org workspace.
Share to the workspace
Toggle a session/file visible to org members; switch back any time.
“Shared with me”
Sessions teammates shared appear under their own sidebar heading, each labelled with who shared it. It only shows when something has been shared with you.
Owners & admins curate
They can manage others' shared items; members/viewers cannot.
Workspace folders
Library folders are partitioned by the active workspace. Sharing a folder never overrides a private file's access setting.
Public links are separate
A session's Share button can make an internet-facing read-only link unless the session contains private connection evidence.

Team billing

Plans live on a user account, not the org. What you can run, and who pays, depends on the active workspace.
One plan, one payer
Your Personal work and every org you own bill to your account's plan.
Inside an org
Usage is attributed to the org and billed to the org owner's plan — the sidebar badge shows that plan, not your own.
Viewers don't spend
Viewers can't run agent work, so they never consume credits.
Usage visibility
Owners/admins see per-member usage attributed to the org.

Plans & credits

See pricing for credit allowances, and manage your subscription in Settings → Billing.

Managing the team

From the organization page, owners and admins keep the roster current.
Change a role
Between Admin / Member / Viewer. Not the owner's or your own.
Remove a member
Revokes access to shared work immediately.
Leave an org
Admins, members, viewers can leave. Owners transfer or delete first.
Transfer ownership
Only the owner can; the previous owner becomes an admin.
Delete an organization
Owner-only; removes the org + memberships, never member accounts.

On this page

WorkspacesCreate an orgInvite teammatesRolesSharingTeam billingManaging the team
Cortexa.

The agent for research teams. 1.4K+ research tools across scientific and professional fields, with sources attached to the claims they support.

Product

  • Documentation
  • Integrations
  • Tool catalog
  • Security & privacy
  • Pricing

Get started

  • Start research
  • Sign in
  • Developer API
  • MCP server

Support

  • Help center
  • Contact us
  • Terms of Service
  • Privacy Policy

© 2026 Cortexa. All rights reserved.

TermsPrivacy·For research context only · Not medical, legal, or financial advice.