Data Privacy & Segregation

Administrators can manage roles and permissions for organizational security and scaling of RPA operations. Nintex’s multi-tenant architecture allows administrators to configure separate working environments and teams for different business units and allocate resources such as RPA developers, managers, and robots to each team – facilitating in-team collaboration.

Multi-tenancy

Enterprises can create fully-separate and secure teams and environments. Resources including robots, RPA developers, and more can be allocated to each team. Administrators can provision multiple companies within an organization, and for each provisioned company, separate the data across all stages of the development and production automation life-cycle.

Authorization & access permissions

Only administrators have the privileges to authorize access permissions, which can be managed in several levels of granularity:

  • RPA Developers can be restricted to specific companies (groups), robots, workflows

  • Robots can be assigned permissions only to specific companies (groups), workflows and data

  • Workflows can be restricted to specific companies (groups), embedded workflows and data

Administrators manage segregation of duties for Studio users as well as robots:

  • Administrators can manage both permissions and users/robots associated with the automation workflow catalog

  • Studio users can be set in groups and roles. Each group/user can have independent segregation between various departments based on organizational needs

  • Administrators can share or block automation workflows per the group/user permissions definition

  • Similarly, Administrators can set permissions for robots, at a group/robot level, allowing/blocking workflow execution

Groups

Administrators can group robots by task types, business units, or other criteria to manage the virtual workforce more efficiently. Instead of assigning a task to a specific robot, a task is assigned to a group and Nintex’s server optimizes the task assignment, sending it to the first available robot. Administrators can add or remove robots from a group based on workload.