Before · 2026.07
Invitation controls
Removed · direct invite path
Release Updates
Explain what changed—and update every customer lesson it touches.
GuideThread turns an approved release into an impact record: the changed behavior, affected customer roles, required action, open questions, and tutorials or FAQ answers that need review.
Separate changed facts from unchanged assumptions.
The comparison keeps four states visible before anyone rewrites customer-facing education.
After · 2026.08
Policy before invitation
Open · delegated administration
Changed
The behavior, label, sequence, permission, or outcome that differs in this version.
Unchanged
The surrounding behavior customers can continue to rely on.
Removed
A step, option, or path that should no longer appear in education.
Open
A product question that must be resolved before the explanation is approved.
Release: workspace invitation controls
Example release record · neutral software workflow
- Source version
- 2026.08
- Affected roles
- Workspace administrator; team owner
- Changed behavior
- Invitation policy now appears before member invitations are sent.
- Unchanged behavior
- Existing member roles are not modified by the invitation policy.
- Customer action
- Administrators review and save a policy before inviting new members.
- Open point
- Confirm behavior for workspaces with delegated administration.
- Affected education
- Administrator onboarding; invite-members tutorial; invitation-pending FAQ.
- Review owners
- Product; support operations; customer education.
Every affected asset gets a decision.
One source version branches into content decisions instead of a row of lookalike cards.
Administrator onboarding · the teaching step changed.
Invite-members tutorial · policy becomes a prerequisite.
Source
2026.08
Workspace invitation controls
Existing member roles · surrounding behavior stays current.
Invitation-pending FAQ · open point needs an owner.
Use only when no current asset exists or advice is no longer current.
A customer update should answer four questions.
Each answer stays short because it describes a distinct customer decision.
01
What changed?
Name the behavior, not only the feature.
02
Who is affected?
Identify role, plan, workflow, or prerequisite.
03
What should they do?
State the customer action and completion cue.
04
Where can they learn the workflow?
Link to the approved tutorial or guide for the same product version.
Release Updates questions
Should every release become a tutorial?
No. Create or revise education when the change affects a customer task, decision, prerequisite, or expected result. A technical change with no learning impact may only need a release record.
Who decides which assets are affected?
The release owner identifies the changed behavior, and the content owner compares it with the source and steps behind existing education.
How should an unresolved product question appear?
Record it as an open point with an owner. Hold the affected explanation until the answer is approved; do not fill the gap with an assumption.
What happens to the previous tutorial?
Keep its version and publication history, mark it superseded when the replacement is approved, and remove it from active distribution according to the destination's content policy.
Start with one release
Give the next tutorial a source, owner, audience, and version before production begins.
Use the release intake template to identify what changed, who needs an explanation, which assets are affected, and what still needs review.