Review candidates

• Compare project code, name, status, and location.
• Treat displayed confidence as a clue, never as confirmation.
• Verify participants, active organization, and clues in the thread.
• If no candidate fits, use manual search by code, name, owner, or location.

Confirm, create, or remove

1. 01

   Select Use project only after verification.

2. 02

   If the project does not exist and your role allows it, create it with confirmed essential properties.

3. 03

   Wait for the success message and reload project context.

4. 04

   If the affiliation is wrong, use Remove project affiliation and confirm the no-project state.

Practical guidance

Compare detected candidates with the email’s actual mandate before selecting one. A confidence percentage ranks a proposed match but does not authorize affiliation. Once a project is confirmed, verify the displayed code again before using its participants, files or memory actions.

Advanced tips

If two projects share a client or similar title, use the exact code and relevant location to resolve the ambiguity. Correct a wrong affiliation before memorizing the email; do not treat a high confidence score as stronger than confirmed project records.