A team member is someone who works in the admin area with you. That is a different thing from a member, who signs in to the member area as your customer. This article is about the first group.
Inviting someone
- Open Settings, then Team & Roles.
- Press Add.
- Enter their name and email address.
- Pick the role they should have.
- Save.
Your plan sets how many people can work in the admin area, and your own account takes one of those places. When the limit is reached, saving shows an upgrade prompt instead of creating the account. Upgrade your plan or remove someone who no longer needs access.
They get an email with a link to set their own password. Until they use it, they appear in the list without having signed in.
Invite people with the address they will actually use. The address is how they sign in, and changing it later means they sign in somewhere new.
What a role decides
A role is a set of permissions. It answers two questions for every area of the platform: can this person see it, and can they change it.
That means you can hand someone the courses area without handing them your revenue figures, or let a moderator work in the community without letting them touch billing.
Open the Roles tab next to Team to see the roles you have and what each one allows.
Building your own role
The roles you start with cover the common cases. When they do not fit, build one:
- Open the Roles tab.
- Press the button to create a role and give it a name people will recognise, like "Course editor" or "Support".
- Work down the list of areas and grant what that job needs.
- Save, then assign the role to the people who do that job.
Grant the smallest set of permissions that lets someone do their work. It is easier to add a permission when a colleague asks for it than to discover later that everyone could see everything.
Whoever can manage team members can also change roles, including their own. Treat that permission as the keys to the building.
Changing or removing access
Use the pencil beside a person to change their role. The change takes effect on their next page load, not at their next sign-in.
Use the bin to remove them. Their access ends immediately. Content they created stays where it is, so removing an editor does not remove the lessons they wrote.
When someone leaves, remove them the same day. It takes a moment, and the audit log records who did it.
Seeing who did what
Every meaningful change in the admin area is recorded with a name and a timestamp. When you need to know who published something or changed a price, the audit log has the answer.