Managers Can Now Update Any Teammate's Agent Settings
Managers and admins saving execution settings on a shared agent that runs on someone else's machine no longer hit an error that blocked the save.
Summary
Agents can be shared across a team, but a manager adjusting a shared agent's execution settings — such as which model it uses — could run into an error if that agent happened to run on a teammate's machine rather than their own. That's fixed: the save now goes through correctly.
What You Gain
Shared agents are meant to be manageable by anyone with the right permissions, not just the person whose machine they happen to run on. Before this fix, a manager trying to tweak a shared agent's settings got blocked by an error entirely unrelated to whether they were actually allowed to make the change — simply because the agent's machine belonged to someone else. That meant asking the machine's owner to make the change instead, even when the manager already had full permission to manage the agent.
How It Works
- Saving an agent's existing settings now works regardless of who owns its machine — only an actual change to which machine it runs on is checked against ownership.
- Managers and admins can move a shared agent onto any machine in the company, consistent with their existing ability to edit any agent.
- If you try to move an agent to a machine you're not allowed to use, you now get a clear message on that field, instead of a generic error.
Where to Find It
This applies automatically wherever you manage an agent's Execution settings — there's nothing to turn on.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.