Roles and permissions on the platform

The Strike platform includes a role system that defines what each user can see and do within the organization. This structure helps maintain operational control, assign responsibilities clearly, and limit access based on each member's profile.

There are four main roles at the organization level:

• Owner: has full control over the platform, including assets, vulnerabilities, projects, connectors, settings, and user and role management.

• Operator: can manage operations, including assets, vulnerabilities, connectors, and projects, but does not have permissions to manage users.

• Auditor: read-only access to all assets, vulnerabilities, and threat emulations in the organization.

• Member: has limited read-only access, restricted to the assets and vulnerabilities explicitly assigned to them.

Granular access per asset

In addition to the global role, the platform allows configuring specific permissions per asset. This enables a more flexible model, where users can have different access levels depending on the asset, without needing to modify their role across the entire organization.

💡 Typical use caseA developer may have a Member role at the organization level but hold Operator permissions on their team's asset, allowing them to manage it without accessing the rest of the environment.

* Important: the effective access level will always be the highest between the global role and the one assigned per asset. This means that if a user has a broader role at the organization level, that level will prevail over any restriction configured at the asset level.

Permissions by action

Below are the capabilities of each role within the platform:

Proper assignment of roles and permissions helps maintain operational security, prevent unnecessary access, and ensure that each user interacts only with the information and features relevant to their role.