# Agent access

An Agent belongs to a Workspace and has an individual owner. Give a person an Agent role to let them view, use, or manage it as appropriate. Resource access does not require Workspace membership and does not open other Workspace resources.

## Applications need a separate grant

An application cannot use an Agent merely because they are associated. Grant the application access explicitly, and review development and production grants separately. An application user's identity does not create a private Agent conversation space; conversations use the Agent's shared resources.

Connection assignments are another decision. Granting an Agent role does not administer an account connection or expose a credential. See [Workspace sharing](/docs/workspaces/sharing) and [connection authorization](/docs/configuration/connections).

## Example: connect a portal

A customer portal might call an Agent to review an uploaded report. Grant the development application the supported Agent access, then authorize the production Site separately when needed.

The portal must enforce its own user permissions before making the call. An Agent association or a visitor login does not create the grant. Review [Authentication](/docs/reference/authentication), [Permissions](/docs/concepts/permissions), and the current [API reference](/docs/reference/overview).

## Review access before integration

Identify the caller, the Agent, and the operations needed. Keep development and production grants explicit, then check a small representative request under the intended caller's identity. Do not use a human administrator's broad credentials as evidence that the application's own access works.

A portal handling several customers must enforce its own data boundaries. Separate Agent conversations do not create private per-customer working resources.