Issue Summary

When interacting with the Atlassian Rovo app in Slack channels, performing actions are expected to run using the requesting user’s Atlassian account. Currently, this behavior is inconsistent: in some cases, the Rovo app instead uses the Slack bot’s Atlassian account credentials to perform actions and integrate with Rovo. As a result, Rovo’s responses sometimes show the bot account as the actor instead of the end user.

Steps to Reproduce

1. In a Slack channel, as a user, interact with Rovo to edit a page (for example, append)

Expected Results

• Atlassian Rovo app uses the user's permission interacting with it to perform the action

Actual Results

• The Atlassian Rovo app uses the bot used for integration to perform the action

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available