I want to enable our QA to test the app before release. The QA team are regular users (not editors). When I provide them with the staging URL it automatically redirects them to the production URL
Hello @eran and welcome to our community!
In your case, you might want to reconsider the roles of your QA team members. The regular users will not have access to the staging environment. You can create a custom role for your QA team: Custom roles | UI Bakery Docs
Hope this helps! If further questions arise, please let me know.
Custom roles are available only on business plan. The overall cost is too high for such a basic feature. I wonder if all your basic plan users test their app on production?
Custom roles are also available with the standard plan. I recently had an exchange with the support team:
Starting from Standard, you can choose how many user and dev seats you need. Admins and editors count as Dev seats, Users — as User seats. There’s no limit (as on the Free plan), but every seat will be charged separately.
For example, if you need 1 admin, 1 editor, and 6 users, your subscription will look like this:
6 x User seats — 4 EUR/month each;
2 x Dev seats — 9 EUR/month each;
So you could add a user with a custom role that can only access staging and production for the QA team (or several), you just need to ask for more seats.
That’s… interesting, never saw that window, even though I am on the standard plan. Does this appear when creating the role?
I have no issues creating the role, the only thing I can’t do, is assign it to a user:
And this just means that we need to request more “Workspace users” seats.
This happens when pressing “Add Custom Role”
I see… you are also on the standard plan, right?
To be honest, this reaches out of my expertise, so I hope @Kate can help you further.
Thank you for the explanation, @Max
@eran,
On a Standard plan, you can add standard role seats (e.g. you can have 3 dev seats and 10 user seats). Custom roles are indeed available on a Business plan, so the warning you are seeing is legit.
I’m afraid, we are not aware of how our Standard plan users handle testing, but if possible, you could grant a tester an editor role. We could recommend managing access to certain data by using {{user.email}} or {{user.role}} variables. Loading user specific data with {{user.email}} variable | UI Bakery Docs
@Max the difference you noticed is happening because we introduced the regular subscription for the self-hosted versions later, so the setup of the seats is a little different.
Hope this helps!
1 Like
It helps me understand but really helping 
I will give him Editor role but this is not a good practice, mostly as this does not simulate a real user
2 Likes
Technically, to simulate a real user experience, you could make the app public in app settings. This would be in production and not staging, but you could just make a temporary copy of the app to let the QA team test on there, this would also allow you to make changes in parallel.
If this “Embed URL” isn’t written anywhere it’s very unlikely someone would find this page. But then again, I’m not sure how the on-premise and cloud version differ from another. When I go on cloud.uibakery.io and try the same it says
But on my standard plan on-premise it seems to work fine… I really don’t know.