SoldierX AI SIEMSoldierX AI SIEM
SoldierX AI SIEMIAM Documentation
  • 1. Overview & Primitives
  • 2. Identity Management
  • 3. Standard & Assumable Roles
  • 4. Policy Engineering
  • 5. Guardrails & Ceilings
  • 6. Policy Evaluation Engine
  • 7. Complete Action Reference
    • Canonical Grammar Standard
    • IAM Administration Catalog
    • SIEM Operations Catalog
    • Account, Notifications & Billing
    • Special Scoping Semantics
    • Dependency Checking
  • 8. Role Pattern Library
  • 9. Audit & Compliance
7. Complete Action Reference
Module 7docs/iam/actions-reference

Complete Action Reference & Scoping Catalog

Every permission in the platform follows the grammar below. This is the same catalog that powers the Effective Permissions panel, the policy editor's autocomplete, and every access-denied message in the product - the same action string always means the same thing everywhere you encounter it.

Canonical Action Grammar

Every action string follows the same three-segment pattern:

action-syntax.txt
service:module:operation
  • service: Either iam (identity and access control) or siem (everything else in the platform).
  • module: The targeted capability (e.g. case, incident, loganalysis, policy, role).
  • operation: The action verb (e.g. read, create, update, delete, assumeRole).

A quick note on how to read the "Resource" and "Scope" columns below: a resource restriction limits which specific thing (an asset, a case) the permission applies to. A scope restriction limits it along a second, independent axis - typically an ID-based filter for a read action, or a fixed own restriction for a mutation. Where a cell reads "-", that axis isn't supported for that action at all.

IAM Administration Catalog

Actions governing policies, roles, groups, direct user attachments, team members, and the IAM dashboard and audit log:

Action StringResourceScopePrerequisite Read
iam:policies:read--None
iam:policy:read-policy IDiam:policies:read
iam:policy:create--iam:policies:read
iam:policy:update-policy IDiam:policies:read
iam:policy:delete-policy IDiam:policies:read
iam:roles:read-role IDNone
iam:role:read-role IDiam:roles:read
iam:role:readPermissions-role IDiam:role:read
iam:role:create--iam:roles:read
iam:role:update-role IDiam:roles:read
iam:role:delete-role IDiam:roles:read
iam:role:attachPolicy-role IDiam:policies:read
iam:role:detachPolicy-role IDiam:roles:read
iam:role:attachBoundary-role IDiam:policies:read
iam:role:detachBoundary-role IDiam:roles:read
iam:role:assumeRole-role IDNone
iam:groups:read-group IDNone
iam:group:read-group IDiam:groups:read
iam:group:readPermissions-group IDiam:group:read
iam:group:create--iam:groups:read
iam:group:update-group IDiam:groups:read
iam:group:delete-group IDiam:groups:read
iam:group:attachPolicy-group IDiam:policies:read
iam:group:detachPolicy-group IDiam:groups:read
iam:user:attachPolicy-user IDiam:policies:read
iam:user:detachPolicy-user IDiam:users:read
iam:user:attachBoundary-user IDiam:policies:read
iam:user:detachBoundary-user IDiam:users:read
iam:user:attachRole-user IDiam:roles:read
iam:user:detachRole-user IDiam:users:read
iam:user:attachGroup-user IDiam:groups:read
iam:user:detachGroup-user IDiam:users:read
iam:users:read-user IDNone
iam:user:read-user IDiam:users:read
iam:user:readPermissions-user IDiam:user:read
iam:user:create--iam:users:read
iam:user:update-user IDiam:users:read
iam:iamdashboard:read--None
iam:audit:read--None

SIEM Operations Catalog

Actions governing telemetry, investigation, and response:

Action StringResourceScopePrerequisite Read
siem:dashboard:readagent ID-None
siem:inventory:readagent IDinventory sectionNone
siem:loganalysis:readagent ID-None
siem:correlation:readagent ID-None
siem:mitre:readagent ID-None
siem:incidenttree:readagent ID-None
siem:customincidenttree:readagent ID-None
siem:filterincidenttree:readagent ID-None
siem:incidentsummary:readagent ID-None
siem:incident:readagent ID-None
siem:incident:updateagent ID-siem:incident:read
siem:incident:markAsIncidentagent ID-siem:incidentsummary:read
siem:case:read--None
siem:case:create--siem:case:read
siem:caseassignment:updatecase ID(s), or "own"user ID(s)siem:case:read
siem:case:update-ownsiem:case:read
siem:case:resolve-ownsiem:case:read
siem:case:delete-ownsiem:case:read
siem:case:communicate-ownsiem:case:read
siem:case:addIncident-ownsiem:case:read
siem:widget:read-widget IDNone
siem:widget:createagent ID-siem:widget:read
siem:widget:updateagent ID-siem:widget:read
siem:widget:delete-ownsiem:widget:read
siem:workspace:read-workspace IDNone
siem:workspace:create--siem:workspace:read
siem:workspace:update-ownsiem:workspace:read
siem:workspace:delete-ownsiem:workspace:read
siem:report:readagent IDtimeline typeNone
siem:agentless:read--None
siem:aidetections:read--None
siem:aifeedback:update--siem:aidetections:read

Account, Notifications & Billing

Actions governing a team member's own alert preferences, notification delivery, and subscription/billing administration:

Action StringResourceScopePrerequisite Read
siem:teamalertconfig:read-user IDNone
siem:teamalertconfig:update-user IDsiem:teamalertconfig:read
siem:notification:receiveseverityalertsagent ID-None
siem:notification:receivesystemalertsagent ID-None
siem:notification:receivesubscription--None
siem:notification:delete--None
siem:subscription:read--None
siem:subscription:upgrade--siem:subscription:read
siem:subscription:downgrade--siem:subscription:read
siem:subscription:cancel--siem:subscription:read
siem:subscription:resume--siem:subscription:read
siem:assetname:edit--siem:subscription:read
siem:billing:retry--siem:subscription:read
siem:billing:portal--siem:subscription:read
siem:paymentmethods:read--None
siem:paymentmethods:create--siem:paymentmethods:read
siem:paymentmethods:update--siem:paymentmethods:read
siem:paymentmethods:delete--siem:paymentmethods:read

Special Scoping Semantics

A handful of actions carry scoping rules worth calling out on their own:

Case assignment is the one dual-meaning action

On siem:caseassignment:update, the resource axis and the scope axis mean genuinely different things at the same time: resource limits which case IDs (or just the caller's own cases) can be reassigned, while scope separately limits which user IDs the caller is allowed to assign onto them. A team lead can hold this scoped so they can only assign work on their own team's cases, and only to members of their own team.

Reports and inventory scope differently

On siem:report:read, scope filters report periods (daily, weekly, monthly, quarterly, a fixed calendar quarter, or a custom range). On siem:inventory:read, scope filters inventory categories (host details, network, open ports, installed software, running processes) - independently of which assets the resource axis covers.

Dependency Checking

Most mutation actions above list a prerequisite read action. Some permissions only make sense alongside another one - you can't meaningfully be granted "resolve a case" without also being able to view cases. The system checks for this whenever a policy is built or attached, and flags a grant that's missing its prerequisite, without necessarily blocking it - so you don't end up with a permission that's technically present but unusable in practice.

On this page

Canonical Grammar StandardIAM Administration CatalogSIEM Operations CatalogAccount, Notifications & BillingSpecial Scoping SemanticsDependency Checking
Previous6. Policy Evaluation Engine
Next8. Role Pattern Library