Roles and permissions on the platform

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

Organization-level roles

There are four roles:

• 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 cannot manage users.

• Auditor: has read-only access to all assets, vulnerabilities and Threat Emulations in the organization.

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

Granular access per asset

In addition to the global role, you can configure specific permissions per asset from the Access tab in the asset detail. This way, a user can have different access levels depending on the asset, without changing their role across the whole organization.

Typical use case: a developer can have the Member role at the organization level and Operator permissions on their team's asset. This lets them manage it without accessing the rest of the environment.

Important: the effective access level is always the highest between the global role and the one assigned per asset. If a user has a broader role at the organization level, that level takes precedence over any restriction configured on the asset.

For more details, see Asset detail: Overview, Details and Access.

Permissions by action

Assigning roles and permissions correctly lets you maintain operational security, avoid unnecessary access and make sure each user interacts only with the information and features relevant to their role.