Managing Enterprise Bots at Scale with AtBot
Bots are becoming a new medium in which to deploy line-of-business applications out to front-line workers. AtBot can play a pivotal role in helping organizations maintain governance and best practices across their business so bots don’t fall into unmanageable silos.
Like any line-of-business application, the life cycle of developing a bot will start with a business unit that has a need. That business unit will present their case to IT to get the bot built and IT will either provide them with the resources they need to do it themselves or take it on as an IT development task.
From a development standpoint, AtBot provides the most powerful no-code bot platform for the Microsoft Cloud. This makes it an easy choice for how any single bot should be developed and deployed. But AtBot also includes a number of tools that allow your organization to manage and deploy many bots across business units with varying ownership.
Role-Based Access Control
The Contributor role in the AtBot Admin Portal allows an organization to designate “bot builders” or teams of builders to build out their bots while only having access to the skills and bots that have been shared with them. Make sure to review our in-depth article about the Contributor role and how it works.
This control empowers IT (or the owner of the AtBot platform) to designate teams of bot builders on a project-by-project basis. It’s up to the organization to determine how they wish to scale this out, but there is no limit to the amount of contributors within a tenant.
AtBot Admin Power Automate Connector
The Admin Power Automate connector is an essential component to the scale-out strategy for AtBot. From alerting administrators when new skills are created to automating the assignment of licenses, the Admin Connector is like an API for administration of the AtBot platform in an organization.
Admin Portal Settings
In the AtBot Admin Portal, under Tenant Management > Logging & Settings, there are a number of useful settings to help your organization scale the platform.
Azure Event Hub Settings
By supplying an Azure Event Hub connection string, all bot traffic will begin to stream into your designated Event Hub. To leverage these logs on a per-bot basis, you would want to employ Stream Analytics to split up the logs and send the data to the correct owner. Here’s an article that covers how to set that up.
Access Denied Message
You can optionally set a message to be sent to any user who is not a Contributor or Admin, when they try to visit the AtBot Admin Portal. This message could contain information about who they should contact in order to get started with building bots in AtBot for that organization.
Unlicensed User Message
When a user tries to use your bot as a logged in user without an AtBot license, you can customize the message that is returned to them. Using this custom message in conjunction with the proper AtBot Admin Power Automate trigger can facilitate automatically assigning user licenses or running through a license request/approval process in Power Automate.
Login Success Redirect
After a user successfully logs into a bot, you can configure the URL they are redirected to afterward. This redirection will include the App ID of the bot so you can conditionally display a message based on the bot they logged into.
The Enterprise-Scale Bot Platform
At AtBot, it’s our goal to create the most powerful and intuitive no-code bot platform on the market. In conjunction with the tools and capabilities to manage at scale, AtBot is an easy choice for any enterprise looking to standardize on a platform for line-of-business bots.
