Skip to main content

Teams, projects & roles

ScribX organizes everyone and everything into a simple hierarchy. Understanding it explains where a meeting lands and who can open it.

The hierarchy

  • Organization — your company workspace. Billing, SSO and org-wide policies live here.
  • Team / project — a space inside the org where meetings are captured and grouped. You can belong to several.
  • Recording — belongs to one team, and is owned by the person who captured it.

When you capture a meeting, you pick which team it lands in — that choice decides who can find it.

Your teams

  • You start with a private team — your personal space (e.g. "My Personal Space"). Meetings you capture land here by default, visible only to you until you share them.
  • Create more teams for groups, clients or workstreams — see below.
  • Switch teams any time from the team switcher at the top-left (next to the logo). The team you're in determines where new captures land and which meetings you see.

Create a team

Spin up a team for a group, client or workstream. You become its admin, and the team owns its own recordings, members and ScribX defaults.

The Create a team screen — name, colour and default ScribX settings12
  1. 1Name your team (e.g. Marketing)
  2. 2Pick a colour for the team badge
Create a team — name it, pick a colour, and set the defaults (you can change them later).
  1. Open the team switcher (top-left, next to the logo) and choose Create team — or go to + New team under your teams.
  2. Give it a name and a colour.
  3. Optionally set the ScribX defaults (recording format, transcription, summary, language) — these are editable later in team settings.
  4. Click Create team. You're its first admin; now invite people.

Roles

RoleCan do
MemberCapture, view and share their own meetings; see team meetings shared with them
AdminAll of the above, plus manage members, team settings and billing

Organization-level admins additionally manage SSO and org-wide controls. Enterprise

Invite people

  1. Open Settings → Members in the web app.
  2. Add people by email and pick their role.
  3. They receive an invitation and join the team.

Where meetings live

  • A meeting is visible to the owner and anyone it's shared with.
  • Setting general access to the team makes it visible to all team members.
  • Moving a meeting to another team changes who can find it.
tip

Use separate teams for separate audiences — e.g. an internal team and a client-facing one — so the right people see the right meetings by default.

What's next?