Which role is NOT able to edit custom workflows in Falcon?

The Security Lead role is not able to edit custom workflows in the Falcon platform. This distinction is important as each role within the Falcon environment has specific permissions and capabilities tailored to its responsibilities.

Typically, the Falcon Administrator has comprehensive control over the system, including the ability to create and edit workflows. The WorkFlow Author, as the name suggests, possesses the privileges necessary to develop and modify workflows specifically. The Analyst, while often focused on monitoring and responding to security incidents, may also have limited editing capabilities, depending on their permissions set by an administrator.

In contrast, the Security Lead is generally more focused on overseeing security operations and decisions rather than directly interacting with the technical details of configuring workflows. Their role is crucial for strategy and management, but it does not extend to the technical editing of custom workflows, ensuring that this task remains within the bounds of those roles that require direct interaction with the system's configuration and management capabilities.