Team setup in most platforms is an afterthought — a 'users' page where you toggle checkboxes and pray. In Ukkera it's a deliberate sequence: role first, course scope second, capabilities third. This walkthrough takes about fifteen minutes for a typical small team and saves you the retrofit later.
Step 1 — Invite with the right role from day one #
Under Academy → Team, invite each member by email and assign their role at the invitation — admin, instructor, teaching assistant or viewer. Starting people at the correct level beats downgrading later: nobody feels demoted, and nobody accumulates access they never needed. New instructors land in a sandbox course where they learn the platform before touching anything live.
Step 2 — Scope each instructor to their courses #
- Assign course ownership: instructor sees, edits and teaches only what's theirs
- Enable co-teaching where two instructors share one course with split sections
- Give TAs support access: Q&A, quiz monitoring, progress views — no editing
- Set viewer access for auditors and quality reviewers as needed
Step 3 — Configure the collaboration defaults #
Three settings determine how the team feels day-to-day: content review mode (instructor edits publish directly, or route through owner approval — start with approval, relax it as trust builds), student data visibility (instructors see their students fully; cross-course analytics stay with owners), and notification routing (who hears about new questions, quiz failures, refund requests). Set these once, deliberately, and the academy develops the operating rhythm of an organization rather than the vibes of a group chat.
Step 4 — The quarterly hygiene pass #
Once a term, audit the team page: remove departed members (access ends instantly), review role creep (that TA who's been 'temporarily' editing content for three months), and confirm each instructor's course scope still matches reality. Fifteen minutes per quarter is the entire maintenance cost of a permission system that protects everything you've built.