Support

Most of this page you will never need. It is here for the day you do: a roadmap has vanished, or a charge looks odd. Or you want to know what happens to your work if you stop paying. If the answer is not here, write to support@roadsnap.app and a person will read it.

Getting hold of us

RoadSnap is a small operation, which cuts both ways: no support queue to vanish into, and no overnight shift. The reply comes from someone who knows how the product works.

When you will hear back

These are the targets we hold ourselves to, chosen to survive a bad week. A missed promise costs more trust than none.

Working days are Monday to Friday, Eastern time, where we are. A message sent on Friday evening is answered on Monday.

An answer is not always a solution. Some things take longer than a day. When that happens you are told so, rather than hearing nothing. Silence is what we are removing, not delay.

About the acknowledgement. It is automatic, from noreply@roadsnap.app, and means only that your message arrived. It covers the first four addresses above. feedback@roadsnap.app is read and does not send one. If you asked us to stop emailing you, it is not sent; the reply from a person still comes.

What to include

Four things make an exchange quick:

• The email address you sign in with. Without it we usually cannot find your account.
• The name of the roadmap, if the problem is about one.
• What you did, what happened, and what you expected instead. In that order, in a sentence or two.
• The version number. It is at the bottom of the roadmap menu, like RoadSnap v1.0.0 · 340 nodes · file v17.

If something looks wrong on screen, send a screenshot.

Please do not send us

Your password — there isn't one. Nor any code we email you: anyone holding one can sign in as you. We will never ask for either.

Signing in

RoadSnap has no passwords. You enter your email address, we send a one-time code, you type it in. Nothing to forget, reuse, or lose in somebody else's breach.

• The code has not arrived. Give it a minute, then check spam. It comes from noreply@roadsnap.app. Still missing? The usual cause is a typo in the address; try again.
• Codes are single use and expire. If you request several, only the newest works.
• Staying signed in. You should not have to sign in repeatedly on your own device. If you do, something is clearing cookies: a privacy extension, or a browser that wipes site data on close.
• Signing out is top-right in the app. It ends the session on that browser only.
• Shared or borrowed computers. Sign out when you finish. Your roadmaps stay in your account, reachable wherever you sign in next.

Where your work is saved

Two places, deliberately.

• In this browser, as you type. That is what makes RoadSnap fast: nothing waits on the network before appearing on screen.
• In your account, when you are signed in. That copy follows you between machines and survives a lost laptop.

The header shows the state:

If two devices edit the same roadmap, saves are checked against a version number, so one cannot silently overwrite the other. A real clash is shown rather than settled quietly. If you load the other copy, a snapshot of yours is taken first, so the wrong choice can be undone from History.

Working offline — planes, trains and bad hotel wifi

Offline is a normal way to work, not an error state. What that means:

• RoadSnap itself opens without a connection. Once you have used it on a device, the app is kept there. A reload, a closed laptop, or opening it from your home screen on a plane all work.
• Works offline: opening and editing any roadmap you have already opened on that device. Every change is written locally before anything touches the network. Insights, the timeline, presenting and exporting all work from that copy.
• Needs a connection: opening a roadmap for the first time on that device, the example library, signing in, Jira and Slack. Taking over editing from a colleague needs one too.
• When you come back: your work goes up on its own as soon as we can reach RoadSnap. You need not do anything or stay on the page; it will go on your next visit if it has to.

Online, you always get the current version of RoadSnap. The stored copy is used only when we cannot be reached, so you are never left on an old build.

The first time a roadmap is safely in both your account and that browser, RoadSnap says so, once. If you are flying tomorrow, open what you will need today.

One person editing at a time

In a team workspace, one person holds the right to edit a roadmap; everybody else has it read-only until they finish. That is deliberate, and it is why RoadSnap has no merge conflicts.

• You take the lease when you open a team roadmap, and hand it back when you close the tab.
• If a colleague holds it, the header says who, and the toolbar is inert rather than silently discarding what you type.
• If their laptop is dead in a bag, the lease lapses after about four minutes and you can take over. RoadSnap warns you that anything they changed and have not sent us may be lost when it arrives. We cannot tell from here whether there is any; if they are reachable, ask.

In a personal workspace there is nobody to contend with, so none of this appears.

Which workspace a roadmap is in

A roadmap lives in exactly one workspace, and that decides who else can open it. Not who made it, not who you invited: the workspace. Everyone in it can open every roadmap in it.

