Can the person working the queue change the app itself?

Budibase distinguishes people who build the workspace from people who use published apps. Give a staff member access to the app and check the app role that controls their screens and data. Verify what the person can do in the underlying table or connected data source too, especially if the team uses a shared connection.

What can make a Budibase Cloud bill grow?

Count creators, staff end users and monthly actions separately. Budibase’s Cloud FAQ counts a row update in Budibase DB or a SQL database as an action, along with qualifying automation work. The current Community option is self-managed. Your team supplies the hosting, maintenance and backups. Check license connectivity requirements if you choose a self-hosted deployment.

Does a workspace export keep the data and credentials?

You can export the latest edited or published version and choose whether to include rows from built-in tables. Turning off rows can still leave connection details and credentials in the file. The guide describes excluding secrets with environment variables and encrypting an export. Back up external data separately and review connections before opening an imported copy.

Can a staff member mark one request ready?

On paper, give a staff member a queue with one fictional request and let them change its status to Ready. Keep workspace editing with the builder.

Write two responsibilities
The staff member changes the request status. The builder changes how the queue works.
Check the saved action
The staff role should be able to save Ready on the assigned request. It should be unable to change the app or use a different screen to edit records outside its role.