Process Automation Teams

Teams provide both a way to organize and route tasks in a business process, and provides for access controls to sensitive elements or for team separation. This allows teams to have and create automation specific to their needs, while preventing others from being able to see or alter those processes and resources.

Projects within the teams provide further control, and allow one team to prepare a process suite that can then be provided, or transferred to, another team for use.

What is in this section

Team Security Features

Managing Teams

Navigating Within Teams

Projects

Process Automation Security Best Practices - Teams and Projects

Securing your Process Automation resources and data should be a top priority when you are working in Laserfiche Cloud. You should consider the following when building your Laserfiche Cloud processes within Process Automation:

The goal is to configure your Process Automation security so that the correct individuals are able to manage who can design your processes as well as see the collected data.

Securing with Teams and Projects

It is highly recommended to create your business processes within a project security context that is managed by the appropriate team. Teams can give access to external team members as they desire to view the collected data or edit their processes.

Adding Process Automation resources to projects will secure the data that is collected from these processes as well as the configuration abilities for these resources to approved team members or external individuals.

Below is the current list of available resources to be secured within projects. More will continue to be added in the future:

If resource types such as Business Processes or Surveys are not secured within projects, there could be a potential security risk in your Laserfiche Cloud system.

Existing Business Processes

Pre-existing businesses processes within the Global security context should be migrated to the appropriate team and project security context that it belongs to. There is a security risk in not doing so as all ACS Process Developers have access to the Global security context and thus can view and edit the processes and collected data. More information on how to migrate and retain previous instance data, can be found here.