I know of "Automation for Jira" account, but I see an "Automation Bot" account which is visible in User Pickers and its an option when selecting in a permission scheme or such, but it's not a visible user in the admin panel... Is this a new system account? Is it Automation and/or Rovo related? If so, do I need to ensure it has access to my spaces via Permission scheme?
Hello @Rosa Fossi
Check Atlassian Administration → Apps/Products → your site → Jira Service Management → Portal-only customers for an account like automation-bot@atlassian-demo.id or automation-bot@atlassian-demo.invalid.
I think it's just a demo customer and is unrelated to Automation or Rovo.
For Automation, is still used Automation for Jira.
Best,
Arek 🤠
Marking as accepted answer, but with a caveat... the path is different in some of the newer navigation cloud instances
Administration > Apps > Sites > Select Site
[new screen opens]
Service Collection > Portal-Only customers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Rosa Fossi
Yes, Automation Bot is an official Atlassian system account used to execute background tasks for Automation for Jira as well as Atlassian Intelligence / Rovo automation steps.
It is a managed Atlassian system/service actor (not a billable user account), so it does not appear in user management under admin.atlassian.com. However, Jira's index surfaces it in user pickers, role assignments, and permission schemes so it can be selected as a rule actor or granted explicit project permissions.
In standard Atlassian projects, system bots inherit access automatically through the atlassian-addons-project-access project role.
Hope this answers your question. 🙂
Thanks,
Anwesha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Anwesha Pan is there some other similarly-named bot perhaps?
In this case, it was definitely the Portal-Only customer as @Arkadiusz Wroblewski suggested (I changed its name and it reflected as expected in the instance)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am glad you were able to figure it out by following @Arkadiusz Wroblewski suggestions 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.