Setting up your organisation

The admin console is at yourorg.rukialabs.com/admin. Administrators and managers can open it; instructors cannot.

This page is the map and the running order. Each step links to the guide that covers it properly.

The order to do things in

Setting up out of order mostly works, but three dependencies will bite you.

1. Check your organisation’s details and branding — name, logo, colours, support email. Do it first because it is what everybody sees from their first sign-in.
2. Set up grading scales — you start with four ready to use. Decide which is your default now. A course graded before you have chosen produces a percentage with no grade beside it.
3. Invite your staff — instructors, managers, the other administrators. Before learners, so there is somebody to teach them.
4. Create your courses — or have your instructors create them.
5. Create cohorts and attach courses to them — this is the step people skip, and it is the one that matters most. A cohort with no courses attached cannot enrol anybody.
6. Assign teaching staff to each offering — who teaches and who manages each cohort-and-course run.
7. Invite and enrol your learners.
8. Schedule classes, if you teach live.

The sidebar

Entry	What it is for
My Dashboard	Organisation-wide activity: top courses, top pathways, most engaged learners
Manage Pathways	Multi-course tracks and who is on them
Manage Cohorts	Cohorts, the courses they run, and enrolment
Manage Courses	Every course in the organisation, and authoring
More Operations → Grading Bands	Grade scales and their bands
All Classes	Every scheduled class in the organisation
All Submissions	Every submission, across every course
All Announcements	Everything sent to anybody
Manage Users	People, invitations, roles and account states
Org Management → Overall Settings	Organisation profile, branding, links, domain, email
My Profile	Your own profile

Managers see most of this. Org Management is administrators only — a manager runs programmes, an administrator decides what the organisation is.

The three things worth understanding early

Courses, cohorts and offerings

• A course is teaching material. Written once.
• A cohort is a group of people with dates.
• An offering is one cohort running one course.

Teaching staff, class schedules and every grade belong to the offering. The same course run by three cohorts is three offerings with three sets of marks.

This is the model the whole product is built on, and most confusion about “where are my learners’ grades?” traces back to it.

Roles are per organisation

Somebody’s role is their role here. It does not follow them to another organisation on the platform, and suspending them here does not touch their access anywhere else.

Four roles exist by default: Admin, Manager, Instructor and Student. Every account is a Student until something else is granted. See People and roles.

Nothing crosses organisations

Courses, users, cohorts, grades and uploaded files belong to one organisation and are invisible from any other, including to someone who is a member of both. This is enforced by the platform rather than by careful configuration, so there is no setting here you can get wrong.

What is on your dashboard

Top performing courses and top performing pathways — by completion and by mark.

Most engaged learners — by activity.

Read the bottom of these lists as well as the top. A course that nobody finishes is usually a course with a structural problem in it, and it shows up here before anybody reports it.

Getting help

Set a support email under Org Management → Overall Settings → General. It is what the platform tells your members to write to when they are locked out, and it signs your transactional mail. Without it, a suspended member’s sign-in screen tells them to contact an administrator without saying how.