Organization policy
An admin can manage SnapPrompt on a computer with a single file. Without it, the app uses its built-in defaults and nothing is locked.
Where the file goes
Put the policy at the path for the computer's system:
| System | Path |
|---|---|
| Windows | %ProgramData%\SnapPrompt\policy.json |
| Mac | /Library/Application Support/SnapPrompt/policy.json |
| Linux | /etc/SnapPrompt/policy.json |
The file is the same on every system. SnapPrompt reads it on that computer. Settings, License and organization shows the organization policy in force.
What a policy can set
- The default model.
- Which models are turned off, or given a daily limit.
- Which permission levels are allowed for Claude Code sessions.
- Command prefixes that are blocked in Claude Code sessions.
- How long images are kept (image retention time).
- Which OCR engine is used (Windows only; Mac and Linux have one engine each).
- Any setting, locked, so users cannot change it.
A locked setting shows a lock icon in the app, so users can see it is managed by their organization.
Without a policy file
The app uses its built-in defaults and nothing is locked. Removing the file returns a computer to that state.
The field list
The exact field names and allowed values are defined in the app's source filesrc-tauri/src/policy/types.rs. A field-by-field reference is not published on this site yet. To get one for your rollout, write to [email protected] and say which settings you want to control.
Related
- Send to Claude Code explains the permission levels a policy can limit.
- Activate a license covers licensing several computers.
- Privacy policy describes what stays on the computer.