Approving your organization's Claude settings
What to do when a task waits for approval of the Claude settings your organization serves. Who can decide, what each choice does and how to undo it.
Your Claude organization can serve its own settings to every Claude Code user. These are called managed settings. They can set environment variables, name network hosts and run hook commands. Claude Code asks a person to approve them the first time it meets them, and again when they change.
A stage has no person at the terminal. So CodeHerder asks you instead. You approve the settings once, and every Claude stage in the workspace uses them from then on.
What happens when a stage meets the dialog
CodeHerder notices the approval dialog and opens one request for those exact settings. Every stage in the workspace that meets the same settings joins that request. The Blockers page shows one row for it, with the number of waiting tasks.
Each waiting task becomes blocked. Its blocker reads “Waiting for a workspace admin to approve the org’s Claude settings”. Every human owner and admin gets one in-app message when a request opens. A stage that joins an open request sends none.
You can’t clear this blocker by hand. It clears when someone decides the request. See Blockers and blocked tasks.
What a request shows
A request lists what the settings do, so you can judge them before you decide:
- Env vars. The names only. A value is never shown.
- Sends data to. The hosts the settings name.
- Every other setting. Shown in full, including hook commands.
- Added, Removed and Changed. What differs from the settings you approved before. This appears only when there is an earlier approval.
- Waiting tasks. The tasks that wait on this request.
- Device evidence. What the device reported about applying the settings, when it reported anything.
Read the hook commands before you approve. A hook command runs on every device that starts a Claude stage in the workspace.
Who can decide
A human workspace owner or admin can approve, reject or try again. Any human member can read requests. An agent can’t read or decide them.
Where to decide
In the web app, open Admin → Integrations and choose the Claude card. The Claude card has no connection to set up. It holds only these requests. Each request shows the buttons you may use.
From the command line:
ch managed-settings list --state pending
ch managed-settings show <managedSettingsApprovalId>
ch managed-settings approve <managedSettingsApprovalId>
ch managed-settings reject <managedSettingsApprovalId> --reason "not our collector"
ch managed-settings retry <managedSettingsApprovalId>
list shows every state unless you add --state. approve asks you to confirm. Add --yes when you do not run it at a terminal. See Using the CLI for sign-in and output options.
The three choices
- Approve. CodeHerder stores the settings for this workspace. The waiting tasks go back to their stages. Every Claude stage then starts with the settings in place, so the dialog does not appear again. The confirm dialog repeats this, including the hook warning.
- Reject. The settings stay unapproved. You can add a reason of up to 300 characters. It goes into the blocker of each waiting task. Those tasks stay blocked until the organization’s settings change or an admin approves.
- Try again. CodeHerder releases the waiting tasks without a new decision. Use it after you fix the device, or after you approve the settings by hand on the device. See When CodeHerder can’t store the settings.
Request states
A request has one state:
- Pending. Waiting for a workspace admin to approve or reject these settings.
- Approved. Stored for the workspace. Every stage writes them back before Claude starts.
- Rejected. Waiting tasks stay blocked until the organization’s settings change or an admin approves. A rejected request can still be approved later.
- Superseded. Replaced by a newer request, because the organization’s settings changed. You can’t approve a superseded request. Its waiting tasks move to the newer one.
When CodeHerder can’t store the settings
Some settings can’t be stored. The request says why:
- The settings are larger than a workspace stores.
- The settings file isn’t a JSON object.
- The settings set environment variables that a workspace refuses to set.
- The device couldn’t read the settings.
For these, Approve is not offered. Approve the settings once by hand on the device. Then choose Try again. If the device couldn’t read the settings, fix the device first. Then choose Try again.
A related case: you approved the settings, but a device ran a stage without them. The blocker says so. Fix the device, then choose Try again.
Revoking an approval
To remove the approved settings, reject the approved request. Choose Reject on the request, or run:
ch managed-settings reject <managedSettingsApprovalId>
Only a human owner or admin can do this. The next Claude stage starts without the settings. If your organization still serves them, the stage waits on the rejection. You can approve the request again later.
Related
Last updated