Configure an Agent
Administrators and the CEO can adjust an agent's prompt, configuration, and autonomy so it fits your business.
#Purpose
Tune agent behavior to your organization's needs.
#When to use this
When an agent's output should better match your voice, rules, or context.
#At a glance
| Detail | Value |
|---|---|
| Required permissions | Edit agents (admin or CEO only) |
| Administrator level | CEO / Admin |
| Portal areas used | Agents (configuration) |
#Step by step
1
Open the agent
Go to the agent in the registry.
2
Adjust its configuration
Update its prompt, configuration, or autonomy setting.
3
Save
The agent uses the updated configuration.
4
Review output
Confirm the change improved results.
#Approval points
Human approval required
- Only an admin or CEO can change agent configuration.
#Security notes
Security considerations
- Agent configuration shapes AI behavior across the organization — restrict it to admins/CEO.
- Do not put secrets into prompts.
#Best practices
- Be specific in prompts about goals and constraints.
- Change one thing at a time and review.
#Common mistakes
- Letting non-admins change agents (not permitted).
- Vague prompts that produce generic output.
#Troubleshooting
| If this happens | Try this |
|---|---|
| I cannot edit an agent | Editing requires an admin or CEO role. |
| Output did not improve | Refine the prompt with clearer goals and constraints. |
#FAQ
Who can edit agent prompts?
Only administrators or the CEO.
Does changing autonomy let AI act on its own?
Meaningful actions still require human approval; AI assists and drafts.
#Keep exploring
#Related admin guides
#Business modules & workflows
Getting Started
Initial setup.
Platform Overview
How the OS fits together.
Knowledge Base
Task-level how-tos.
Business Workflows
End-to-end processes.
#AI departments
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?