Team
Your team is the people who can open the academy's admin: everyone who writes, reviews, publishes, or reports on courses. Learners are not on it — they sign in from the academy itself and never need an invitation. The team lives on Admin → Team.
Inviting someone
Owners and admins see an Invite a teammate form at the top of the page: an email address and a role.
- The seat exists at once. The person is on the team the moment you press Send invitation, and the list shows them as Invited, hasn't signed in yet until they do.
- They get one email, from your academy's name, with a link to its sign-in page — their address already filled in. Sign-in is the same magic link learners use: no password to set, nothing to accept. Once in, they land in the admin. The team always signs in with their email: sign-in from your product is for learners, and refuses anyone with a seat.
- Didn't get it? Send the invitation again sits in their row's Actions menu until they've signed in. If the email can't be sent, the page shows the sign-in link to pass on yourself.
- Invitation emails are limited: 20 a day per academy, and 3 a day to any one address. Past that, the person is still added and the page shows the link to pass on instead.
- Already on the team? The form says so and leaves their role alone; change it from the list instead.
Someone who was already a learner keeps their learning record when they join the team — the seat is added to the same person.
Roles
| Role | Can |
|---|---|
| Owner | Everything, including making and removing owners. |
| Admin | Everything an owner can, except making or removing owners. |
| Author | Everything except the team, the academy's name and domain, its plan, selling (Stripe and certificate prices), sign-in from your product, and setting up integrations. |
Every role can author and publish courses, curate the home, read every insight, manage learners and accounts, change the brand, and download every export. The roles only differ on the academy itself — who's on the team, what it's called, the custom domain, the plan, selling certificates, sign-in from your product, and the integrations on Admin → Settings → Integrations: owners and admins connect the courses repo, the docs source, embedded labs' hosts and the webhook, generate the API token, and see their secrets; every role can still press Sync now, send a test event and resend a delivery, and sees whether the API token is set and which host the webhook sends to (the whole endpoint stays with owners and admins: for a catch hook, the address works like a password).
Authors see the team list but not the invite form or anyone's actions.
Changing roles and removing people
Each row's Actions menu holds what you may do to that person: Make owner / admin / author, Send the invitation again, and Remove from the team. Removing asks first and says what happens: they lose access to the admin right away, and their learning record stays. You can invite them again any time.
- Only an owner makes or removes owners. An admin's menu never offers it, and an admin can't change an owner's seat.
- There's always an owner. The academy's only owner can't be removed, demoted, or leave — make someone else an owner first. This holds even if two owners try to demote each other at the same moment.
- Leaving. Anyone can leave from their own row's menu (Leave the team), except the only owner.
The academy's name
Owners and admins rename the academy at the top of Admin → Settings. The name shows in the header when there's no logo, in browser tabs, on certificates, and as the sender of the academy's emails — invitations included. Invisible and control characters are removed, and the name is kept under 80 characters.