> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.superpath.io/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # Assigning Roadmaps to Teams or People # Assigning Roadmaps to Teams or People **In this article:** * Overview * Before you start * How to assign a Roadmap Level * What happens when you assign * Things to keep in mind * FAQs * Who can do this ## Overview Assigning a Roadmap is how your people get their development plan. You always assign one **Level** of a Roadmap rather than the whole grid, because the Level is what tells SuperPath where that person currently sits — the competencies, behaviours and learning they should be working towards. You can assign to individuals, to a whole Team, or to a mix of both in one go. ## Before you start The Roadmap must be published. While it is unpublished the assign icon is greyed out and its tooltip reads *"Publish roadmap to be able to assign people"* — see *How to Publish a Roadmap*. It also helps to know who is already on the Roadmap before you assign. Use the **View learners** (chart) icon on the Roadmaps list to check — see *How to View Learners on a Roadmap*. ## How to assign a Roadmap Level 1. Go to **Roadmaps**. 2. Click the assign (people) icon. It is in the row actions for each Roadmap in the list, and also in the top right of the Roadmap editor when you have a Roadmap open. ![](https://storage.googleapis.com/superpath-help-centre/assigning-roadmaps-to-teams-or-people/01-roadmaps-list-assign-action_4379c8a2.png) 3. In **Assign to people and teams**, open the **Roadmap Level** dropdown (**Select a roadmap level**) and choose the Level you are assigning. ![](https://storage.googleapis.com/superpath-help-centre/assigning-roadmaps-to-teams-or-people/02-assign-dialog-roadmap-level-dropdown_cfea56b8.png) 4. Click the **Search people and teams** box and start typing. Click a person or a Team in the results to add them — Teams are marked with a **Team** badge. Repeat to add as many as you need, and use the **x** beside an entry to remove it. 5. Leave **Notify people** switched on if you want assignees to be told about their new Roadmap, and optionally type a message in **Add a custom message to assignees (optional)**. Switch it off to assign quietly. 6. Click **Assign**. ![](https://storage.googleapis.com/superpath-help-centre/assigning-roadmaps-to-teams-or-people/03-assign-dialog-team-and-person-notify_68dcb03c.png) SuperPath confirms with *"This roadmap has been assigned successfully"*. ## What happens when you assign * Each person gets their own Roadmap Level record for that Level of that Roadmap. This is what appears on their profile and in Roadmap reporting — it is not a standard learning assignment. * A Team is expanded to its members at the moment you assign, and duplicate people across Teams are only assigned once. * Any learning attached to that Level with **Auto Assign** switched on is assigned at the same time: Pathways as a Pathway, and Content, Events and Forms as an assignment. Knowledge articles are skipped — see *How to Auto-Assign Learning at a Competency Level*. * With **Notify people** on, assignees are notified by email, Slack and mobile push (depending on what your organisation has enabled), including your custom message. You are not notified if you assign a Roadmap to yourself, and deactivated users are not notified. * Learners find their Roadmap from the notification or from their profile's **Roadmap** tab — see *How to View Your Assigned Roadmap*. ## Things to keep in mind * You must choose a Level. If you click **Assign** without one, SuperPath warns *"Please select a roadmap level"*. * **Assign** stays disabled until you have added at least one person or Team. * Assigning to a Team is a point-in-time action, not an ongoing rule — anyone who joins that Team later is not assigned the Roadmap automatically. To automate it, use a Workflow (see *How to Use Roadmaps in Workflows*). * The assign dialog does not flag people who are already on the Roadmap, so check the learners report first to avoid assigning the same Level twice. * Roadmap assignment is deliberately simple: the start dates, due dates, scheduling, learning evidence and approval options you see when assigning content or a Pathway are not part of assigning a Roadmap. * To move someone to a different Level later, complete their current Level and assign the new one in the same action — see *How to Progress a Learner to the Next Roadmap Level*. ## FAQs **Can I assign a whole Roadmap instead of one Level?** No. You assign a specific Level, which sets the person's starting point on the Roadmap. **Why is the assign icon greyed out?** The Roadmap is still unpublished. Publish it and the assign action becomes available. **Will new Team members be assigned the Roadmap automatically?** No. Assigning a Team assigns the people in it at that moment. Use a Workflow if you need it to happen automatically as people join. **Can I assign different Levels to different people at once?** Not in one action. Assign the first group their Level, then repeat for the next Level. **Do assignees have to be notified?** No. Switch **Notify people** off before clicking **Assign** and no notification is sent. ## Who can do this **Owners**, **Admins** and **Managers** can assign a Roadmap Level to people and Teams. **Content Managers** can create, edit and publish Roadmaps, but they cannot assign them — their Roadmap Level permission only covers their own records, so an attempt to assign is refused. **People Managers**, **Instructors**, **Employees** and **Restricted** users cannot assign Roadmaps and do not have access to the admin Roadmaps area.