Note: This article describes an experimental Labs feature, which may change without warning. If you're giving this feature a try, let us know your feedback by chatting with our Support team or starting a conversation in our Product Makers community!
Customers, prospects, and external stakeholders might request to have a more detailed look into your plans. This is why we recommend having approved customer-facing roadmaps to share with them.
By sharing or embedding your roadmaps you can ensure that your most important stakeholders and customers are well informed and can help guide you to better outcomes.
This article covers:
- Sharing roadmaps publicly
- Republishing roadmap changes
- Showing portal cards on roadmaps
- Embedding roadmaps
- Limitations
Sharing roadmaps publicly
To share your roadmaps publicly, open your roadmap, and follow these steps:
- Click the Share button (
) in the top navigation bar of your roadmap.
- Toggle on: Share a link with anyone.
- Then, you can choose if you want to share a link (Copy link
) or get the embeddable code to embed your roadmap on an external platform (Embed
):
Note:
- The customer facing roadmap link is unique and different from your internal one.
- You can only share roadmaps publicly on column-based roadmaps.
Sharing restricted products
If you try to share a restricted product or feature on your customer-facing roadmap, we will show you a warning message. However, if you wish to still share the product you can click Copy link ():
Republishing roadmap changes
Whenever you make any changes to your customer-facing roadmap, those won't appear on your shared roadmap. To make sure your shared roadmaps are up to date you need to republish them.
To republish your roadmap, follow these steps:
- Save your roadmap, if you haven't done so already.
- Click Publish (
) in the top navigation bar of your roadmap.
Showing portal cards on roadmaps
We recommend showing customers portal cards on roadmaps, rather than feature descriptions. If you want to show portal cards on your customer-facing roadmap, follow these steps:
1. Click Share () in the top navigation bar of your roadmap.
2. Toggle on Share a link with anyone.
3. Click the menu icon () and toggle on Show portal cards on roadmap:
Embedding roadmaps
Embedding your roadmap is great for sharing a roadmap with customers on your website or sharing it with colleagues who have access to an internal wiki.
1. Click Share () in the top navigation bar of your roadmap.
2. Toggle on Share a link with anyone.
3. Click the Embed button () to copy the iframe embed code.
You can paste the link in any place that supports an iframe and the viewers will be able to see and interact with your customer-facing roadmaps.
Embedding roadmaps in Notion
You can embed your customer-facing roadmap into your Notion articles. To do that, follow these steps:
- On any Notion page, click the plus (+) on the left-hand side.
- Click the Embed option.
- Paste the iframe link of your customer-facing roadmap. Your roadmap will appear and you can resize it by dragging the edges:
Embedding roadmaps in Confluence
You can embed your customer-facing roadmap into your Confluence pages. To do that, follow these steps:
- In Productboard copy your roadmap link by clicking (Copy link
).
- In Confluence, click the Insert button (+) at the top.
- Select the iframe option.
- Paste the iframe link of your customer-facing roadmap in the URL input box.
- Resize your roadmap by changing the width and height values.
You can also add iframes to pages by using the Confluence apps like iFrames for Confluence.
Limitations
There are some limitations in our LABS🧪 release you should be aware of:
- The roadmaps are a snapshot in time and don't update in real-time. So if you make any changes to your roadmap after you shared it, you'll need to republish it.
- Roadmaps shared via URL will not display subfeatures.
- You can't protect the roadmaps you share with a password.
- You can't display dependencies and owners on the roadmaps you share.
To check the progress on the items above, check our Portal.
Comments
Article is closed for comments.