The workspace is chosen when the roadmap is first saved to your account: whichever one you were working in. One mistake is easy to make:

You should rarely need to do this by hand. When you create a team workspace, RoadSnap asks whether to bring the open roadmap with you. The People dialog says whether the people you are inviting can open it, with a link to move it if they cannot. The roadmap's workspace is also shown beside its name in the header, marked when it differs from where you are working.

To fix it, open the roadmap and choose Move this roadmap to another workspace. It is in the roadmap menu beside the other cloud commands, or type / and search for move. Pick the team. Everyone in it can open the roadmap from that moment.

Moving is not copying. There is still one roadmap; it has changed address, and the workspace it came from loses access. That is why taking a roadmap out of a team requires an owner of that team. An editor cannot remove something the whole team works from. Moving one of your own roadmaps into a team needs only edit access there.

Owners, editors and viewers — and handing a workspace over

A team workspace has three roles. Viewers read every roadmap in it and change nothing. Editors read and edit. Owners do both and run the workspace itself: inviting and removing people, setting roles, connecting Jira and Slack, and managing the plan.

An owner can change anybody’s role at any time, in People: the role beside each name is a picker and takes effect at once. You can also invite somebody as an owner from the start.

To hand a workspace over: open People and make the other person an owner. RoadSnap then offers to step you down to editor. You keep access to every roadmap; you simply stop running the workspace. You can also step down using the picker on your own row.

The one thing refused: a workspace can never be left with no owner. If you are the last owner, stepping down and removing yourself are both refused until somebody else is one. A workspace with nobody in charge cannot be run, so it is stopped before it happens.

Readers cost nothing. A viewer takes no seat. Editors and owners do, counted once across every workspace you own: the same person in three of your workspaces is one seat. Giving a viewer edit rights takes a seat; stepping an editor down, or removing them, frees one. An invitation for edit rights holds a seat until accepted or withdrawn.

Adding anyone to a workspace — even a viewer — is part of Team. On Free and Pro, show somebody a plan with a read-only share link, free on every plan. See Sharing a roadmap by link.

One subscription covers every workspace you own. You do not buy again for a second workspace of yours. If you are short of seats when you invite somebody, RoadSnap names the price of the extra seat and asks before adding it. The difference lands on your next invoice, prorated.

Why a feature can be missing from a roadmap you can open

Your plan comes from the workspace you are working in. Access to a roadmap comes from the workspace it lives in. Almost always the same. When they are not, you can open a roadmap while a different plan applies. Objectives, Jira write-back and the API come with Team, so in a workspace whose owner is on Free they are not drawn. Comments are not among them — see below.

You should not run into this. Opening a roadmap moves you into its workspace, so the plan that applies is the one its owner pays for. A note in the corner says so and offers to put you back. Not on a reload: a workspace you chose from the header stands.

Update now — the six items worth changing, not the forty

Update fatigue is why roadmaps go stale. Not disagreement, not the tool — the tedium of opening forty items to change six. Commands → Update now queues the open items nobody has looked at for longest. It walks you through them one at a time.

It is ordered by how long something has gone untouched, not by date. Stopping halfway still leaves the items that most needed a look handled. Three keys do everything — Enter if it is still right, Tab to skip it for two weeks, Esc to stop. Status and target can be changed in the queue; for anything else, Open this item takes you there.

The weekly digest links straight into it. The email has just named what has gone quiet, so its button opens the queue rather than the roadmap. An email that drops you on a dashboard to find those items by eye has saved you nothing.

Items you skip come back after two weeks. Finished and dropped items are never asked about, and neither are themes — a theme’s answer lives in its children.

Commenting needs an account, not a paid seat

Any member of a team workspace can comment on any item — including a viewer, who takes no seat. The seat pays for authoring the plan, not for being talked to. A viewer can read every roadmap, comment on any item, and change nothing.

Mention a colleague with @. Typing @ in a comment offers the people in the workspace. Pick one and they get one email with your comment and a link to the item. It falls under the "when somebody shares something with you" preference; somebody who has switched that off is not emailed, and the mention still shows.

Commenting does need an account, so a remark has a name against it. It also needs a roadmap saved to your account rather than living in one browser. If either is missing, the panel says which.

The Open a roadmap from the cloud list names the workspace beside each roadmap, so you can see where something lives without opening it.

Recovering a deleted roadmap

