A user record, a group record and a membership relationship are separate parts of identity administration. Creating a person and a named group doesn't put that person in the group. Keep that distinction visible in an access handoff, especially when a reviewer is approved for a limited task.
These original tasks create fictional identity metadata under a tenancy OCID. Their example.test addresses are reserved examples, not real recipients. The browser doesn't create authentication factors, issue credentials or add memberships. It checks the requested local names and fields. Production work needs the actual supported identity setup, membership and policy relationships reviewed before anyone claims that a caller has the intended permission.
Separate identity records from membership and authentication.