Skip to main content
Skip to content

Address health

The Address Health page lists the email addresses in your directory that need a decision: people Owlie can't reach, addresses several identities share, sign-in emails nobody has verified, and sign-in emails still held by former employees. Open it from Admin > Directory > Address Health. You need the identity.read permission to see it.

Each report is a tab. Every row links to the identity's Attributes tab, where you make the fix; the page itself changes nothing. Sign-in email and email explains the two kinds of address these reports refer to.

Unreachable​

Unreachable lists active people that no work notification can reach. Each has no email, isn't allowed to sign in to Owlie (so they have no in-app inbox), and has no linked Slack account. If one of them is given a task, such as an approval, they never hear about it, and Owlie raises an unreachable-recipient alert.

Give each person at least one route:

  • an email, supplied by the source that should own it or entered on the Attributes tab;
  • a linked Slack account; or
  • sign-in access, which gives them the in-app inbox.

Disabled people aren't listed. Owlie stops sending them work notifications on purpose, and a task sent to one raises an alert asking you to reassign it.

The report counts any linked Slack account as a route, even when your organization doesn't deliver notifications to Slack. It can therefore leave out someone whose only route is a Slack account Owlie doesn't send to. A task for that person still raises the alert.

Shared​

Shared lists every address that two or more identities carry as a sign-in email, email or secondary email. Each row shows the holders, the role the address plays for each (Sign-in email, Email or Secondary email) and each holder's lifecycle state.

Sharing a contact address is allowed. A ward, store or team mailbox can be several people's email, and each work notification opens with the name of the person it is for. Everyone who reads that mailbox sees those messages, so decide whether each shared address is intended.

A row with a Sign-in collision badge is listed first. One identity signs in with the address, and it is also the email or secondary email of another identity that isn't terminated. Owlie refuses to set up this state unless an administrator records an override, but a source can write the address onto another identity later, and the first person keeps signing in. Meanwhile the other identity's work notifications go to a mailbox that belongs to someone else. To resolve it:

  • If both identities are the same person, move the accounts to the identity that holds their access, then remove the other.
  • If they are different people, correct the address in the source that wrote it, or change the sign-in email.

Pending​

Pending lists sign-in emails that are set but not yet verified, on identities that aren't terminated. A pending sign-in email can't receive sign-in links or password resets. The Status column says why it is pending:

  • Invitation not yet accepted: the person has never signed in. Ask them to open their invitation or verification link.
  • Address change awaiting verification: someone changed the address and nobody has opened the link sent to the new one yet.

From the person's Sign-in block, select Resend verification to send a new link, or Change to correct a mistyped address.

Held​

Held lists sign-in emails still set on terminated identities. A held address can't become anyone else's sign-in email, and it stays with the leaver so that a returning person can sign in again once rehired. When the mail system reissues the address to someone new, release it from the leaver first; see Reusing a sign-in email. Otherwise you can leave it held.