Can someone use the queue without editing the whole base?
In Airtable a base holds the tables and an interface is a screen built from them. Sharing an interface separately from the base requires a paid plan. For a private staff interface, the person needs a verified Airtable account. A user with separate base access may still be able to open more records there. Review both kinds of access.
Why might someone see a status field but be unable to change it?
Editing depends on the collaborator’s permissions and what the interface allows. Put an editable status field on the staff screen only if the person is allowed to change it. Choose a view-only role for someone who only needs to inspect progress, and check the billable role rules for your plan before inviting people.
Does a CSV capture the entire Airtable workflow?
Download a view when you need a table of those records. Filters and hidden fields can affect what the view contains. Keep a separate inventory of interface settings, linked records and automations you need to rebuild. Check how to move attachments rather than assuming they are inside a CSV.
Which rows and fields should the dispatcher see?
Draw a fictional queue with two shipments. Make a screen for changing one shipment’s status and a read-only screen for a manager.
- Compare the two invitationsWrite down which person can edit and which can view. Note whether either needs access to the underlying base.
- Check the moveCircle the columns you expect in a filtered CSV. List the staff screen and its permissions separately.