Policy Profiles

Profiles let you save a policy configuration, switch between them, and share them across your organization via the ArmorIQ backend.

Saving a Profile

Save the current active policy as a named profile:

/armor profile save strict-mode

The profile captures all current statements, the default decision, and metadata. You must have at least one rule - empty policies cannot be saved.

Listing Profiles

/armor profile list

Shows all saved profiles with their name, description, version, and creator:

Saved profiles (2):
  strict-mode - (no description) (v1, user)
  balanced - Read allowed. Bash/Write/Edit require approval. (v1, user)

Switching Profiles

Switch to a saved profile (stages the change for confirmation):

/armor profile switch balanced
/armor yes

The switch replaces your entire active policy with the profile's policy.

Deleting Profiles

/armor profile delete strict-mode

Deletes immediately - no confirmation needed.

Sharing Profiles with Your Organization

With an API key connected, push and pull profiles to/from the ArmorIQ backend:

Push a Local Profile

/armor profile push strict-mode

Uploads the profile to your organization. Other team members can pull it.

Pull Organization Profiles

/armor profile pull

Downloads all profiles from your organization and saves them locally. Existing local profiles with the same name are overwritten.

Workflow Example

Set up a team-wide "compliance" profile:

/armor policy template lockdown
/armor yes

/armor policy add allow Read and Grep
/armor yes

/armor profile save compliance
/armor profile push compliance

On another machine:

/armor profile pull
/armor profile switch compliance
/armor yes

Where Profiles are Stored

Profiles are saved as JSON files in the plugin data directory alongside your policy:

ls ~/.claude/plugins/data/armorclaude-armoriq/profiles/