Covers 1 to 4 October 2026
One home for your apps, clearer approvals and passwordless sign-in
SpringRoll now gives every member one place to find the apps they build and use, puts everything a reviewer needs on the approval itself, and signs everyone in with an email link or single sign-on. Sharing, data connections and build logs are easier to work with too, and you can now send us feedback without leaving SpringRoll.
One home for every app
Apps now brings every app together in one place, with three views: My apps, Available to me and All apps. You see only the apps your role allows. Each one shows its status in plain words, when it last updated successfully, and a warning when the latest update failed. Adding a new app takes just a name and a repository URL.
Why we built it: Finding an app should not depend on knowing which page it lives on. One home, with a status you can read at a glance, tells you whether an app is working before you open it, and makes registering the next app quick enough that nobody puts it off.
Approvals you can decide with the facts in front of you
Each request in Approvals now shows what it is for, the environment and release it covers, the data fields it asks for, who submitted it, when it expires and which checks are blocking it, with failing checks listed first. You decide on the request itself: approve in one click with an optional note, or reject or request changes with a reason the requester can read. Bulk approval from the list has been removed, and a request assigned to a named person stays with that person.
Why we built it: An approval is only as good as what the reviewer could see when they gave it. Deciding each request with its full context makes every decision one you can stand behind, and a written reason tells the requester exactly what to fix.
Passwordless sign-in and safer sessions
SpringRoll no longer uses passwords. You sign in with a one-time email link, valid for 15 minutes, or with your organization's single sign-on where it is set up. Sessions now end 12 hours after you sign in, and signing out signs you out of every open tab. Invitations work the same way: sign in with the invited email address, then choose Join workspace. There is nothing to set up. Next time you sign in, ask for an email link.
Why we built it: Passwords are the easiest credential to steal and the most tedious to look after. Email links and single sign-on remove them entirely, and a fixed session length means no browser stays signed in indefinitely.
Send feedback from wherever you work
Choose Feedback under Help to send us a bug report, an idea or anything else, or ask your coding agent to send it for you through its SpringRoll connection. Your feedback goes straight to the SpringRoll team. Inside your workspace it stays private: your feedback list shows only what you sent, and other members, including administrators, cannot see it.
Why we built it: The best ideas for SpringRoll come from the moment something gets in your way. Being able to tell us right there, from SpringRoll or from your coding agent, means we hear about it while it still matters.
App pages that lead with what matters
Every app now opens on an overview that answers the first questions people ask: is it working, who can open it, and what happens next. Open app and Copy app link sit at the top, next to the app's status and who can open it. While an update builds, or if it fails, the overview makes clear that your current version is still running. Each app is organized into five tabs: Overview, Deployments, Access, Data and Settings.
Why we built it: Whether you built the app or are about to share it, you should not have to read deployment details to learn whether it works. Keeping the working version separate from the latest attempt means a failed update never looks like a broken app.
Sharing that respects who can open each app
Copy app link now gives you a SpringRoll link for Production or for UAT (user acceptance testing). Whoever opens it signs in if they need to, lands back on the same app, and gets the version that is live in that environment, never a fallback build or a rejected or archived release. People without access see a clear explanation instead of an error. The access editor now asks one question, who can open this app, and switching an app to Everyone keeps the exclusions you already set.
Why we built it: A hosting address skips your access rules and can change when a new version ships. A SpringRoll link checks access every time it is opened, so sharing an app is safe by default, and widening access never quietly removes a restriction.
Data, formerly Connect: faster connections and precise requests
Adding a data connection now starts with just the source, a name and the required fields, and everything else waits under Connection options. SpringRoll creates names for you, keeps saved credentials unless you choose to replace them, and can save and test a connection in one step. SAP connections can use a technical user or a BTP OAuth client. When an app needs data, its managers can search for the exact fields they need, and data owners can grant the request, reject it with a reason, or add a note.
Why we built it: Connecting an app to real company data is where it becomes useful, and also where the most careful decisions are made. Less setup gets you there sooner, while the data owner still decides which fields each app may use, and saved credentials are never shown again.
Build logs that explain what went wrong
When SpringRoll cannot fetch an app's source from Git, the deployment log now shows the error that stopped it, with web addresses and access tokens removed. Long build output stays in order, and an unusually long line is replaced with a short notice instead of being cut off mid-message. We also fixed a Git ownership check that could stop managed builds before they started.
Why we built it: A failed build with an empty log is a dead end. Showing the real reason, safely, tells you what to fix the first time instead of the third.
Also improved
- Optional sections of the New app form stay closed until you need them, open by themselves when something needs fixing, and keep what you typed.
- App showcase is now the Public app page, an optional introduction to your app that previews exactly what will be published, and the Download card option has been removed.
- App Settings brings the name, data classification, details and build settings together in one form.
- Updating an app through the SpringRoll API no longer resets the settings you leave out, such as its visibility, data classification, tags and build settings.
- Long approval inboxes are split into pages, so older requests stay easy to reach.
- Open workspace on the SpringRoll home page takes you straight to your workspace, or asks which one you want if you belong to more than one.
- Accepting an invitation no longer creates an extra personal workspace.
- Hosting now shows just your deployment workflow, your public app page policy and your hosting status.
- The setup checklist stays in Getting started instead of appearing above every page.
- Analytics are sent after an action completes, so they never slow you down, and each app tab loads only the data it shows.
- On a deployment record, the assumptions behind SpringRoll's hosting recommendation now display correctly.
- The SpringRoll docs are now organized by task, from connecting your coding agent to sharing an app and requesting data, with the API and MCP reference at the end.