Overview
Organization-level settings live on the Organization page (under Administration in the sidebar) and apply to every member. Only Admins see this page. Settings fall into five groups: organization identity, membership via email domains, privacy controls, user consent documents, and external integrations. Your organization’s AI context - description, website, and the documents that power track contextualization - lives separately under Context & Documents.Setting the organization identity
The Organization Name at the top of the page is what members see across the app and in invitations. Further down, the SAML/OIDC section shows your single sign-on status - SSO is enabled and disabled by JAM support, so use its Contact us link rather than hunting for a toggle (see Logging In to JAM for what SSO changes for your users).Adding your logos
The Branding section on the Organization tab lets you co-brand JAM with two logos. Paste a link to each image and Save; a preview under each field shows how it will look.- Square logo - appears in the navigation bar, where it replaces members’ profile pictures, and in small spots like onboarding and the help chat. Use a square (1:1) image, otherwise it looks stretched.
- Full logo - appears in white on the certificates your learners earn. Use a wide image with a transparent background.
Letting people join by email domain
Want colleagues to join without individual invitations? Set your Primary Domain (and any Additional Domains), then enable Allow users with matching email domains to automatically join. Anyone signing up with a matching address joins your organization directly - no invite required, though each joiner still consumes a seat.Controlling privacy
Two org-wide switches narrow what Coaches and Admins can access (see Understanding Who Sees Learner Data):- Audio privacy - call recordings stay accessible only to the learner who played the session; Coaches and Admins still see results and transcripts.
- Enhanced privacy - hides all individual performance data from Coaches and Admins, leaving only aggregated team data. JAM warns against this one: it removes the basis for individual coaching. The better pattern is controlling visibility through team membership.
Requiring user consent
The User consent section lets you upload a PDF policy (legal, data-processing, or AI-use) that every user must accept before using JAM - one active document at a time, up to 5 MB. The version history table tracks adoption per published version, and an audit CSV records every accept and revoke event for compliance.Connecting an external reporting system
The Integrations section connects your learning management system. Use Set up external reporting to sync completed session data to an external Learning Record Store (LRS), so your team’s progress shows up in whatever system you already track learning in.What happens next
- Name and logo changes show up across the app for all members immediately.
- With domain auto-join on, watch your seat usage - joining is self-service from then on.
- A newly-required consent document interrupts every member’s next visit until they accept.
Troubleshooting
A member can't change their own name or email
A member can't change their own name or email
Accounts managed through SSO lock those fields in Personal
Settings - they’re owned by
your identity provider, not JAM.
Related articles
- Understanding Billing and Plan Limits - the seat budget auto-join draws from
- Creating and Managing User Accounts - invitation-based membership
- Managing Your Personal Settings - the per-user counterpart to these settings
- Logging In to JAM - how SSO changes sign-in for your members
Last updated: November 2026

