Use UUIDs for identifiers that need no readable sequence
Random UUIDs can label records, example data or application objects without displaying a simple increasing number. Decide how the receiving system stores and compares them, including hyphens and capitalisation. An identifier should identify a record; access to that record still needs its own authorisation controls.
Example: prepare a small batch of test record IDs
Choose five UUIDs, generate the output and copy one line into each test record's identifier field. Run the generator again when you need fresh values rather than reusing a published example. Your production data store should still enforce its unique-key constraints and handle any rejected duplicate appropriately.
Keep identifier generation separate from access control
A value that is difficult to guess does not make the associated resource private. Do not rely on a UUID alone as proof that a visitor may read or modify a record. This workspace generates UUID v4 only; it does not create time-ordered UUID versions or derive deterministic values from a namespace.