# Custom Dashboards errors,

**URL:** <https://forum.wixstudio.com/t/custom-dashboards-errors/79767>\
**Category:** Ask the community\
**Tags:** cms, code, question\
**Created:** [September 15, 2026, 8:53pm UTC](https://forum.wixstudio.com/t/custom-dashboards-errors/79767 "2026-09-15T20:53:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Hunte](https://sea1.discourse-cdn.com/wix/user_avatar/forum.wixstudio.com/mark_hunte/32/100172_2.png) [@Mark\_Hunte](https://forum.wixstudio.com/u/Mark_Hunte)\
**Post date:** [September 15, 2026, 8:53pm UTC](https://forum.wixstudio.com/t/custom-dashboards-errors/79767/1 "2026-09-15T20:53:58Z")

</div>

**We have had some Custom dashboard working for ages with no changes.**

One uses upload file ( image) which it will save it to a cms. but now we just get ‘unexpected error’ I did try and change the code to use the newer API but same thing.

Another dashboard gives another error when trying to write to a cms.

‘WDE0027: The current user does not have permissions to update on the All\_Tickers collection." to…’

I also have a backup from a few months ago, which does exactly the same.

It is like the server is not registering my or other authorised uses permissions correctly any more.

On a copy backup site -I just set two of the cms permissions for the that one of the dashboards use that was getting the error WDE0027:… to

 ![Screenshot 2026-09-15 at 22.02.13](https://us1.discourse-cdn.com/wix/original/3X/b/a/bae53097e4db6c541cb607459006a74c53198bd4.png)

and it works.

set them to

 ![Screenshot 2026-09-15 at 22.09.44](https://us1.discourse-cdn.com/wix/original/3X/4/5/454c4d2ecb5e26c627df617cc51af551105e88d1.png)

and it does not work

This seems to suggest it is only working on everyone??

---

<div class="post-metadata">

**Author:** ![Webhil](https://sea1.discourse-cdn.com/wix/user_avatar/forum.wixstudio.com/webhil/32/122559_2.png) [@Webhil](https://forum.wixstudio.com/u/Webhil)\
**Post date:** [September 16, 2026, 3:48am UTC](https://forum.wixstudio.com/t/custom-dashboards-errors/79767/2 "2026-09-16T03:48:18Z")

</div>

Your permissions test is the diagnosis. If it only works when the collection  
grants the action to Everyone, then the call is arriving with visitor  
authorisation — not yours. The server isn’t failing to register your  
permissions. It isn’t seeing you at all.

That matters because of how the two permission systems line up. In the  
dashboard you’re a Wix user, which is a different identity from the roles the  
CMS permission table is written in — those are member-side roles. Frontend  
dashboard code calling wixData directly depends on that translation happening,  
and in your case it isn’t. Everyone is the only row that doesn’t require an  
identity, which is exactly why it’s the only row that works.

Move the write into a backend web module and the problem disappears, because  
suppressAuth bypasses collection permission checks entirely. Identity  
resolution stops mattering.

backend/tickers.web.js

import { Permissions, webMethod } from ‘wix-web-module’;  
import wixData from ‘wix-data’;

export const updateTicker = webMethod(  
Permissions.Admin,  
async (item) =\> {  
return wixData.update(‘All\_Tickers’, item, { suppressAuth: true });  
}  
);

Then from the dashboard page:

import { updateTicker } from ‘backend/tickers.web.js’;  
await updateTicker(myItem);

Note the .web.js extension — suppressAuth only works in backend code, so this  
has to be a real backend module, not a helper file in page code.

Two things worth doing while you’re in there.

Put your collection permissions back. If you’ve currently got All\_Tickers set  
to let Everyone update just to make the dashboard work, that’s a public write  
endpoint on your live site right now. Once the write goes through the backend  
module you can set it back to admin-only and it’ll still work.

Keep Permissions.Admin on the web method rather than loosening it. If the web  
method itself rejects your call from the dashboard, don’t switch it to  
Permissions.Anyone to get past that — that would make the write callable by  
anyone, and Wix’s own docs note that dashboard page code is publicly visible.  
A rejection there is actually useful: it’s clean proof the identity isn’t  
resolving as admin, which is the thing to put in a support ticket.

On the ticket — your point about the months-old backup behaving identically is  
the strongest evidence you have, so lead with it. Unchanged code, unchanged  
backup, changed behaviour, and a permission matrix where only Everyone works.  
That’s a platform-side change, and it’s specific enough to be actionable. But  
don’t wait on it; the backend module makes you immune either way.

Last thing: treat the upload error separately for now. “Unexpected error” is  
too vague to diagnose, but if that dashboard also writes to a collection it’s  
plausibly the same root cause wearing a different message. Fix this one, then  
retest the upload before chasing it.

---

<div class="post-metadata">

**Author:** ![Mark\_Hunte](https://sea1.discourse-cdn.com/wix/user_avatar/forum.wixstudio.com/mark_hunte/32/100172_2.png) [@Mark\_Hunte](https://forum.wixstudio.com/u/Mark_Hunte)\
**Post date:** [September 17, 2026, 9:58pm UTC](https://forum.wixstudio.com/t/custom-dashboards-errors/79767/3 "2026-09-17T21:58:21Z")

</div>

FYI,

I will probably adjust my code as @Webhil suggested. But I did just check if there issue was still there. And it now seems to be working as expected. Hopefully its now fully fixed