Resolve
Working through the queue
Each case explains why it was found, who is involved, and what Kanri proposes to change. Cases are grouped in this order: school contact details and test data, possible duplicates, old contact notes, shared contact details, then Aquila gaps. Resolve earlier cases first because later cases may become clearer after profile details are cleaned up.
Read the action at the start of each step before applying it. It names the affected profiles and shows the exact email, phone or note changes, including old and new values when replacing something. Profile identifiers beside names help distinguish people with identical names. New profiles are identified by their name and the step that creates them. The rule badge, safety label and explanation underneath describe why the action was suggested, not a separate action.
Merge steps say which profile is kept, which is removed, what happens to sign-in accounts, and how history and contact links transfer. They also explain how missing details are filled and permissions are combined. When duplicate contact links combine, management or communications can remain enabled if either link allowed them. Linking a contact without merging does not change an existing link’s relationship or permissions.
Note steps show the title and text being added or replaced. A rename shows the note’s identifier and old and new titles without changing its text. A step saying No automatic change requires an answer or manual review rather than silently changing a profile.
Merging duplicate profiles can leave an email address or phone number shared with another person. Kanri does not block that merge or discard the value. It creates a separate Shared case for you to review next.
For each case you can:

Search terms: