Skip to main content

October 2026

Let people who open a public or private link see your story map's attachments.

Written by Arpad Tamas

October 4

Let people with a shared link see your attachments 📎

When you share a story map with a public or private link, you can now decide whether the people opening it get the map's attachments too. Until now a shared board had no attachment panel, and images in card descriptions often showed up as broken images for your readers.

Turn it on for a link

  • On a next-gen board, open the Share dialog and switch on Allow access to attachments. Workspace admins find the same switch on the story map's Visibility tab.

  • There is one switch for the public link and one for the private link. They are independent, just like the other visibility settings of the two link types.

  • It's off by default. While it's off, a note under the switch reminds you that attachments aren't available to people using the link and that embedded images may appear broken.

What your readers get

  • The Uploaded files panel on each card, read-only: they can open files, browse images in the gallery and download them. They can't upload, rename or delete anything.

  • Images and file links in card descriptions and release goals work.

  • The name of the person who uploaded a file is shown only if Show user identities is on for that link.

When the switch is off, the panel isn't shown, images in descriptions appear broken and file links don't open, including links that were copied earlier.

You stay in control

  • Attachment links only open files of their own story map. They can't be used to change anything.

  • Turning off sharing or the attachment switch stops the links. Turn it back on and the same links work again.

  • Revoke & generate new on a private link also retires every attachment link handed out before.

  • Archiving the story map stops the links as well. Restoring it leaves sharing off, so you decide when to share it again.

  • Your workspace's email-domain and IP restrictions apply to attachments the same way they apply to the shared board.

  • A reader's browser may keep showing images it has already loaded until the page is reloaded.

Good to know

  • Images and links are supported in the forms our editors insert them: Markdown images, Markdown links and simple HTML image tags. Plain pasted URLs, comments, the "About this board" panel and persona descriptions aren't covered.

  • Public links created in the classic view now open the next-gen reader.

  • Visibility and link sharing are now managed in the Share dialog of the next-gen board. In the classic view these settings are read-only. An existing classic private link can still be copied or revoked, but new ones can't be created there; use a next-gen private link instead.

October 25

Your AI agent can create many cards in one go 🚀

Building a story map from a requirements document used to take your AI agent one call per card, which meant dozens of calls for a medium-sized map. Now your agent can create up to 25 cards in a single call: goals, steps and stories mixed together, under different parents. Fewer calls means faster results and fewer chances for the agent to lose track along the way.

What your agent can do

  • Create one or many cards on a story map in one call, with everything it could set before: title, description, release, color, estimate, assignee, personas, status, priority, business value, effort and annotations.

  • Put each card exactly where it belongs: directly before an existing card, or at the end of its siblings. Cards added to the same place keep the order the agent sent them in.

  • Build a whole new area of the map in a few calls. Parents need to exist already, so the agent creates the new goals first, then their steps, then the stories.

All or nothing

Every card is checked before anything is saved. If any card has a problem, none of them are created, and the agent gets the full list of problems for every card at once. It can fix them all and try again in one go, so you never end up with a half-built map.

If a call times out and the agent can't tell whether the cards were saved, it's told to check the story map before trying again instead of creating duplicates.

Easy to follow on the board

  • Open boards show the new cards live, in the same order you'll see after a reload.

  • On the Board Activity Panel, a multi-card call shows up as a single entry, for example "created 12 cards". Click it to see every card. With Follow Changes on, the board scrolls once per call, to the last new card.

  • Your team chat gets one summary message per call, with the first few card titles, instead of one message per card.

  • People mentioned in a card's description and the cards' assignees are notified just as before.

Good to know

  • One call works on one story map and can hold up to 25 cards. For bigger jobs, the agent splits the cards into several calls.

  • The new tool is called CreateStoryMapCards and replaces CreateStoryMapCard. If your own prompts or scripts mention the old name, switch them to the new one.

Did this answer your question?