How does Appsmith turn existing orders into a staff screen?

Use a table to display records and a button for an approved action. A query is the request Appsmith makes to a connected system, such as your app’s database.

Imagine an order queue with labels and follow-up status. A read request can show those two fields. An update should change just the allowed status of one order. If your app checks permissions or records who changed an order, send the update through that existing service so its rules still apply.

Limit what the data connection can do. A screen that only shows order status can use a connection with read access to the needed fields. The connection needs no access to card details or message sending.

Does the Viewer role make an app read-only?

The default App Viewer can use the app and run its queries. Check who is allowed to run the query that changes a record as well as who can see the button.

Appsmith documents custom roles on Business and Enterprise, including restricting which roles can execute a query. A permission on the underlying connection or app service should also enforce the job’s limits. Verify the permitted and denied outcomes with separate test users and isolated data before using real records.

Keep a staff queue private. Appsmith’s public embed can open without an Appsmith login. Its documentation lists private embedding for Enterprise. If you need to share something with customers, start with a separate customer screen and decide which information each person should see.

How would you try one permitted status change?

Use a paper version of the queue. Give the reader a lookup and the supervisor one approved change.

Draw the two accounts
Write Reader and Supervisor beside fake orders P-14 and P-15. Both can see Needs follow-up. Only the supervisor can change that status.
Write what the button asks for
Write “Set P-14 to Ready to contact.” Decide which account can make that request. Record the expected denial when Reader asks for the same change, even if the button was hidden.
Read the orders again
Imagine the supervisor completes the request. P-14 should show the new status. P-15 should be unchanged. Nothing should send an email. This exercise uses no accounts, app or database.

What do Cloud and self-hosting charge for?

Appsmith’s public plan table lists Free Cloud for up to five users and paid Business pricing per user per month. The Business count includes people added to the instance at any point in the billing cycle.

A person who builds or edits an app counts as a standard user. Appsmith also offers an open-source Community Edition that you host. Your team is responsible for the machine or hosting service, updates and recovery. Check how many teammates need an account and which features your installation needs before choosing.

What can you copy to another Appsmith instance?

Export the application as JSON and import it into another Appsmith workspace or instance. Reconnect the data sources there. The export leaves out the values used to connect them.

A page can also export selected elements, such as a widget or query, for reuse. Use the whole-application export if you want to move the whole screen. After importing, the two copies change separately. Back up the actual order records where they are stored and check that the new copy can read and update only what you expect.