Skip to main content
These admin routes run the Console’s own identity and settings operations for an API key. An External App is refused with 403, even when it holds the permission.
  • Unmapped sign-in attempts: list them with workforce:manage, pending first, optionally with the dismissed ones. Each attempt answers its _id, its claim type, the inbound external id, display name and email, and, for Slack, the workspace and channel it came from.
  • Dismiss an attempt by that _id with workforce:manage, with a reason and an optional dismissal period in days (0 keeps it dismissed). The audit event names who dismissed it: a platform API key is recorded as the key, and a Personal key as its owner.
  • A person’s profile and avatar: read a profile with GET /api/v3/identity-profile and clear an avatar with POST /api/v3/identity-avatar/clear. These need a Personal key, which acts as its owner: with no userId (or the owner’s own), it reads or changes the owner’s own record and needs no permission. Another person’s userId needs workforce:manage; without it the route answers 404, whether or not that person exists. Any other key is refused with 403 and personRequired: true. Setting an avatar is not on the API yet: it takes an image uploaded through the Console.
Linking an attempt to a person is not on these routes: the Console’s link does not apply the person-reach rule. The workforce identity routes, POST /api/v3/persons/{personId}/email-claims and POST /api/v3/persons/{personId}/identities, apply it. Orphan identity repair is not on the API.