Administering your organization

Under Roles & Structure, open the template gallery — around eighteen ready-made starting points grouped into families: Sports (pro, college, youth, esports), Corporate (sales org, leadership development, employee wellbeing / EAP), Public safety (first responders, military), Healthcare, Education (K-12, higher-ed), Arts (performing arts), Franchise (studio, fitness), and Practice & mission (coaching practice, faith / nonprofit, government). Each one seeds a role stack, starter groups, and the terminology to match — a pro club talks about athletes and coaches; a fire service talks about a chief, sergeants, and responders. If none fits, choose Custom / start blank and build your own from the underlying primitives.

A template picks sensible default nouns, but the terminology editor lets you rename them so the product reads in your words. You set what the org calls the organization, the person in overall charge (Overseer), a Member, the Clinician, the Admin, and a Unit / group. The same underlying model then reads as “AD / coach / student-athlete” for a college program or “chief / sergeant / officer” for a department — the roles and rules don’t change, only the labels.

For a multi-location org, add site and region nodes to the structure and hang groups under them. A Subtree role scope then lets a regional or site lead see their own node and everything under it — but nothing in a sibling region. You can also node-scope any person’s assignment to limit their sight to a single site or group, so a local admin only ever sees their own location.

One member can hold more than one role at once — someone who instructs, sells, and also trains as a performer holds all three. Effective access is the union of what those roles grant. Groups work the same way: they overlap and nest, and a member can belong to any number of them. You don’t have to force people into a single box.

On Members, invite one person by email, or bulk-import a CSV. Each CSV row carries a name, email, phone, one or more roles, and one or more groups — groups named in the file are created on the fly. When a person accepts, any intake you staged for them is applied automatically. You can also assign or change roles and groups on a member after they’ve joined.

Team includes up to 25 Performer seats and 2 Leader seats. The cap is enforced — the 26th Performer add is blocked until you free a seat or arrange more with your Peak Mind contact. Engineer seats aren’t bundled; add them à la carte at $149/mo each.

Turning on Individual full requires a legal acknowledgment: your organization is responsible for its own legal and consent basis for that depth of visibility — Peak Mind provides the mechanism, not the consent. You can set optional per-group overrides where a specific group needs a different ceiling. A member-transparency toggle shows members exactly what the org can see about them.

Team is a firewalled, tiered read of the roster that honors the ceiling you set. At Aggregate it shows de-identified team numbers with a minimum group size so no single person can be re-identified; as the ceiling allows, it opens up through roster status to per-person readiness. It never touches clinical records at any level.

Under Branding, set your logo, brand and accent color, and label overrides — rename Performer, Leader, and Engineer, rename the coach, and set your own welcome text. These apply to both the portal and your members’ mobile app, so the product reads as yours end to end.

Billing is self-serve through Stripe: one org customer, individual members don’t pay. Billing & seats shows a seat meter and a Billing Portal button to manage your card and download invoices. Seat-count and plan changes go through your Peak Mind contact.

Claim an email domain under Domains & SCIM — prove ownership with a DNS TXT record — and new signups on that domain auto-join your org at a default role. For directory-driven provisioning, mint a SCIM v2 token and point your IdP at it to create and deactivate members automatically.

SCIM provisioning is available now. Single sign-on for login (SAML / OIDC) is on the roadmap — SCIM handles provisioning today; SSO login is not yet part of Team.

Every admin action is written to an org audit trail. The Audit & Access surface also gives you an access-review view that flags who currently holds elevated access, so you can confirm the org’s reach matches its intent.