โ01-15-2021 08:22 AM
[Dec 22, 2020] Mike Power (CRM Enterprise Architect at American University) posted:
Good afternoon all,
We did a brief POC with Workbot for MS Teams recently, and may build some recipes with it but our infrastructure group has governance concerns.
Iโm curious what others do with Workbot for MS Teams (or potentially other applications since the need for governances is probably the same). Questions like:
Weโre pretty new to this space, so Iโd appreciate any thoughts/gotchas on starting to use Workbot as an organization.
Thank you!
โ02-26-2021 12:33 PM
We have a dedicated service account for the connection. Our Office365 Admin is able to temporarilly elevate its permissions to perform the consent, then change it back to non-admin. The admin does this for us only one time during the setup.
We have a single bot, and yes the commands are getting a bit long. I dont think we are ready for custom bots yet. Probably soon. However, one of the things we do is check AD/Okta group membership for the user who is running the bot command to see if they are allowed to run it.
I.e. in each bot recipe we capture the user who is running the bot, we call a callable recipe that checks if this user is a member of an AD group that we define for this purpose (or reuse a group if already exist). If the user is not a member we stop the command and reply to the user with some kind of "not authorized" message.
Hope this helps.
โ02-27-2021 11:13 AM
Hey Mike Power !
Tagging you back into the loop, so you are kept up-to-date with more of the brilliant information your peers have provided ๐
Ported this conversation from the previous platform. Hope the new answers are of help to you!