Core Docs - Core Concepts - Agent Security

Rock Version: v20.0
Last Modified: 2026-07-15 1:56 PM

Rock's agents work within the same security model you already use everywhere else in Rock. The roles, permissions and access controls you've set up apply here too.

New agents start locked down.
When you create a new agent, Rock restricts access to RSR - Rock Administrator by default. That is intentional - agents can write data, so Rock errs on the side of caution. Before staff can use a new agent, open the agent security and grant View access to the right role. For most organizations, RSR - Staff Workers is the right starting point for internal use.    

Security works in layers

Agent security has three layers.

The agent isn't a shortcut around your permissions. It works within them.

Here's an example of how to secure an agent...

Then an example of how to secure a skill or tool...

Internal vs. Public

The Audience setting on each agent (covered in Configure an Agent) also shapes what data the agent can share. A public agent should carry only the skills appropriate for an unknown visitor. Think carefully about which skills you attach and keep the set narrow.

What Spark sees

Spark Development Network does not have access to your organization's data. Your configurations, instructions and conversation history stay within Rock and the AI provider you've configured.