Any application intended for enterprise deployment must squarely address security, and Blue Prism is no
exception. One important foundation for security in the product is role-based access control. Once a Blue
Prism administrator has defined what roles a user can act in, the system will allow that user to perform
only the actions allowed by these roles.
Blue Prism also keeps track of significant changes to its environment. Using the Audit Log Viewer, part of
System Manager, an administrator can examine records of things such as when a user logs into Blue
Prism, when that user starts or deletes a process, when that user changes her password, and more.
Another issue, especially for a technology based on presentation integration, is safely storing and
managing the user names and passwords used to log in to applications. To do this, Blue Prism provides an
encrypted credentials database controlled by a Blue Prism administrator. For example, a set of credentials
(i.e., a user name and password) might be usable only by specific Blue Prism processes started by users in
specific roles and running on specific servers. It’s also possible to use Active Directory in place of some
parts of Blue Prism’s user management mechanisms. While it’s not required, larger organizations in
particular can find this useful.