Cohort Q&A: keep every cohort's answers
A Flow for a course or accelerator where participants ask, mentors answer, and each cohort starts with the last one's solved questions.
A template is a setup recipe you follow in Flow settings. There is no one-click copy yet.
Cohort Q&A Search answersWave types to turn on
Best for: Course leads, accelerator program managers, bootcamps.
Question
Participants ask. Idle questions archive after 14 days, which keeps the open list honest.
Discussion
Introductions and weekly check-ins.
Session
Weekly office hours with mentors, set to repeat.
Announcement
Deadlines and schedule changes. Pin the current one.
Opportunity
Optional. Useful if partners post internships or projects.
OptionalProfile types and what each can do
Profile types are custom roles. Each sits on top of a base Flow role and adds its own limits.
| Profile type | Base role | Can create | Can do | Pages |
|---|---|---|---|---|
| Participant | member | Questions (up to 10), discussions | Reply | None |
| Mentor | member | Sessions (up to 5), questions | Reply, mark helpful | Speaker Page (1) |
| Program lead | admin | All types | Reply, mark best, moderate | Any |
Set it up in six moves
Create the Flow
Choose the course category, add your logo and set the join mode to a code.
Add two profile types
Participant and Mentor, with the permissions in the table above. Keep yourself as owner or admin.
Set default tags
Add the week tags and topic tags so every question lands somewhere browsable.
Post the first four Waves
Introductions, the week one announcement, a repeating office-hours session and one real question with a marked answer.
Invite the cohort
Send the join code, or create an invite link for each profile type so mentors join as Mentors.
Mark answers every week
In office hours, mark best answers on the week's questions. That is what the next cohort will search.
Access and moderation settings
Start with these, then adjust once you see how members use the Flow.
Join mode: Join code
Share one code in your welcome email. Change it when the cohort closes.
Visibility: Private
Only members see Waves, so participants can ask freely.
Reports
Keep the default: any member can report, program leads review.
Slow mode
Turn it on for the introductions Wave in week one if it gets busy.
Digest
Suggest weekly digests in your welcome email so quiet members still see solved questions.
Variations
One Flow, many cohorts
Keep one Flow and add a cohort tag such as #cohort-4. Search covers every cohort at once.
A Flow per cohort in one Room
Give each cohort its own Flow and group them in a Room, so alumni and DMs carry across.
Paid mentors
Give mentors a speaker Page so participants can book time through its call-to-action button.
The recipe as data
For partners creating Flows through the API. This is the profile type shape Dium stores in a Flow's settings. Dium adds each type's short code itself.
{
"profile_types": [
{
"name": "Participant",
"perms": {
"can_create_wave": true,
"can_reply": true,
"can_invite": false,
"can_create_exhibit": false,
"threads": [
{"type": "question", "create": 10, "view": true},
{"type": "conversation", "create": 5, "view": true}
],
"reply_wave_types": ["conversation", "question", "session"]
}
},
{
"name": "Mentor",
"perms": {
"can_create_wave": true,
"can_reply": true,
"can_invite": false,
"can_create_exhibit": true,
"threads": [
{"type": "session", "create": 5, "view": true},
{"type": "question", "create": 10, "view": true}
],
"pages": [
{"type": "speaker", "create": 1, "join": "unlimited"}
],
"reply_wave_types": ["conversation", "question", "session"]
}
}
]
}settings_json when calling ladder.php action create. Check the API reference for which fields are applied on create before relying on it.Start free and follow the recipe.
Create your Flow, then work through the six moves above. Free while you are under 50 members.