Setting up your organisation
Your organisation is the boundary around everything: its people, its courses and its data. Nothing crosses between organisations.
Your addressβ
Your organisation is reachable at its own subdomain β yourorg.rukialabs.com β
and the three consoles sit under it:
| Path | Console |
|---|---|
/ | Learner experience |
/instructor | Authoring and grading |
/admin | Administration |
/docs | This documentation, in your organisation's colours |
Organisations on a paid plan can use a domain of their own instead, such as
learn.yourcompany.com. That is a DNS change on your side and a short
configuration on ours β contact support to start it.
Peopleβ
Everyone in your organisation is a member, and membership is what grants access. Someone with no membership has no access, regardless of having an account or knowing the address.
Invite people by email, individually or by CSV. An invitation creates the account and the membership together.
Cohortsβ
A cohort is a group of learners who move through courses together β an intake, a class, a department.
Courses are attached to cohorts rather than to individuals. This is the part worth getting right early: enrolling a hundred people one at a time and enrolling one cohort of a hundred produce the same result today, but only one of them is still manageable when the intake changes.
Someone can belong to more than one cohort, and sees the courses of all of them.
Rolesβ
| Role | Can |
|---|---|
| Learner | Take courses they are enrolled in |
| Instructor | Author courses, grade submissions |
| Administrator | Everything above, plus people, cohorts and settings |
Roles are per organisation. Being an administrator of one organisation grants nothing in another.