Yodeck’s October release adds a prebuilt Salesforce sales dashboard app and separates permissions for media files from permissions for app instances. For enterprise signage teams, the useful change is the combination: less work to put business data on a screen, with a clearer way to decide who can alter the application supplying it.
The release notes were first posted on Oct 1, 2026 and show an update on Oct 6, 2026. This is a catch up assessment of the documented capabilities, not a claim that Yodeck launched them today. Google Reviews and Sign In App integrations also appear in the release, alongside limited App Gallery creation through the API. The operating question is what has to be controlled once screens become a shared view into business systems.
A scoreboard is different from a dashboard replica
The new Salesforce Sales Dashboards app builds its own views from Opportunity records. Its guide lists Performance, Pipeline Health, Leaderboard and Efficiency, with fixed metrics rather than a flexible dashboard designer. That makes it a different assignment from reproducing a team’s existing analytical workspace.
Yodeck’s older Salesforce app remains the route for supported dashboards already built in Salesforce Lightning. Its documentation says it reconstructs charts from data rather than displaying the original dashboard interface, and excludes interaction such as drilling into details and filtering. Integrators should establish which product the brief actually requires before demonstrating either one.
For the new app, the critical prerequisite is source access. Yodeck’s setup guide specifies a client credentials connection and a Run As user with View All access to Opportunity. It warns that insufficient access can produce figures covering only that user’s deals. A successful connection therefore does not, by itself, establish that the displayed totals represent the intended population.
That distinction changes acceptance testing. Compare a selected screen metric with the corresponding source population before treating the screen as a scoreboard for the whole organization. Then establish who is meant to see it. A shared display’s audience is a separate decision from the records an integration account can retrieve; accurate access at one layer does not answer the other.
Two permission systems, two different jobs
The release places separate Media and Apps controls in Custom Roles on Enterprise and Enterprise Plus plans. Existing roles are retained. The Salesforce sales app is listed for Premium, Enterprise and Enterprise Plus. Buyers should therefore distinguish availability of the application from availability of the more granular custom role controls.
Yodeck’s current Custom Roles documentation separates ordinary files, such as images, video and documents, from app instances. This allows a content team to maintain media without managing the live data applications. It also records an exception: granting at least View access to Apps automatically grants View access to Media. The boundaries are useful, but they are not completely symmetrical.
The release notes describe view, create, edit and delete access; the role guide presents View, Change and Delete. Those descriptions support separate resource controls, but the labels are not identical. An integrator should verify the effective permissions in the customer’s account rather than promise a particular control layout from the release wording alone.
Salesforce controls a different boundary. Its developer guidance recommends a dedicated integration user and permission set, scoped to the data and operations the application needs. That is independent context for reviewing the source connection, not evidence that Yodeck has achieved a particular security outcome. Where the sales app requires broad Opportunity visibility, the customer needs to assess whether that scope fits the intended use.
Less configuration work does not remove operating ownership
The new app can be useful precisely because its view is constrained. A sales team wanting a common scoreboard may prefer fixed, readable metrics to another custom reporting project. The counterweight is that a fixed view may not answer a more specific management question; that is a fit issue rather than evidence of a defective implementation.
A practical pilot should establish three things together: the source records behind the chosen metric, the people permitted to change its app instance, and the audience permitted to see the resulting screen. Those are acceptance questions derived from the documented access model. They are not claims that an existing customer has suffered an exposure or incorrect report.
The next useful proof is a customer deployment showing that its displayed figures reconcile with its chosen Salesforce population and that content contributors cannot alter the live data app beyond their assigned role. Yodeck’s update provides more tools for that division of responsibility. Whether the division works depends on configuration and verification, not the number of integrations in the gallery.