Use a different default avatar for API-only users

[rachaelshaw]

• @noahtalerman: User requested this because API-only users currently appear identical to human users in the activity feed, making it hard to differentiate automation from manual actions.
  • @noahtalerman: In the interim, users can manually cross-reference API keys or user roles to determine if an action was automated.
  • @noahtalerman: Eventually, Fleet should introduce a visual indicator (such as a unique avatar or label) to distinguish API-only users in logs and the activity feed.

---

User stories

• Different default avatar for API-only users #27457

[noahtalerman]

Gong snippet: TODO

Problem

API-only users are unlikely to have a gravatar, and in the activity feed, query author, etc., they look the same as any other user that doesn't have an avatar set. It'd be nice to show when things come from an automation versus a human manually making changes.

(OKR: Small UX improvements)

What have you tried?

N/A

Potential solutions

Back-end: Migrate existing activities to include a new boolean like actor_api_only
Front-end: Update avatars to use a different default when user is API-only. Could be something like:

• </>
• the letters "API"
• Robot face

What is the expected workflow as a result of your proposal?

I'm scrolling through the audit log. I can easily spot which changes were made via an integration and which were made by human users.