Skip to main content

Organization admin console Enterprise

Plan & role

The org console is for organization admins. Most settings here are Enterprise. Teams inherit org policy and can tighten — but not loosen — it.

Screenshot placeholder
📷 To capture: the organization admin console (target: /img/handbook/security/org-settings.png).

The organization is the top of the hierarchy: billing, policy and org-wide defaults live here, and every team inherits them. Open it from Organization in the web app.

What an org admin controls​

The console is grouped into four sections.

Account

  • General — org name, logo and ID; who can create teams; the email domains your org claims.
  • Plan & Credits — the plan, this cycle's allowance and any purchased credits. See Plans & billing.
  • Usage — meetings captured, credits spent and storage used over time.

People

  • Members — everyone in the org and their org-level role.
  • Teams — every team in the org.

Security

  • Privacy — how long recordings are kept, org-wide. Teams can shorten the window, not extend it. See Data handling & retention.
  • Voiceprints — whether voiceprints are enabled, and whether members may share them org-wide.

Integrations

  • Transcription — the org-wide engine, and a bring-your-own STT key if you have one.
  • Storage — ScribX storage, or your own bucket.
  • Meeting Platforms — org-wide Zoom, Google Meet and Microsoft Teams connections. See Integrations.
  • Automations — a When / If / Then rule engine for things like tagging a meeting or posting its summary onward. Not active yet; the panel shows what's coming.

How inheritance works​

Org sets policy → teams inherit and set their own defaults → members override where allowed. For example, the org picks the transcription engine and retention window; a team then sets its default recording format and summary; a member can override their reading language.

SSO & access controls​

Plan

SSO and org-wide controls are available on the Enterprise plan. See Plans & billing.

Enterprise organizations manage how people sign in and what they can do from one place — your identity provider and an org-wide policy.

Single sign-on (SAML)​

Connect ScribX to your identity provider (Okta, Entra ID, Google Workspace, etc.) so your team signs in with your existing credentials.

  1. An org admin opens Organization → Security.
  2. Exchange the SAML metadata between ScribX and your IdP.
  3. Optionally enforce SSO so members must sign in through your provider.

See Sign in & accounts for the member experience.

Roles & access​

  • Assign Member or Admin roles across teams.
  • Control guest access — whether members can share to external emails or create public links.
  • Set org-wide defaults for recording, summary and language that teams inherit.

Audit history​

Org admins can review an audit log of significant actions — sign-ins, sharing changes, deletions. Audit logs are retained for 7 years (see Data handling & retention).

What's next?​