Select an existing Person Collaborator that is not already represented by an authorization actor - RodrigoMattosoSilveira/EnterpriseRemoteSystems GitHub Wiki

For manual testing, the safest way to guarantee that you have a Collaborator with no Authorization Actor is to create one specifically for this test:

1. Go to People and create a new, complete Person. Give the Person an unmistakable nickname, for example AuthAccountTest01.
2. Go to Collaborators → Create Collaborator and create an active Collaborator Journey for that Person.
3. Go to Authorization at /admin/authorization.
4. In Create Actor, use the Collaborator search field and type AuthAccountTest01.
5. The Collaborator should appear under Matching collaborators for actor creation. Select it and create the Authorization Actor.
6. Grant that actor, for example, EXPENSE_OPERATOR @ default.
7. Do not create an Authentication Account yet.

At that point you have exactly the prerequisite for Section 10:

Person
  ↓
Active Collaborator
  ↓
Active Authorization Actor
  ↓
EXPENSE_OPERATOR @ default
  ↓
No Authentication Account

If you prefer to reuse an existing Collaborator, try searching their nickname in the Create Actor search. If they are offered as a matching candidate, they are usable for actor creation; if they already have an actor, they should not be offered by that candidate flow.

For this manual test, though, I recommend creating the dedicated AuthAccountTest01 Person/Collaborator. It eliminates uncertainty about whether an existing record already has an Actor or Authentication Account.