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, plus the progress table below it, which has a section of its own.
• 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.

The one table where numbers sit side by side

Under the calendar grid, each team gets a progress table: per person, the pace they set themselves and how far this week has come, posted and ready. It is the one place in the app that puts one person’s numbers next to another’s, and it is there because somebody planning a campaign cannot coordinate against a blank week.

It is not a ranking. Nobody is ordered, scored or marked red, there is no leaderboard anywhere in the app, and a quiet week reads as coverage information rather than a failing grade. You see the teams you are in; an admin sees all of them.

An admin can switch it off for the whole organisation under Organisation → Users, and then nobody sees it, admins included. It is on until somebody turns it off.

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.

One exception, on purpose: somebody who already has an account here, from a magic link or from another organisation, is not pulled in by their first SSO login. Add them under Organisation → Invite by email first, and SSO signs them in as normal from then on. A matching domain shows that your organisation is at that domain. It does not show that one particular address is yours to hand over, so taking over an account that already exists needs an admin to say so.

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.

Taking the organisation’s data out

An admin can download everything the organisation holds, from Organisation → Data export: one JSON file, straight to the browser, no waiting for an email. People with their roles and teams, campaigns, shared wins, the activity history, connected channels, and the billing, SSO and Slack settings with their credentials left out. Pieces travel only once they are ready or posted.

What does not travel is exactly the list teammates can never see either: drafts, ideas, coach conversations, goals and check-ins, including the exporting admin’s own. The file names its own omissions, so nobody reading it later has to guess what is missing.

Leaving, and deleting

Leaving an organisation is under Organisation → Danger zone. If you are not an admin, Organisation settings are not in your menu at all, so the way in is My settings → Danger zone, which links there. 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.

Deleting your account

My settings → Danger zone deletes the account itself, and it is a different thing from deleting an organisation. It takes your ideas, drafts, posted pieces and coach conversations, and any organisation nobody else is in. An organisation with other people in it stays, and so does their work. You confirm by typing your email address; there is no backup and nothing comes back.

Two things stop it, and each says so. If you are the only admin of an organisation somebody else is in, make another person an admin first: an organisation cannot be left with nobody able to run it. And if coaching sessions of yours have not reached an invoice yet, the deletion waits for the next hourly run, which is minutes.

What stays is the record of what was done. An organisation’s history says a piece was published or a campaign was changed, with your name no longer on it, because that history is what answers questions for the people still there.