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.
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
Hello @camila_medrano
This happens because Rovo uses a centralized bot account model in shared Slack channels to prevent data leaks. If your personal admin account was used during setup, Rovo will execute channel actions with your elevated privileges. Have your admin re-run the Slack onboarding using a dedicated, low-privilege service account. 😉
For any workflows that require strict user attribution, it's best to have users interact with Rovo in private DMs instead.
Atlassian Rovo for Slack: AI-Powered Search & Assistance in Your Workspace
Best,
Arkadiusz🤠
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.