Skip to content

Team Members and Roles

As your academy grows, you’ll likely bring in help — a co-instructor, an operations manager, or an assistant to handle learner support. Klimb lets you invite team members to your academy and assign each a role that controls what they can see and do. This keeps collaboration smooth while protecting sensitive areas like billing and payouts.

Inviting a teammate

  1. Go to Settings → Team.
  2. Choose Invite member.
  3. Enter their email address and pick a role.
  4. Send. They’ll receive an email to set up access to your academy.

Teammates join your tenant with the role you assign — they only have access to your academy, never any other creator’s. Their access is independent of any learner account they may also hold.

The roles

Klimb offers three roles, from most to least access:

  • Owner — full control of the academy, including billing, payouts, team management, and the ability to delete the academy. The Owner is typically you, the creator who set up the academy. There’s one ultimate Owner, and ownership is the highest level of trust.
  • Admin — can manage courses, learners, coupons, and analytics, and generally run the academy day to day. Admins are your trusted operators. Depending on your settings, Admins may have limited or no access to the most sensitive billing actions.
  • Instructor — focused on content. Instructors can create and edit courses and lessons and view engagement, but don’t manage billing, payouts, or team membership. Perfect for co-creators who teach but don’t run the business.

Choosing the right role

Grant the least access each person needs to do their job:

  • A co-teacher building content → Instructor.
  • An operations or support manager handling learners, coupons, and reports → Admin.
  • A business partner who needs full control including finances → Owner-level trust (assign carefully).

You can change a teammate’s role anytime from Settings → Team as responsibilities shift.

Managing your team

From the Team screen you can:

  • See everyone with access and their current role.
  • Change a role as someone’s responsibilities grow or narrow.
  • Remove a member when they leave — their access ends immediately, while the courses and content they created remain part of your academy.

Removing a teammate doesn’t delete their work; it only revokes their access.

Security considerations

Team access is powerful, so treat it with care:

  • Limit Owner and Admin roles to people you fully trust — they can affect money and data.
  • Encourage 2FA for every teammate; their account security is your academy’s security. See Account and security.
  • Review your team periodically and remove anyone who no longer needs access.
  • Offboard promptly when someone leaves a project.

Accountability

Sensitive actions in your academy are recorded, so you can see who did what — granting access, issuing refunds, or changing prices. This audit trail helps you collaborate confidently while keeping accountability clear.

With roles, you can scale your team without handing everyone the keys to everything. Match each person to the smallest role that lets them succeed, and your academy stays both collaborative and secure.