Is it possible to turn off the enforced messages that have started appearing in Archer SaaS in a big yellow box?
Causing confusion among end users & they are unnecessary.

Originally posted on August 2, 2024 in the Archer Community.
Is it possible to turn off the enforced messages that have started appearing in Archer SaaS in a big yellow box?
Causing confusion among end users & they are unnecessary.

Originally posted on August 2, 2024 in the Archer Community.
Comments
5 comments
Mike - these banner messages should only be appearing to those users who have a System Administrator role or who have been given the OOTB Role: Troubleshooting Access or Group: Self-Help Admin.
Originally posted on August 2, 2024.
OK, thanks. Is it possible to turn off?
Originally posted on August 2, 2024.
It's scheduled to run for this week leading up to the Free Friday Tech. Huddle. When you close the window, it will not display again within a 24-hr. period. We hope you're able to utilize the Chatbot to assist you with any problems you may encounter or questions you have regarding the platform.
Originally posted on August 2, 2024.
Well, I'd like to remove the chat bot, but I believe the only way to do that is to remove your email address, meaning you won't get notifications, which is not helpful. At the very least, it would be useful to be able to move the speech bubble for the chat bot & place it somewhere where it does not get in the way. A better option for it would be a link in the top bar, like the online help, doesn't make sense to place it somewhere on the screen where it gets in the way & sits on top of items in the nav menu.
Originally posted on August 2, 2024.
Mike, I would check to see who all is assigned to the Self-Help Admin group in your production. If there are users who are receiving that message that shouldn't, then they should be removed. We only have our system admins assigned this role. The messages have been extremely helpful to give us updates and to be able to provide updates to our leaders on when the latency issue is going to be corrected.
Originally posted on August 5, 2024.
Please sign in to leave a comment.