Deleting is recoverable for 30 days. Delete a roadmap while signed in and it goes from your account and every device you sign in on. It is not destroyed at once: it is marked deleted and kept for 30 days.

If a device still holds the roadmap — a laptop that was open on it, a phone that had it — open it there. The top right says Deleted from the cloud — saved on this device only. Click it and choose Restore it from this device. That copy becomes the cloud copy again, comments included. Any owner or editor of the workspace can do this.

If no device has it, email support@roadsnap.app with:

• the email address you sign in with;
• the name of the roadmap, as closely as you can remember it;
• roughly when you deleted it.

Restoring is quick at our end. A list of what you deleted, to restore from, is on the roadmap.

Attaching a file to an item — what we do instead

RoadSnap does not store files, by decision rather than omission. A note takes links, and images by their address — ![](https://…) — so the picture is shown from wherever it lives. Put the Figma frame, the Drive document or the shared folder in the note as a link. Name the file if the link might move.

The reason is not storage cost. A file attached to a plan is a copy, and copies go stale while the real artefact keeps changing where it lives. A stale duplicate becomes a second version of the truth, in a tool whose whole point is an accurate plan. It also keeps your export honest: a RoadSnap file is one file you can take and walk away with.

Getting work in and out

Your plan is yours. Everything can leave in a form something else can read.

All of them are in the roadmap menu, under Backup.

Bringing work in

• Open a file as a new roadmap — adds it beside what you have; nothing existing is touched.
• Replace this roadmap from a file — overwrites what is open, keeping its place and its cloud copy. Use this to restore a downloaded backup over the original.
• Paste or drag in a spreadsheet and RoadSnap builds the tree from it. Usually the fastest way out of Excel and into a shape you can restructure.

Files record the format version they were written against. Older files are migrated forward when opened, not refused.

Sharing a roadmap by link

Share in the roadmap menu makes a read-only link and emails it to the address you give. By default anyone holding the link can read the plan without signing in, so it can be forwarded. Untick Anyone with the link can read it and the link is bound to that one address. It then opens only after they sign in with a one-time code. Links made before 5 September 2026 are all bound.

Copy link makes a link anyone can read and puts it on your clipboard, with no email sent. It appears in the same list and can be withdrawn the same way.

A reader cannot change anything. If they try, they are offered Ask to edit: you get one email saying who asked, and decide by inviting them from People (Team). Share links are free on every plan and can be withdrawn at any time from the same dialog. A shared link shows assignee names from Jira, as the app does.

A shared roadmap carries a small Made with RoadSnap mark in the corner. It is how people who have never heard of us find us, and it is what a free plan pays with. On Pro and Team an owner can switch it off in Settings, per workspace.

Exports keep the mark either way, deliberately. A shared link is read inside RoadSnap, where the address and the name at the top already say what you are looking at. A deck or an image is read somewhere else, where nothing does. The spreadsheet is the exception: a trailing line would corrupt the file.

Email from RoadSnap, and how to stop it

Every email we send carries a link at the bottom to your email preferences, and you do not need to sign in to use it. Some of our email goes to people with no RoadSnap account, because a colleague shared a roadmap with them.

Product news and pricing are separate on purpose: follow what changes in RoadSnap without hearing about upgrades.

Your mail app's own Unsubscribe button works too, and stops everything at once. The preferences page can turn individual kinds back on.

The Monday summary of your own plans

Starting 31 August 2026. If you are in a workspace with roadmaps, a short email arrives on Monday with a reading of them. It says what finished this week against last, what is still open, and what is blocked and who it waits on. It also nudges you about open items with no owner or no date.

It is a reading of your plan, not news about RoadSnap. That is why it sits under “your roadmaps and your account” rather than product news. Somebody who has switched off marketing still wants to know their programme slipped a month. It goes only to people in that workspace and says nothing they could not see by signing in.

A week with nothing to say is skipped, not sent. If nothing finished and nothing is blocked, no email goes out. That bar is higher than the Slack digest's on purpose. A Slack post costs nothing and scrolls away; an email does not. The first one you get sets what you expect of all of them. Switch it off like anything else on the preferences page.

How often

Each kind of email has its own limit, applied when we send rather than promised here. The Monday summary goes at most once in six days. The “this roadmap has gone quiet” nudge goes at most once in 25 days, and an ending-trial notice once. A busy week is the summary plus one notice.

What changed, and when

The changelog says what shipped and when, written for the person using RoadSnap rather than for the commit log. Follow it without an account through the Atom feed, or switch on What is new in RoadSnap on your email preferences. Both are optional and neither is on unless you ask.

Reading the plan back

Insights answer the questions a tree cannot answer by being looked at. They are read-only: nothing here changes your plan. Each says plainly when it has nothing to work with, rather than drawing an empty chart.

Two things about the forecast, before you rely on it. It waits until three separate weeks have had something completed, and says so until then. A projection built on one good week is worse than none, because somebody repeats it in a meeting. And the baseline comparison is against what you promised, so open work the baseline never covered is counted separately. A plan that looks on track only because half of it was never in the baseline is the failure this catches.

The critical path and the dependency map both need dependencies to exist. If none are recorded they say so and stop. Neither invents a link.

Items that recur rather than finish

Most items are done once. Some are commitments you keep — a quarterly review, a practice you maintain. Marking one Ongoing stops it reading “To do” for ever. It shows as Ongoing once demonstrated, with the date it first was, and stops counting as outstanding work. Until then it reads Ongoing, not yet run, the honest description of a commitment nobody has kept yet.

The AI Assistant

Press / or Ctrl-K and start typing. RoadSnap has one box for everything: it searches your plan, runs any command, and sends us feedback. If what you typed matches no command or item, the first thing offered becomes Ask the AI Assistant. The moment nothing matched is usually the moment you want it. There is also an Ask the AI Assistant command if you would rather start there.

It is on Pro and Team. Nothing calls a model on Free.

The answer appears as it is written, not all at once at the end. A Stop button sits where Send was while it works. Stopping keeps whatever had arrived, useful when the first sentence shows it has misread you.

What it will not do. It can add and edit. It cannot delete, archive, drop, reorder or move anything, and no setting lets it. Deleting cannot be made safe by asking first, and a plan is your record of what you decided.

What we send, and what we keep. The question and an outline of the roadmap — ids, titles and field values. Your notes are not sent unless the AI Assistant needs a particular branch; then that branch’s notes go with it. We keep a metering row per call — tokens and cost — and not the question or the answer. The provider is Anthropic; the full picture is on the Security page and in our DPA.

Asking is free; changing costs. A question that ends in an answer and no proposal does not count against the budget. A proposal does, and so does each unprompted suggestion. Before you type, the panel shows what a proposal typically costs in this workspace. It also shows the most one question can spend, and what is left this month. On Team the allowance grows with the seats.

There is a monthly budget per subscription, shared across every workspace you own, so a runaway question cannot surprise you. If you reach it the AI Assistant says so rather than failing oddly. A single question has its own ceiling too; at that point it stops looking things up and answers with what it has.

When it speaks first

Once a day, when you open a roadmap, the AI Assistant may offer two short things. One is where to start today; the other is one thing that would improve the plan itself. It appears as a small card in the corner. It never opens a dialogue, takes the cursor or interrupts you mid-edit. Most days it says nothing: it speaks only when both halves are worth interrupting for.

It can suggest changes, and you accept or reject them one at a time, as when you ask. At most two, and nothing moves until you press Keep.

Tell it what you thought. Useful and Not useful are recorded, and so is opening an item it pointed at or keeping a change it proposed. That is what stops the next suggestion being more of the same, and why it never repeats one you have seen.

Change how often, or switch it off: Settings → Suggestions — once a day, once a week, or never. It is a workspace setting, so off is off for everyone there. It does not affect asking it things yourself.

It can be wrong. It reads your plan, not the world, and says so when the plan does not answer a question. Treat a proposed change as a suggestion from a colleague who has read everything quickly, because that is what it is.

Snapshots and history

RoadSnap keeps snapshots so you can see what a plan looked like before and compare it with today. It also records one reading a day of the plan's shape: size, how much is complete, how much is flagged. The trend lines in History are drawn from those.

• Snapshots are taken on demand, and automatically as you work.
• Signed in, history belongs to the roadmap rather than to a browser. Trend readings and snapshots are kept in your account, so a second machine shows them too and clearing your browsing data does not take them. Snapshots from different machines are listed together.
• Signed out, history lives only in that browser — and is lost with it.
• Browser storage is finite. If it fills, RoadSnap drops the oldest snapshots first and tells you — your roadmaps are never dropped to make room. Your account keeps more than the browser, so a snapshot dropped locally may still be listed.
• Weeks with no reading are shown as gaps, never filled with a guess. A week nobody opened the roadmap is a fact, and a line through it would be invented data.
• On Free, History shows roughly the last quarter; Pro and Team show all of it. Where the view is shortened, RoadSnap says so, so a chart starting thirteen weeks ago is never mistaken for a plan that did.
• For anything you need to keep, download a copy. A file on your own disk outlives any account.

To see how one item changed, select it and use Commands → How the selected item has changed. It reads the snapshots, so it can say what changed and when. It cannot say who, or catch a value that changed and changed back between two snapshots; it says both on screen.

Plans and prices

All prices are in US dollars, per person, and exclude any sales tax that applies where you are. Annual works out at roughly ten months for twelve.

Managing your subscription

Everything below is self-service. Sign in, then click Plan & billing in the top right.

• Change plan. Move between Pro and Team in Plan & billing in the app; any offer on your subscription is kept. Switch between monthly and annual in the billing portal. Either way the change is prorated onto your next invoice: credit for what you have not used, and the difference charged. Only the person who pays can change or cancel the plan; another owner of a workspace it covers is told whose plan it is.
• Update your card. Same place. Billing emails link straight to it.
• Cancel. One button, no phone call, no retention interview. You keep your plan until the end of the period you have paid for; nothing is clawed back.
• Invoices and receipts. Every invoice is emailed when issued and can be downloaded from the portal.
• One subscription per account. If you already have a plan, a new checkout sends you to the portal instead, so you cannot pay twice.

Payments are handled by Stripe. We never see or store your card number.

What happens to your work if you stop paying

Your roadmaps stay in your account: you can always sign in, open them and download a copy. Paid features stop; nothing you made is taken away or held hostage.

Trials and codes

• On a founder plan with no card on file, the number of seats is fixed at what we set up. Write to support@roadsnap.app to change it.
• Founding and invitation codes. If you were given a code, enter it at checkout under I have a founder code. Codes are checked when used; if one is not recognised, checkout stops and says so rather than charging full price.
• An invited founder or Lions code is not a trial in the usual sense. It gives you a full year at no charge on whatever plan you pick, and 50% off for as long as you keep it afterwards. No card is asked for at signup: card details in exchange for a gift is friction at the wrong moment. You are prompted for one before the year is up. If you never give one, the subscription never silently turns into a charge.
• You will be reminded before any first charge. We email you about a week before a free period ends, saying what will be charged and when. If it is not for you, cancel in the portal and the charge never happens.
• Discount codes such as public early-adopter offers go in the promotion-code box on the payment page.

Charges, receipts and statements

Prices on the pricing page exclude sales tax. Where we are registered to collect it, tax is worked out from your billing address. That means GST and QST in Canada, state sales tax in the US, and VAT in Europe. It is shown at checkout before you pay, never added afterwards, and is a separate line on every receipt and invoice. If you have a business tax number, add it at checkout; in some places that changes what is charged.

• On your statement a charge appears as ROADSNAP.APP. The first charge after a free trial is marked as such. A payment arriving a year after you signed up is then recognisable rather than mysterious.
• Currency. Everything is billed in US dollars. If your card is in another currency, your bank converts it and may add a fee of its own.
• The business behind the charge is Loon Island Group Inc., a Canadian company, of 349 Avenue Kensington, Westmount, Québec, H3Z 2H2.

Refunds

We are not going to make you argue for one.

• Charged by accident, or forgot to cancel? Tell us within a reasonable time and we will refund it.
• Bought the wrong plan? Change it in the portal — proration handles the money — or write to us and we will sort it.
• Something did not work and we could not fix it? That is our failure, and a refund is the right answer.

Refunds go back to the card that paid, usually within five to ten business days, depending on your bank.

Leaving, and taking your work

Leaving should be as easy as arriving, or the product relies on the wrong thing.

• Take everything first. Download each roadmap as a .roadsnap.json file. That copy is complete and independent of us.
• Cancel in the billing portal.
• Close your account from Plan & billing → Close my account. You type the word CLOSE to confirm; it is the one action nobody else can undo for you.

A lost or stolen device

Settings → Sign out everywhere ends every session signed in as you, on every device, including this one. Nothing is deleted; you simply sign in again.

We deliberately show no list of your devices. RoadSnap cannot see your live sessions, only end them. Any list would be our record of past sign-ins, not what is signed in now, and could show a device already signed out. A wrong list about access is worse than none.

What closing does, and when. Your access ends at once and any subscription is cancelled. Everything you have — roadmaps, history, snapshots, memberships — is deleted 30 days later, and after that nobody can recover it. Inside those 30 days it is reversible: sign in and reopen it, or write to support@roadsnap.app. The delay is deliberate: a mis-click or a borrowed session should cost you an email, not everything you have written here.

If you own a team that other people are working in, closing is refused until somebody else owns it. Open People, make another member an owner and step down — or remove the members first. Your work is yours to delete; theirs is not, and a closure that took a colleague’s roadmaps with it could not be undone. Personal workspaces never block anything.

Prefer a person to do it? privacy@roadsnap.app works, and always will.

Your rights over your personal data — access, correction, deletion, portability — are set out in the Privacy Policy.

When something goes wrong

"Browser storage is full"

Browsers give each site a limited slice of local storage. When it fills, RoadSnap drops the oldest snapshots first and tells you. If it keeps happening, open Storage from the menu. It lists every roadmap with its size, and lets you download and remove ones you no longer need on that machine. Removing a local copy does not touch your account.

A roadmap looks out of date on another device

Open it while online and let the header reach Synced. If it still looks wrong, do not edit both copies: download the good one, then tell us. Once two versions diverge, the download is what saves you.

The app looks stale after an update

Reload with Ctrl+Shift+R (Cmd+Shift+R on a Mac) to bypass the browser cache. The version number at the bottom of the roadmap menu says what you are running.

A payment failed

Stripe retries and emails you. Update the card from that email or from Plan & billing. Nothing is deleted while a payment is sorted out.

Connecting your other tools

This part is for whoever sets things up, and it is at the bottom on purpose: nobody needs it to use RoadSnap. Each connection belongs to the workspace, not the person who made it, so it survives their leaving.

Jira

Importing a backlog and keeping status current is on Pro. Pushing changes back to Jira is on Team.

1. In RoadSnap, as an owner of the workspace: Settings → Jira, then Connect Jira. The Jira section appears from Pro upwards.
2. Atlassian asks you to authorise the connection and choose a site. On Pro the consent screen lists read access to issues. It also lists permission to report the assignees we hold back to Atlassian (see Who an issue is assigned to below). On Team it also lists write access to issues and to Jira Software’s backlog order. Pushing changes back and ranking are Team features.
3. You land back in RoadSnap with the site name and who connected it.

Atlassian shows a banner saying the app has not been reviewed by Atlassian. That is accurate: we have not started Marketplace review, and it is not a security finding.

Linking without importing. If the work is already on your roadmap, you need not import it and have everything twice. Open the item, find the Jira section in its panel, and type the issue key — ABC-123. RoadSnap checks the issue exists before linking; unlinking later keeps the values it brought over.

Importing. For work that is only in Jira. Select the node the issues should arrive under, or select nothing and they arrive as a new top-level branch. Pick a project from the list and RoadSnap writes the query for you. Edit it to narrow further, or choose Everything I can see and write your own. The preview says how many issues matched, and how many are already here, before anything is imported.

What arrives. The hierarchy survives. RoadSnap follows each issue’s parent, so epic → story → sub-task lands nested, and so do extra levels above the epic. Status is mapped from Jira’s own categories. Blocked, In review and statuses meaning abandoned are recognised by name, so they do not collapse into “in progress” or “done”.

Who an issue is assigned to. Since 10 September 2026 a sync brings the assignee across, and Jira owns the Assignee column for linked items. The roadmap keeps the Atlassian account id; the name is looked up from a table RoadSnap holds for the workspace. That table is kept current against Atlassian, and an entry goes when they tell us an account closed. A blank name means the account is gone or the sync has not run since it was assigned.

Ranking Jira’s backlog. On Team, a switch in the Jira dialog makes the order of linked items here Jira’s backlog order there. It runs once a night and when you push by hand, and needs the Jira Software permission. If the connection predates that permission, reconnect Jira once to allow it; your nightly-push settings survive.

Pushing changes back (Team). RoadSnap shows which issues would change and to what, and you confirm before anything is sent. Jira does not let a status be set directly; each issue has its own allowed transitions. So changes go one issue at a time, and some can succeed while others fail. You get a result per issue, not one all-or-nothing answer.

Or let it keep itself current. Tick Keep Jira up to date automatically and the same changes go across once a night, so nobody has to remember. It is off until you turn it on, per workspace. It never sends titles: rewriting the summary your engineers read is always a deliberate act. Anything a Jira workflow refuses shows as a problem on this screen rather than vanishing.

And it tells you it ran. Under the tick box, RoadSnap says when the nightly push last went out, how many issues were updated, and how many Jira refused. Before the first one it says so. A job that succeeds in silence looks the same as one that never ran. Automatic only helps if you can see that something else remembered.

Which way a column travels is decided by who owns it. A column Jira owns flows in and is read-only here. A column RoadSnap owns is yours to edit and is what gets pushed back. To change which, open the column heading and choose Let RoadSnap own this field. The Jira panel states which columns go which way.

Disconnecting. We delete our copy of the tokens at once. The authorisation itself belongs to the Atlassian account that granted it, so we cannot revoke it for you. The dialog says where in your Atlassian account settings to do that.

Slack

On Team. A weekly digest posted where the team already talks.

1. Settings → Integrations → Slack…, then Connect Slack.
2. Slack asks which workspace and which channel to post in. Pick the channel; that choice is the whole permission.
3. Back in RoadSnap, choose the day the digest goes out, and send yourself a test message.
4. Then use Preview this week’s digest to post the real thing now rather than waiting for the day. If there is nothing worth reporting it says so instead of posting an empty one.

RoadSnap can post to that one channel and nothing else. It cannot read messages, see who is in the workspace, or post elsewhere.

The digest names, per roadmap, what finished, what is blocked and what is merely quiet. A week with no news is skipped rather than sent: a digest that says nothing every Monday is one people learn to ignore.

Disconnecting deletes the webhook, so posting stops at once. Nothing already posted is removed, and the app stays installed in Slack until somebody removes it there.

The API

On Team. Read-only access, so a script can pull your roadmaps as JSON into a warehouse, a spreadsheet or a status report.

1. Settings → Integrations → API tokens…, then create one. Only an owner of the workspace can create or revoke a token. A credential the workspace could not withdraw should not be one an editor can mint.
2. The token is shown once and never again. We keep only a hash, so we cannot show or recover it later. Copy it then; if you lose it, withdraw it and make another.
3. Send it as Authorization: Bearer rs_live_…

Every endpoint is a GET under https://roadsnap.app/api/v1, rate-limited to 60 requests a minute per token. A token reaches only the workspace it was made in. The full reference, with the shape of a node and the error codes, is at roadsnap.app/api.html.

Withdrawing a token stops it at once. There is no write API, deliberately: a token that leaks can read a plan, not rewrite one.

Single sign-on

On the Team plan you can sign in through your own identity provider. Okta, Entra ID, Google Workspace, JumpCloud, or anything else that speaks SAML 2.0 will do. It is included, and we do not intend to charge extra for it. An SSO surcharge is a tax on being careful, and the most resented practice in this market.

What it changes

• Anyone with an address at an enrolled domain is sent to your provider instead of being emailed a code. No second button to find: they type their address and it happens.
• Because that becomes the only way in, disabling someone at your provider disables them here too. That is usually the whole point.
• People who already had a RoadSnap account at that domain keep everything. Their workspaces and roadmaps move to the new sign-in the first time they use it, and the app says so.

Setting it up

It goes through a person rather than a settings page, because one step cannot be automated responsibly. We must confirm you control the domain before a provider may vouch for everybody with an address at it. Write to support@roadsnap.app with two things ready:

• Your provider’s SAML metadata URL (or the metadata XML file).
• The email domains you want enrolled — acme.com, and any others your people use.

We send you what your provider needs, add the connection, and test it with you before it goes live for anyone else. It is usually done the same day.

Once it is on, Settings → Integrations → Single sign-on… lists every enrolled domain. It shows whether each is required or still allows email codes, and when it was added.

Things worth knowing before you ask

Privacy and security

What we can see when you write to us. We look you up by the address you sign in with, and the console records who looked and why before it shows anything. What it shows is metadata: when the account was made and last signed in, and which workspaces you are in. It also shows how many roadmaps and items each holds, and the plan. Never a roadmap’s name, an item, a note or a field value. The console’s database role has no permission to read plans, so nobody here can. To see one, we would need you to send it.

• We do not sell your data, and no advertising or session-replay trackers come near your plans.
• Sign-in is passwordless, sessions are hardened, and accounts are isolated at the database level. The detail is on the Security page.
• Data is hosted in Eastern Canada.
• Found a vulnerability? security@roadsnap.app. We will thank you properly.
• The full picture is in the Privacy Policy and the Terms.