Teams, and what stays private

Everyone gets an organisation of their own, and you can belong to several. The switcher at the top of the nav moves between them; each has its own calendar, campaigns, wins and activity.

What teammates can see

Coordination only, as metadata:

• Calendar: who is posting what topic, where, and when. Coverage at a glance, never a scoreboard.
• Campaigns: time-boxed themes with topics and an optional brief.
• Wins: a short note you chose to share, with reactions.
• Activity: behind the bell at the top right, with a badge when something is unread: published and planned pieces, campaign changes, shared wins, people joining. React with an emoji, and open a row to go straight to the piece, win or campaign it is about.

What they can never see

This is enforced in the data layer, not just hidden in the interface:

• your ideas and drafts in progress
• your coach conversations
• your intention profile
• your Plan, including all engagement

Two people in the same organisation still cannot read each other’s private coach data. The only things that cross the boundary are the coordination items above, and a draft body is never one of them.

Nothing is ranked

No leaderboards, no comparing people. A quiet week shows as coverage information, not as a failing grade.

Single sign-on, over SAML

An admin can point the whole organisation at your own identity provider, under Organisation → Integrations. Everyone whose email domain matches signs in there instead of asking for a magic link, and joins this organisation the first time they do.

It speaks SAML 2.0, which is the protocol Google Workspace, Microsoft Entra, Okta and the rest have in common, so the same setup works whichever one you run.

Trust runs both ways, so setting it up is a swap. The panel shows you the two values your provider wants from us:

• the entity ID, which your provider may label Audience URI or Identifier
• the ACS URL, which it may label Reply URL or Assertion Consumer Service URL

Both are also in our metadata file at /auth/sso/metadata. Most providers will read that file if you hand them the URL, which saves typing either field.

In Google Workspace

Admin console → Apps → Web and mobile apps → Add app → Add custom SAML app. Google shows you an SSO URL, an Entity ID and a certificate to download: those are the three values to bring back here. Then map the primary email address to the name ID, and turn the app on for the people who should use it.

In Microsoft Entra

Entra admin center → Enterprise applications → New application → Create your own application, and pick the non-gallery option. Open Single sign-on → SAML, put our entity ID in Identifier and our ACS URL in Reply URL, then take back the Login URL, the Microsoft Entra Identifier and the Certificate (Base64) download. Assign the users or groups who should have it.

Back in Integrations

Paste in the three values: entity ID, SSO URL, and the certificate whole, including its BEGIN and END lines. Add the email domains you own, comma separated, and save.

A domain has to be one an admin of this organisation has an address at, so no organisation can claim a domain that isn’t its own.

The certificate is public rather than secret, but it is the entire trust anchor: it is what decides whether a login really came from your provider, which is why only an admin can change it. When your provider rotates it, paste the new one in here. Until you do, sign-ins stop with a message about the signature.

Require SSO for these domains switches magic-link sign-in off for everyone at those domains. Test a real login before you turn it on. There is a break-glass list of addresses that may always use a magic link, so a mistyped SSO URL cannot lock an organisation out of its own account, but it is configured on the server rather than in this panel, so ask us to put an address on it first.

Leaving, and deleting

Leaving an organisation is under Organisation → Danger zone. You keep everything of your own; you lose access to that organisation’s campaigns, calendar and activity. The last admin can’t leave, promote someone else first, or the organisation would be left with nobody able to administer it.

An admin can also delete the organisation outright, from the same place. That is final in the strongest sense: every campaign, every shared win, the whole activity history, the Slack connection and the SSO configuration are deleted, for everyone, and there is no backup to restore from. You confirm by typing the organisation name, because no button alone should be able to do that.

One thing deletion does not touch, and cannot: your own pieces, ideas and channels. Those were never organisation property, they belong to whoever wrote them, and they stay after the organisation is gone. The same is true for everyone else’s.