Admins own the structure a review runs inside: the people, the teams, the framework, the workspace.
You don't own anything written inside a review, including your own reports' — reading that comes from managing someone. You also still have a growth record of your own. See As an employee and As a manager.
Setting up the workspace
Organization → Getting started tracks three steps. They're all your own work, so the list finishes without waiting on anyone.
1. Create your teams. Organization → Teams. A team is a name, a manager, its members, and optionally a parent team. Naming the manager is what gives everyone you add a reporting line, which is why this comes before inviting people. Nobody is notified — this is bookkeeping, not an announcement. See Teams.
2. Invite your people. Organization → People, by email or CSV (with optional team and reports_to columns). Pick the team as you invite and the reporting line arrives with them. Everyone arrives as an employee; you can't pre-grant manager or admin access from an invite, so come back to the table afterwards and toggle it on. Re-importing a CSV skips people who already exist, so an updated list is safe to send again. See People.
3. Set who reports to whom. Anyone who didn't arrive through a team, or who reports to someone other than their team's manager, gets a manager set directly on their record — and that setting wins over the team's. Reviews run along reporting lines, not team membership.
Two more things before a review can open
Neither is on the Getting started list, and a review can't start without them.
Decide what people are assessed against. Publish a framework from Organization → Framework: a built-in starter, a markdown document you already keep, a short guided draft, or an empty grid. Everything lands as a draft nobody but admins can see, and nothing is assessable until you publish. Or skip it and have managers write personal expectations one person at a time. See The framework.
Hand off the level placement. Managers place their own reports on a track and level. You can't do this for them, on purpose: whoever assesses against a level should be the one who chose it.
Organization → People has an Assessed against column — visible to you, not editable — and a count above the table that filters down to everyone still unplaced. That count is your handoff checklist, and it has to reach zero before those people can be reviewed.
Ongoing admin work
Most weeks there's nothing to do. What comes up:
Joiners and movers. Invite, place on a team, confirm the reporting line. Changing someone's team or manager carries their whole record with them — closed reviews, focus areas, evidence — to whoever manages them next. Nothing is reset by a reporting change.
Leavers. Deactivating is reversible and deletes nothing. Their record, evidence and closed reviews are kept as they were. They can no longer sign in, and their record is not shown to anyone, their manager included, until they are reactivated. To undo it, use Reactivate in the Deactivated list at the foot of the People page.
Framework revisions. A published version can't be edited in place — that's what makes old reviews trustworthy. New version duplicates it into a fresh draft you publish when it's ready. Publishing archives the superseded version automatically but never moves anyone onto the new one; a manager has to place them there. A version already used in a review can be archived, never deleted.
Seats and billing. €9 per user per month excluding VAT, five-user minimum, 30-day trial with no card and no feature held back. Payment details never touch Growth Record — Manage billing hands off to Stripe's portal. If you cancel, nothing is deleted and everyone keeps access to the end of the paid period; after that the workspace goes read-only, drafts intact, resumable any time. See Settings & billing.
What admins can't read, and why
You can't open a review, read an assessment, or see what's in a plan. Not for anyone, including people who report to you — for them you'd read it as their manager, not as an admin.
This is a deliberate limit, not a missing feature. The person being assessed is the least powerful party in a review, so admin access stops at the structure and doesn't reach into what two people wrote about each other. What you can see is who's assigned to what, and where a review stands as a matter of fact. Never its contents. See Roles & perspectives.
In practice: when someone asks you to check how a review is going, the honest answer is that you can't, and the right person is their manager.
Exporting data
- People exports as CSV, for reconciling against payroll or anything else outside the product.
- Review content doesn't bulk-export, by the same logic as above. Each person exports their own full record, as Markdown, from My Growth.
- Deleting the organization cancels the subscription at once, signs everyone out, and erases everything 30 days later. Export what you need first — and we can send a full organization export on request.