What do you connect before the first list works?
React-admin needs a data provider, the code that translates a list or edit action into a request to your API. Connect its sign-in checks to your authentication service as well. Start by loading one list of fictional records. You still need the API that owns the records and decides whether the person may read or change them.
Who should decide whether a staff member can edit?
The app can use access checks to decide which buttons or pages it shows. The API needs to enforce the same rule before it saves a change. Core React-admin is MIT-licensed. Optional Enterprise modules are separate, and your team runs the frontend and its backend services.
Does the Export button save everything?
The standard list exporter uses the data provider and can make a CSV. Its main fetch has a default limit of 1,000 records, which the developer can configure. Check the active filters, visible output fields and record count. Keep the project source and an independent copy of the underlying data.
Will a read-only reviewer get the same queue as the editor?
Sketch a fictional stock queue for a reviewer and an editor. They should both see the permitted list. Only the editor should be able to save a quantity.
- Draw the app and the APIPut the staff screen on one side and the service holding the records on the other. Show which request reads and which saves.
- Write two expected repliesA read from either allowed account returns the queue. A save from the reviewer should be denied by the service, even if a button is present.