Guides · Discussions

Discussions workflow in Stride

Use this guide to run discussions with a clear create-read-update rhythm, so teams can resolve decisions without losing context across chat, meetings, and files.

Read permissions deep dive

1. Create a new discussion

Create

Open Discussions and click New discussion.
Set a clear title and add the first message so people know the decision or problem space.
Pick the visibility scope that matches the audience (for example org-wide, board-only, or team).
Submit to publish the thread and notify participants in the workspace.

2. Read and triage active threads

Read

Use the filter tabs to focus on unread, meetings, decisions, files, or all threads.
Open a topic to review latest messages, participant activity, and context links.
Use unread indicators to prioritize what needs a response first.

3. Update the conversation and access

Update

Reply in-thread to keep decisions and follow-ups in one place.
Add participants when broader visibility is needed.
Remove participants when scope changes or the thread is no longer relevant to them.
Mark threads as read through normal viewing so your unread queue stays accurate.

4. Keep discussions healthy over time

Maintain

Use concise thread titles so the list remains scannable.
Prefer one topic per decision to avoid mixing unrelated subjects.
When a thread is resolved, post a final summary message with outcome and owner.
If a topic is no longer useful, remove or limit participants instead of starting duplicate threads.

Discussion quality checklist

Use explicit titles like "Q2 budget approval" instead of generic names like "Question".
Start each thread with context, proposed decision, and expected deadline.
Limit participant lists to people who can approve, execute, or unblock next steps.
Post final outcomes in-thread so future readers can recover decisions quickly.