ToolJet

Which version of a ToolJet queue does staff open?

A released ToolJet app keeps a stable link. Set the release to private so it requires the right workspace access.

Imagine a builder wants to add a status button while staff continue to use the current order list. ToolJet separates builder editing from the released app people open. Its access guide describes released access as the default for end users. An administrator can explicitly allow access to a preview environment where supported.

Hiding an app from the dashboard still leaves its URL accessible to permitted users. Use private sharing and the intended app permissions for a staff queue. A public app can open without a ToolJet account.

Where does an order update actually happen?

Connect the queue to the system that holds the orders. A query is the request the tool makes to that system. Check what requests staff can run before you give them the link.

Make the lookup read only and use a separate authorized action for changing status. If the order service normally checks who can update an order, keep that check in the service. Grant the connection only the access that action needs.

ToolJet documents separate permissions for who can configure a data source and who can build with it. Check those settings as well as the app’s audience. A staff member should be able to open the intended queue without receiving a connection credential.

How would you check one private release before adding staff?

Sketch a draft and a released queue on paper. Use fake orders and decide what each person should see.

1. 1
   Keep the release predictable

   Draw the current private release showing orders P-14 and P-15. Draw an unreleased change that adds a status button. The staff link should still show the released version.
2. 2
   Separate the users

   Give an authorized teammate the private link in your sketch. An outside visitor should have no access. A teammate with read-only permissions should be denied any request to change an order.
3. 3
   Check one allowed edit

   Imagine the supervisor later receives the released status button and can set only P-14 to Ready to contact after approval. Read both orders again to see which status changes. This is a paper check with no data connection, release or notification.

What does ToolJet count on its plans?

ToolJet lists paid prices per builder per month, with separate end-user allowances. Cloud Free lists two builders and up to 50 end users.

People who build the queue and people who use it have different jobs. Check the builder and end-user allowances and the app limit in your actual plan. If you self-host, your team operates the instance and pays for its infrastructure.

ToolJet documents a free Basic license for self-hosting. Its guide says the Basic limits apply starting with version 3.5.20-ee-lts and can archive excess users when an older installation upgrades. Check your version, license and active users before making that change.

Does exporting an app also save its order data?

ToolJet exports a selected app version or all versions as a JSON file. The option to export built-in table schemas copies their structure. Save the actual records separately.

A table schema describes how fields are laid out. An external database or API still holds the records behind its connection. For a practice import, choose a disposable workspace before importing. A bundled table schema can create tables there. Confirm the app can reach only test data and that email and other outgoing actions are disabled or use test destinations. Check this before importing and again before opening the app or running a query, since a query can run when the app opens. If you cannot confirm those settings, use the paper exercise. Once the checks pass, use a fictional order to verify the approved update. Keep any export containing sensitive configuration private.