A CRM for a learningcommunity in Discord.

A course or a school is the same units, roles and terms. The panel keeps the roster by groups, stores materials, lays lessons out in slots and collects work with grades.
A study week: notes in the materials, a lesson on schedule, submitted work and a reminder.

Sound familiar?An ordinary cohort without a panel.

Three things that drown a course in organizational noise.

“Only the mentor remembers who is in which cohort”

Cohorts and roles live in the structure, and a student card keeps the terms and the history.

“Materials are scattered across pins and direct messages”

Materials live in the panel, and search looks for words inside the text, not only in the title.

“Who submitted the work and who did not — we count by hand”

Work arrives as reports, the review awards points, and everything is visible in one list.

Why it fitsa learning community.

Three pillars of a course that usually live in a chat and a spreadsheet.
Cohorts

A roster by groups, not by memory

The cohort, the group and the mentor role are described once. A student card keeps the term and the history, and the Discord role is granted with enrollment and removed at graduation.

You can see who is in which cohort and since when.

Materials

Notes that can be found

Lectures, rules and notes live in the panel, and search looks for words inside the documents. The right to edit is granted separately, so a random person will not rewrite a lecture.

A student finds what they need without asking the mentor.

Assignments

Work with a grade and a reminder

A student submits the work, a mentor accepts it and awards points. The decision lands in the author’s notifications, and an automation reminds those who have not submitted, as many days before the deadline as you set.

Backlogs are visible early, not at the end of the course.

Three situationsin a learning community.

  1. Materials spread across chats

    A document lives in the panel and belongs to the server, and the right clause is found by a phrase from the text.

  2. Classes collided

    A taken slot closes its neighbours, so two groups never land on the same hour.

  3. It is unclear who is working

    Points from accepted reports and the log give numbers, and a filed absence explains who warned in advance.

Questionsfrom learning communities.

Can faction and reprimand be renamed?

Yes. In Terms the labels change to fit you — cohort, tutor, remark. Data and permissions are untouched.

Who sees the documents?

Those with access to the section: visibility is set by position, and creation and deletion rights by the action matrix.

Which time zone does the schedule use?

Moscow time (UTC+3) — the same for every member, wherever they are.

Can several cohorts run at once?

Yes: every cohort is its own unit with its own mentors, permissions and notification channel.

Do students see each other’s grades?

Not unless you opened the section to them: menu visibility and action permissions are set separately from each other.