Ctrlk
Home
For the complete documentation index, see llms.txt. This page is also available as Markdown.

5. Groups and Rooms

Purpose. Groups are the core operating units of Nexus Platforms. They are work rooms—built for collaboration, delivery, review, and decision support. When used correctly, Groups keep the network high-signal and make outputs reusable.

Quick links (bookmark)

5.1 What Groups Are For (work rooms vs social channels)

Groups are for doing work together. They are the place where:

  • work threads live (so they’re searchable and durable)

  • drafts are reviewed and improved

  • tasks are assigned and tracked (often linked to quests/builds/bounties)

  • a room’s outputs get promoted to KB/Journals/Campaigns when ready

Groups are not for:

  • generic networking (“nice to meet you” posts without an ask)

  • broad promotion, recruiting, or sales

  • duplicating the same announcement across multiple rooms

  • long debates with no output or next action

Routing rule

5.2 How to Find and Join Groups (recommended first groups by domain)

5.2.1 Find groups fast

  1. Open the Groups directory: https://therisk.global/groups/

  2. Use the group search/filter tools (keyword, domain, program name).

  3. Open the group page and read:

    • the group purpose

    • the pinned Start Here post (if present)

    • membership rules (open / request / invite-only)

5.2.2 How to join (step-by-step)

  1. On the group page, click Join Group (or Request to Join).

  2. If there’s a question field, answer it in 1–2 sentences:

    • your scope (role + domain)

    • what you will contribute

    • what you’re looking for

  3. After acceptance, read pinned posts first before posting.

5.2.3 Recommended first groups (by domain)

Because group names can vary by implementation, use this rule-based method:

Pick two groups only in Week 1

  • 1 Domain Home group (your core domain community)

  • 1 Working Room group (a program or deliverable room)

To identify your best matches:

  • Search the directory using your lane keywords (e.g., “Financial”, “Technology”, “Health”, “Policy”, “Public”, “Resilience”, “Standards”, “Verification”): https://therisk.global/groups/

If you want the platform to route you:

5.3 Group Etiquette (how to participate without creating noise)

Principle: every post should create clarity, not volume.

5.3.1 The “high-signal” posting rule

Every post should include:

  • Context (1–2 lines)

  • What’s new / what you’re sharing

  • The ask (review / collaborator / decision / pointer)

  • Deadline (if any)

  • Links to the relevant artifact/thread (avoid duplicate copies)

If you can’t state the ask, don’t post yet.

5.3.2 Don’t fragment work

  • Don’t create multiple threads for the same topic.

  • Keep updates in the original thread unless the topic changes materially.

  • Summarize long threads periodically (one “state of play” post).

5.3.3 Avoid cross-post spam

If multiple groups need to know:

  • Post in the primary group thread.

  • Share a short pointer elsewhere with the link (no full repost).

5.3.4 Tone and conduct

  • Disagree with ideas, not people.

  • Ask clarifying questions before criticism.

  • Keep it professional; assume leaders are reading. Rules and integrity norms: https://therisk.global/network-charters/

5.4 Creating a Group (eligibility, naming conventions, purpose template)

Group creation may be enabled only for certain members or roles. If you don’t see a Create Group option, it means it’s gated.

Start here: https://therisk.global/groups/

5.4.1 When to create a group (decision rule)

Create a group only if:

  • the work is ongoing (not a one-off question)

  • you need a shared room for collaboration and review

  • the output will produce artifacts (briefs, templates, plans)

  • there will be a regular cadence (weekly/biweekly)

If it’s a single question: use Q&A instead: https://therisk.global/questions/ask/

5.4.2 Naming conventions (clean and searchable)

Use this structure:

[Domain] — [Purpose] — [Type]

Examples:

  • “FIN — Stress Testing — Working Room”

  • “TEC — Third-Party Risk — Review Room”

  • “HLT — Supply Chain Resilience — Build Room”

  • “POL — Standards & Governance — Drafting Room”

Rules:

  • Start with the domain lane (FIN/TEC/HLT/POL/PUB or your platform’s equivalents)

  • Use one clear noun phrase (not a slogan)

  • Avoid using “official”, “board”, “chair” unless formally granted

5.4.3 Purpose template (copy/paste)

Use this “Group Charter” format as the pinned first post:

  • Group name:

  • Purpose (1 sentence):

  • Scope (what’s in / out):

  • Primary outputs: (e.g., checklist, brief, draft standard, playbook)

  • Cadence: (weekly/biweekly; day/time; timezone)

  • Participation lanes: (contributors / reviewers / hosts / builders)

  • Visibility & handling: (public-safe vs member-only rules)

  • How to start (first task):

  • Moderator(s):

  • How decisions are recorded (if any):

5.5 Running a Group (weekly cadence, pinned posts, moderation checklist)

