Which records should someone be allowed to change?
Use roles to define what each team member can do and a data scope to define which records that action can reach. In a request queue, the same person might read all incoming requests but update only the ones assigned to them. Check the data scope on the update action, even if a menu already hides other records.
Which edition is this workflow for?
This is the NocoBase 2 no-code workflow. Moving an existing app to NocoBase 3 means rebuilding it there and then importing its business data. The NocoBase 2 Community plan is free to self-host and lists unlimited applications and users. Paid editions add selected plugins such as external database connections. Check the exact feature list and budget for running and maintaining your own installation.
Will you be able to recover the app and its records?
The Backups Manager plugin documents a backup of the NocoBase database. It can include files uploaded to the server’s local storage if you enable that option. Check whether your edition includes the plugin. Arrange separate recovery for files stored elsewhere or for an outside database. Keep a record of the version, plugins and role setup you will need in a restored copy.
Can the second reviewer edit the first reviewer’s request?
Draw two fictional requests assigned to different people. Both reviewers should be able to see the queue, while each can change only their assigned record.
- Mark the data scopeGive the Update action the assigned-record rule. Do not use the visible list alone to represent write access.
- Check the two outcomesReviewer A changes their own request, then attempts the same change on reviewer B’s request in the sketch. Write Saved beside the first and Denied beside the second.