Build courses together with Team members

Decide who needs which access

Start with the work each person will do. Someone editing lessons needs different access from someone taking the course. Account roles keep those responsibilities separate:

• Owner: manages the account, billing and team membership, as well as its content.
• Creator: creates, edits and publishes account content, subject to the plan.
• Viewer: previews content and inspects the account’s available reporting without editing.
• Learner access: takes a course under its audience and joining rules. This is separate from a collaborator invitation.

Send an invitation

An authorised owner opens Account, finds Team Members, enters the address in Invite someone by email and chooses Creator or Viewer. Send Invite creates the invitation. The recipient accepts it using the invited email and their own sign-in.

Check Pending Invites if the person has not joined. Use the available resend or revoke action when appropriate. If the roster failed to load, retry the read rather than assuming there are no members. Inviting collaborators requires the Team plan.

Agree how you’ll work on the course

Shared access is useful, but it doesn’t decide who is doing what. A simple arrangement helps: one person drafts a lesson, another reviews the examples, and someone checks the finished course before publishing.

Choose how you will hand work over and where reviewers should leave their notes. Finish one review round before someone else starts rewriting the same lesson.

Use a review handover you can actually follow

For a volunteer induction course, give the subject expert the first lesson draft and ask a second person to review it as a new volunteer. The reviewer should list where they needed missing context, which example felt ambiguous and whether the final action was clear. Those observations are easier to act on than “make it more engaging”.

Agree who is editing which lesson before you begin. Agree a handover in your usual team chat or document. Tiny Courses shares the course between collaborators, but does not provide live co-editing, review comments or approval stages. A Viewer can be useful for a read-only review without giving that person content-editing permissions.

Use Preview for the saved draft. Choose a person who is responsible for the final publication check, then use Publish Course when it is ready. A saved edit is not automatically a release to learners.

Keep the first collaboration small

Choose one course and invite the people who need to work on it. Give each person a clear job and review the course together before sharing it with learners. You can build on that arrangement as more people get involved.

Keep client ownership and learner access separate

If a client needs their own account and subscription, Set Up Client is a different workflow from adding a teammate to yours. The client owns that new account, and the inviting creator joins it under their own profile after the client completes setup.

If someone only needs to take a course, use its published link and sharing settings. A team invitation gives access to the account’s work. It is not the right shortcut for a learner who needs one lesson.

When a collaboration ends, the owner can remove the person’s membership. Account content stays with the account. Check the correct account in the switcher first, and review any separately granted learner access if that needs changing too.