Why does Chronicle show a specific user performing actions instead of Chronicle itself?

When Chronicle performs certain actions in your workspace — such as archiving a channel — it sometimes needs to act with administrator privileges. It does this through the Slack API, acting on behalf of whichever admin most recently installed the app. As a result, Slack shows that specific user as having performed the action, rather than showing Chronicle itself.

You can identify when Chronicle (rather than the user) performed an action, such as archiving a channel, by checking the message posted just beforehand — it details relevant information like the channel's last activity and members at the time.

You can't directly choose which user Chronicle performs actions on behalf of — this is determined by how Chronicle interacts with the Slack API. However, since Chronicle acts on behalf of whichever admin most recently installed the app, you can change this by having a different admin add Chronicle to Slack. That user will then be the one shown performing actions, until another admin installs the app.