5.5.1 Minimal operating cadence (recommended)

To keep a group alive without noise:

Weekly (15 minutes)

  • Post a “This Week” thread:

    • priorities (3 bullets)

    • 1–3 asks (review needed, volunteers needed)

    • upcoming events (links)

  • Close out with a “Done / Next” note

Monthly (30 minutes)

  • Publish a one-page “State of the Room”:

    • what shipped

    • what’s stuck

    • what’s next

Use Events for meetings so attendance and links are centralized: https://therisk.global/events/

5.5.2 Pinned posts every functional group should have

  • Start Here / Group Charter (purpose, scope, cadence, rules)

  • How to contribute (what to post, templates, lanes)

  • Current priorities (updated weekly)

  • Links to canonical artifacts (KB/Journals/Docs as relevant)

5.5.3 Moderation checklist (light but firm)

  • Remove spam and off-topic promotion

  • Enforce “no misrepresentation” and visibility norms

  • Merge duplicates (point people to the canonical thread)

  • Encourage “ask + next action” formatting

  • Move “how-to” questions into Q&A so answers become reusable: https://therisk.global/questions/

5.6 Inviting Members and Managing Requests (approvals, access controls)

5.6.1 Inviting members

Identify members via the directory: https://therisk.global/members/

Invite with a specific ask and context:

  • “We need review on X.”

  • “We’re drafting Y and need your domain lens.”

  • “Please join this build room for deliverable Z.”

5.6.2 Managing join requests (best practice)

If your group is request-based:

  • Approve members who have a clear match to purpose/scope.

  • Decline (or redirect) if they’re misrouted:

5.6.3 Access control settings (typical modes)

Depending on your configuration, a group may be:

  • Open (any member can join)

  • Request-to-join (approval required)

  • Invite-only (restricted rooms)

Use stricter access when:

  • work involves sensitive operational context

  • drafts require controlled review

  • the room is tied to governance or eligibility pathways

5.7 Group Roles & Permissions (admin/mod/member capabilities)

Exact controls depend on your platform configuration, but the standard model is:

Admin

  • change group settings and visibility

  • manage roles and membership

  • approve/deny requests

  • pin posts, manage structure, enforce standards

Moderator

  • enforce rules and remove noise

  • manage threads and duplicates

  • route members to correct lanes

  • escalate integrity issues when needed

Member

  • post, comment, contribute artifacts

  • join events and program threads

  • request changes via the group’s process

If you’re unsure what you can do in a given group, check its About section and pinned posts.

5.8 Posting in Groups (best formats; where to put files/links)

5.8.1 Best post formats (copy/paste templates)

A) Review Request

  • Context:

  • What’s attached/linked:

  • What kind of review:

  • Deadline:

  • Decision needed (yes/no/notes):

B) Proposal

  • Problem:

  • Proposed approach:

  • Assumptions:

  • What we need from members:

  • Next step:

C) Progress Update

  • What changed:

  • What’s done:

  • What’s blocked:

  • What’s next:

  • Who can help:

D) Meeting / Session Follow-up

  • Summary (5 bullets):

  • Decisions (if any):

  • Action items (owner + date):

  • Links/resources:

5.8.2 Files and links (best practice)

  • Prefer links to canonical sources (Docs/KB/Journals) over re-uploading duplicates.

  • If you upload a file, include:

    • version number

    • date

    • purpose

    • what you want readers to do

Use KB for repeatable guidance: https://therisk.global/kb/ Use Journals for curated releases: https://therisk.global/journals/

5.9 Archiving / Sunsetting Groups (when and how)

Groups should not live forever. Sunsetting keeps the platform clean.

5.9.1 When to sunset a group

Sunset when:

  • the work is complete

  • the room has been inactive for 60–90 days

  • the group was created for a time-bound campaign/build that ended

  • the group’s scope is duplicative of another room

5.9.2 How to sunset (clean process)

  1. Post a final Closeout note:

    • what was delivered

    • where the outputs now live (KB/Journals/Docs links)

    • who to contact for follow-up

  2. Pin the closeout note and lock new threads (if enabled).

  3. Update the group name with “(Archived)” if your configuration supports it.

  4. Redirect members to the successor room (link).

5.9.3 Preserve outputs properly

Group Operator Quickstart (first 20 minutes)

  1. Browse groups and join your two starter rooms: https://therisk.global/groups/

  2. Read pinned Start Here posts before posting.

  3. Post a clean introduction with your scope and one ask.

  4. Register for the next relevant event: https://therisk.global/events/

  5. If you need a new room, ask in Q&A whether to create a group or use an existing one: https://therisk.global/questions/ask/

Previous4. Search and NavigationNext6. Publishing and Content

Last updated

Was this helpful?