Why rovo agent is addressing me as my Jira admin?

[camila_medrano]

When we connected Rovo to Slack, to have a especific Rovo Agent respond to questions in a Channel in Slack, the Rovo agent was responding to me as if I was the admin. If I asked to am I, it would respond to me as I was the Jira admin. How can I fix this? so it addresses each person by who they truly are. 

[Martin Runge]

Hi Camila,

Welcome to the Atlassian community.

We resolved this once by officially adding the Rovo app to the channel using /invite @atlassian Rovo, which allowed it to access participant metadata.

Hope this helps.

[camila_medrano]

Thanks for your answer! I still have the same issue

[camila_medrano]

In this step: do you know why this is not Oauth authentication like other slack apps (jira, confluence..) As the bot can create tickets and confluence page, we do not want it to create those using a generic bot account

[Dr Valeri Colon _Connect Centric_]

@camila_medrano welcome to the community. Inviting the Rovo app can help, but this is usually about identity context mapping between Slack and Atlassian. If users aren’t properly matched (email/domain mismatch, guest users, or missing permissions), Rovo may default to the admin context. Make sure Slack users are correctly linked to Atlassian accounts (same email/domain) and that Rovo has access to user metadata—otherwise it can misidentify users.

[camila_medrano]

Thanks for your answer! Im still having an issue: specifically here: 

In this step: do you know why this is not Oauth authentication like other slack apps (jira, confluence..) As the bot can create tickets and confluence page, we do not want it to create those using a generic bot account