A Journey is a collection of Milestones. Members of the community must complete each Milestone in the Journey, in any order, to receive a reward. Each Journey’s availability to the community can be controlled by the Journey’s activation status and completion window.
Did you know you can create one with our MCP server too? Try asking your agent: “Create a New Member journey with milestones for posting an intro, replying in a thread, and registering for an event.”
Every journey carries the same settings, whichever surface you create it on.
Name - What members see. Up to 100 characters.
Completion window - The interval during which members’ actions count towards this journey. Members can only complete milestones inside it.
Start - When actions begin counting. It defaults to the moment you create the journey, so earlier activity does not count. To include earlier activity, set the start back to the point where you want counting to begin.
End - When actions stop counting. A journey is set to inactive once it ends. Leave it blank to keep the window open indefinitely.
Completion award - The award granted automatically when a member completes every milestone. Optional.
Active - The journey’s publication status. Members can only make progress when the journey is active and the action falls inside the completion window.
You can create up to 3 journeys. More depend on your plan.
Go to Journeys under Engagement. The table lists every journey in your community.
The Journeys page in Studio
Click Create journey. The wizard has two steps.
The Details step of the create-journey wizard in Studio
1
Details
Set the journey settings above. Starts and Ends are shown in your local timezone, and Completion award offers No award if you don’t want one.
2
Milestones
Add the steps members complete on this journey. This step is optional: you can add or change milestones at any time from the journey’s own page.Click Add milestone, then Create journey when you are done.
The Milestones step of the create-journey wizard in Studio
Counting rules differ per action: logging in counts per successful login, registering counts once per unique event, replying counts once per unique thread, and voting counts once per poll. Reaction and message actions never count activity directed at yourself.
Click a journey in the list to open its detail page. From there you can edit its details, add, edit, reorder, and delete milestones, and read its progress analytics.
Next, you can manage the Milestones that make up the Journey. Click the ••• menu next to the Journey and select the 🚩 Manage Milestones action.
Manage Milestones menu action
In Slack: Milestones list for a Journey
Modifying the Milestones of an active Journey can have unintended consequences for members who are mid-progress. See Modifying Milestones of an Active Journey for details.
You can customize the display order of Milestones within a Journey. From the Milestone list, click the ••• menu next to a Milestone and use the Move Up or Move Down actions to rearrange the order. The updated order is reflected everywhere Milestones are displayed, including the member-facing “My Journeys” panel. This is purely a visual change and has no effect on the order in which milestones are achieved.
In Studio, milestones are managed from the journey’s own page. See Milestone fields and Milestone action types above. The rest of this section covers the Slack flow.A Milestone is a certain goal or criteria that a member of the community can meet in order to receive a reward. Each Milestone is associated with a single parent Journey.You can create up to 10 Milestones per Journey.
To access Milestones for a Journey, click the Manage Milestones menu option from the Journeys List panel. Click + Create Milestone button to access Milestone creation, where you can configure the following:
Count Threshold - for supported action types, the Count Threshold is the number of actions the member must perform in order to complete the Milestone. For example, for the “Post in channel” Milestone, setting the Count Threshold to 10 would mean the member must post 10 times in the channel to complete the Milestone. See action types.
Scope to: Slack Channel - for supported action types, the actions can be scoped to a specific Slack channel (only activated channels may be used). Actions must occur by a member in this channel to count towards completion of the Milestone. If left blank, actions across allactivated channels will count towards completion of the Milestone.
Scope to: Emoji - for supported action types, the actions can be scoped to a specific emoji. Actions must use this emoji to count towards completion of the Milestone. If left blank, any emoji will count towards completion of the Milestone.
In Slack: Create Milestone modal
You cannot edit the Action of a Milestone after it has been created.
Counted per unique Event (i.e. registering multiple times for the same Event only counts once towards the Milestone)
When a member registers for a Calendar Event
Vote in a poll
A user participates in a Tightknit poll by voting at least once. Excludes anonymous polls.
Counted per unique poll (i.e. voting multiple times for the same poll only counts once towards the Milestone)
When a member votes in a poll
Milestone progress is checked in response to member activity, not on a schedule. The check is not limited to the channel a Milestone is scoped to: when a member performs one of the actions above, Tightknit re-checks their progress on every Milestone that uses that action, counting all of their qualifying activity within the Journey’s start and end dates.This means a Milestone can be completed retroactively, but only for activity that falls inside the parent Journey’s completion window. For example, let’s say a member named Ozzy made a post in your welcome channel last week, and today you want to create a Journey with a Milestone for posting in that same channel. If you set the Journey’s start date to prior to last week, then Ozzy’s post will count towards the Milestone. If you set the Journey’s start date to today, Ozzy’s post from last week does not count and they would need to post in the welcome channel again to complete the Milestone.
The “Join the workspace” Milestone action type is always considered completed if it is part of a Journey, since it is implied that every user in the workspace has achieved this. This is the one action type that ignores the completion window: members who joined before the Journey’s Start Date still have it counted as complete.
Slack Connect channels have limited support with Milestones and Journeys at this time. Activity on threads which were started by users from external workspaces will not count towards your own users’ milestone progress.
When a member meets the conditions required to complete a Milestone in the community, they will receive a private notification along with the Award, if any award is configured.
Adding or Removing Milestones of an Active Journey
Adding a new Milestone to an active Journey adds a new requirement for all members who have not yet completed the Journey. Members who are in progress will now need to complete the new Milestone in addition to any remaining ones. Members who previously completed the Journey keep their Journey achievement. The new Milestone will appear as not yet achieved in their “My Journeys” panel, but a note will indicate that their completion is not affected.Removing a Milestone from an active Journey removes that requirement for all members. Members who were working towards the removed Milestone will lose their progress on it. Removing a Milestone does not automatically complete the Journey for members who have now achieved all remaining Milestones. Journey completion is only evaluated when a member achieves a new Milestone within that Journey. If a member has already achieved all remaining Milestones, there is no trigger to re-evaluate their Journey completion.
Removing a Milestone permanently deletes all achievement records for that Milestone. See Deleting a Milestone or Journey for details.
When you edit a Milestone that belongs to an active Journey, the change takes effect immediately for all future progress checks. However, the impact depends on each member’s current status with that Milestone.Members who have already completed the MilestoneCompleted Milestones are stored as achievement records. These records are not affected by changes to the Milestone’s criteria. If a member has already completed the Milestone and received credit, they keep that achievement regardless of any edits you make.Example: A Milestone requires 1 post in #introductions. Alice has already completed it. You change the Milestone to require a post in #general instead. Alice keeps her achievement. She does not need to post in #general.Members with partial progress towards the MilestoneMembers who are actively working towards a Milestone but haven’t completed it yet are the most affected by changes. Because progress is calculated dynamically against the current Milestone criteria, any prior activity that no longer matches the updated criteria will stop counting towards their progress.Example: A Milestone requires 5 posts in #introductions. Bob has posted 3 times in #introductions. You change the Milestone’s channel to #general. Bob’s 3 posts in #introductions no longer count. His progress resets to 0, and he now needs 5 posts in #general.Example: A Milestone requires 3 reactions given in any channel. Carol has given 2 reactions. You increase the count threshold from 3 to 5. Carol still has her 2 reactions counted (the action type and channel didn’t change), but she now needs 3 more instead of 1 more.New members who haven’t startedNew members are unaffected. They will see and work towards the updated Milestone criteria from the start.
Deleting a Milestone permanently removes all achievement records for that Milestone. Members who previously completed it will lose that achievement, and if the Milestone was the final one needed to complete a Journey, the Journey completion is also affected.
If you want to retire a Milestone without losing member achievements, edit the Journey instead. You can deactivate the Journey to hide it from new members while preserving all existing progress and achievements.Deleting an entire Journey removes all of its Milestones and their associated achievement records. If you want to stop new members from starting a Journey while keeping historical data intact, deactivate the Journey rather than deleting it.
When a member completes a Milestone that is a part of a Journey in the community, they will receive a private notification indicating their new progress towards completing the Journey.
Admins can track how the community is progressing through a journey in Studio. Go to Journeys under Engagement and click a journey’s name to open its detail page, then select the Analytics tab.
Completion rate — the percentage of active members who have completed every milestone in the journey.
Members completed — the count of active members who have finished the journey.
Avg milestones completed — the average number of milestones completed per active member.
All rates are measured against active, non-bot members. The toolbar filters for team members and member type apply here, so you can view progress for specific segments.
A horizontal bar chart shows the share of active members who have completed each milestone. Use this to identify which milestones are easy wins and which are bottlenecks.
A table lists every active member with their progress through the journey’s milestones, sorted by furthest along first. Members who have not started appear at the bottom. You can search by name or email and paginate through the results.
Milestone types cannot be modified once a Milestone is created.
A Milestone added to a Journey after that Journey’s completion window has closed can never be completed. Progress is only checked in response to member activity that falls inside the window, so no later activity will trigger the check.
Slack Connect channels have limited support with Milestones and Journeys at this time. Activity on threads which were started by users from external workspaces will not count towards your own users’ Milestone progress.
If a custom emoji which is connected to a Milestone is removed from the Slack workspace, it will no longer be possible for users to make progress towards that Milestone. Update the emoji or remove the Milestone.
Emoji activity that uses emoji aliases does not count towards Milestones connected to the original emoji.
Message-based activity is only tracked on messages which were sent while the Tightknit app was present. This may exclude non-activated channels and older messages sent before Tightknit was installed or activated in the channel. For older messages, you can use the message shortcut to sync the message manually.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.
