Users understand what changed
An explanation names the change, its value and the next action.
Users see a change, find the new location or feature and start using it at work. Your team gives customers one exact release explanation.
Choose a day and your team will have the report before the meeting.
The user completed the task and can keep working.
An explanation names the change, its value and the next action.
A short announcement on the changed screen leads to the feature or full entry.
One published entry explains the update in your product and on the public page.
Follow the user journey: take an action and see the result in the workspace.
Choose a day and your team will have the report before the meeting.
The user completed the task and can keep working.
BenefitHelps you focus on the current task.
What changedHides extra elements while you work.
BenefitHelps you give people access that fits their role.
What changedTeam settings now include administrator and member roles.
Start with a full entry, then prepare a short announcement for the screen where users see the change.
Explain the change and the user’s next step.
Publish the entry in the product, on a public page or in both places.
Show a pop-up to the right audience and lead to the entry or feature.
A pop-up draws attention to a change in the product. A changelog keeps details users can revisit.
No. It makes an entry available in the selected channel. Use a pop-up for an in-product message.
Yes. Set display rules by role, attributes, page and events.
Once connected, your team updates entries, messages and tours, then publishes a new version.
Show us a product update. In the demo, we will connect the full entry, announcement and user action.
Leave your details. We’ll email you to find a time for the demo.