Users and Authentication

Prove the data before polishing the interface.

Begin with the smallest record set that can demonstrate the intended result. Confirm the collection and property types, remove optional filters or conditions, and display one plain value from the current record. Once that basic path works, restore one rule at a time. The first rule that changes the expected result identifies the layer worth investigating.

Keep query logic, component visibility, and actions separate while debugging. A query decides which records are available. Visibility decides whether one interface element appears. An action changes data or navigation state. Treating those as different responsibilities makes it easier to explain both the successful path and the empty, denied, or missing-data states.

The resources below label their evidence and limitations individually. Use the reviewed date to judge freshness, follow current official sources for product behavior, and treat dated forum reports as examples of builder experience rather than guarantees. Finish with the testing checklist on the relevant page, including at least one record that should pass and one that should fail.