Adalo buying guide: a repair ticket filter is not a permission
Use a fictional repair ticket prototype to test lists, detail screens and data access with separate accounts.
Adalo is worth trying if you need a repair ticket prototype where each requester sees their own tickets. Do not stop when the “My tickets” screen looks right. Filtering out someone else’s record and preventing access to it are different jobs.
One collection, two checks
Adalo’s filtering documentation explains that filters determine which records a component displays. Its collection permissions documentation distinguishes hiding interface content from restricting data access. Create a fictional ticket collection with ID, status, creator and sample description. Build a list and a detail screen, then set display rules and collection permissions separately. Keep real addresses, contacts and photos out of the pilot.
Repeat with another account
Have test accounts A and B file one ticket each and use a third with none to check the empty state. Open each account’s own ticket from the list, then have A try B’s example detail entry in the test environment to confirm the disallowed record is not disclosed. Check that list and detail agree after a status update. Record what permissions actually block versus what the interface merely hides. This is a proposed acceptance check, not a hands-on result.
Make the call
If all you need is a workflow demonstration, fake data and a clear list can validate the interaction. If you intend to use real tickets, first require evidence that collection permissions cover every actual access route. Hidden interface elements and a single demo are not enough.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:help.adalo.com