Organization Admin Guide
The current Organization Admin workspace: people, culture, communication, engagement, settings and billing — with the privacy boundary made explicit.
Open Organization AdminGenerative AI is experimental.
1. Organization Admin workspace
The admin navigation is organized around the real operating journey rather than separate technical modules.
Dashboard — organization overview and operational signals.
People — employees, departments and teams in one people structure.
Culture — organization values and culture content.
Announcements — organization communication.
Challenges, Leaderboards, Recognition and Rewards — engagement tools.
Products — internal products/services for employees.
Settings and Billing — administration and commercial management.
2. People, invitations and seat capacity
Manage employees and the organization structure from People.
Invite people only when the organization has the required seat capacity.
Seat and invitation flows are enforced server-side; do not treat a sent invitation as proof that capacity exists.
Use Billing to understand active paid capacity and commercial status.
The platform has been hardened around seat-allocation and invitation integrity. If capacity and membership disagree, treat that as a support issue rather than manually working around it.
3. The privacy boundary
Organization Admin is not a surveillance console for individual SelfOS behavior.
Do not expect access to employees’ private habits, goals, mood entries, journals or AI conversations merely because you are an organization admin.
Use organization-level engagement and program data for management decisions.
Coach permissions are a separate relationship controlled by the client/coach access model.
Health and other sensitive data require the appropriate consent path.
4. Culture and communication
Maintain Culture content that explains the organization context inside SelfOS.
Use Announcements for program updates, launches and internal communication.
Keep communications relevant to the SelfOS program instead of duplicating every internal communication channel.
Draft announcements are surfaced in the admin navigation so unfinished communication is visible to admins.
5. Challenges, leaderboards, recognition and rewards
Create challenges with clear rules and a real participation purpose.
Use leaderboards deliberately; competition is not appropriate for every wellbeing or development objective.
Recognition should reward observable contributions or achievements, not expose private personal-development data.
Use Rewards and Products as distinct tools: incentives/redemptions versus internal offerings.
6. Settings, branding and enterprise controls
Organization profile, preferences and administrative configuration live under Settings.
Branding availability depends on plan.
SSO is an Enterprise capability in the current commercial catalog.
Enterprise is a managed/contact-sales plan rather than a zero-price self-serve plan.
7. Billing
Organization billing is seat-based.
Use the Billing page for the organization’s current payment/subscription information.
Commercial terms, active plans and feature availability are sourced from the canonical pricing catalog.
Do not rely on old screenshots or hardcoded plan descriptions when making purchasing decisions.