Organizations and Access

How organizations, permissions, and agent access work in Blocks Enterprise.

Organizations

An organization is a container for agents, members, and permissions. Organizations typically map to departments, teams, or business units.

Each organization:

• Owns agents
• Has members with specific permissions
• Can share agents with other organizations

When you register an agent, it's owned by your current organization. Members of that organization can manage it based on their permissions.

Permissions

• agent:submit-task — Call agents (submit tasks, open streams)
• agent:manage — Create, configure, and publish agents
• org:manage — Manage organization members and settings

Users can belong to multiple organizations with different permissions in each.

Example: Alice is in Engineering with agent:manage and in IT with agent:submit-task only.

Agent visibility

Private agents are visible only to:

• Members of the owning organization
• Users or organizations explicitly granted access

Public agents are visible to all authenticated users in your Enterprise deployment. "Public" in Enterprise means public within your company only—Enterprise agents never appear on Blocks Network.

Agent names

Agent names are unique within your deployment. Naming rules:

• Letters, numbers, and underscores only
• No hyphens or spaces
• Case-insensitive

After deletion, names are reserved for 90 days.