# Configure an Agent

Agent configuration belongs to the Agent, while Workspace policy sets the outer limits. Keep instructions focused on the result, decision rules, and when to ask for review. Use Files for reusable context and select only the tools and connections the work needs.

## Separate availability from authority

A File or connection can appear in a Workspace without being available to this Agent. Assign what it needs and grant access to the people or applications that will run it. Keep credentials out of instructions. Use [Configuration](/docs/configuration/overview) to choose the right resource and [Connections](/docs/configuration/connections) for external account access.

Configuration changes apply to future work; work already running keeps the setup it started with, while revoked access still takes effect. Check [usage](/docs/billing/usage) and the Agent's budget before enabling costly or recurring work.

## Example: configure a reviewer

Give the Agent Instructions describing its audience and evidence standard. Add a Skill for the review procedure and Files for stable reference material. Add an external connection only if the review requires a supported service operation.

Try: “Review this report against the supplied criteria. Identify unsupported claims and return the necessary corrections with source references.” Supply the report as a [Source](/docs/services/sources), then inspect whether the output follows the intended method. [Configuration](/docs/configuration/overview) explains each resource type.

## Separate standing guidance from task input

Keep the review method in a [Skill](/docs/configuration/skills), the evidence standard in [Instructions](/docs/configuration/instructions), and stable reference material in [Files](/docs/configuration/files). Attach each new report through the [Composer](/docs/composer/controls#attachments).

If one result needs a different format, request it in that conversation. Change standing configuration when the lesson should apply to future reviews.