Skip to main content
The Agent Management page gives administrators a bird’s-eye view of all agents in their workspace—their status, capabilities, and who has admin access. From here you can pause agents, manage permissions, and control which capabilities are available.
Agent management page showing the Agents tab with a list of agents, their status, privacy settings, and capabilities

​
Access levels

  • Workspace administrators see all agents and have access to workspace-wide settings
  • Team administrators (when teams are enabled) see only agents within their teams

​
Agents tab

The Agents tab lists all agents you have access to. Each row shows:
ColumnDescription
AgentName and avatar
StatusOn/Off toggle—paused agents don’t process triggers or scheduled tasks
PrivacyWorkspace (visible to everyone) or Private (invitation-only)
UsageCredits used today, with optional daily limit
AdminsCurrent agent administrators
Click any agent row to expand and see its capabilities. Each capability badge shows an icon indicating whether it runs autonomously or requires approval.
You don’t need access to the Agent Management page to stop an agent. Anyone with edit rights can stop their agent from within the agent’s settings, under the Main Settings tab.

​
Managing agent admins

Add or remove administrators for any agent. Admin tags are color-coded to indicate membership status—for example, red indicates a user who is no longer a member of your workspace.
You can’t remove the last admin from an agent—every agent needs at least one administrator.

​
Capabilities tab

Control which capabilities and MCP servers are available for agents.
Agent management page showing the Capabilities tab with workspace-wide settings and capability toggles

​
Workspace-wide settings

Workspace administrators have two top-level controls: Allow Custom MCP Servers
When enabled, users can add their own MCP servers to agents. Disable this to restrict agents to workspace-approved servers only. Default mode for capabilities
  • Default ON: Capabilities are available unless explicitly disabled
  • Default OFF: Capabilities are unavailable unless explicitly enabled
This is especially important when Abundly adds new capabilities to the platform—should they be allowed by default?

​
Capability toggles

Each capability has three states:
  • ON (solid green): Explicitly enabled
  • OFF (solid red): Explicitly disabled
  • Default (outlined): Follows the default mode setting
Click a capability to cycle through these states.

​
Team-level overrides

If your workspace uses teams, each team can have its own capability settings that override the workspace defaults. Team administrators can set team-specific default modes and enable or disable capabilities for their team. Capabilities disabled at the workspace level can’t be enabled at the team level—those appear grayed out with a “Blocked” label.

​
FAQ

Paused agents stop processing triggers, scheduled tasks, and incoming messages. The agent remains fully configured and can be resumed at any time.
Workspace-level settings apply to all agents. If your workspace uses teams, team settings can override workspace defaults, but can’t enable capabilities that are disabled at the workspace level.

​
Learn more

Capabilities

What capabilities are and how they work

Usage & limits

Monitor and control agent resource usage

Teams

Organize agents by department or function

Access control

Security roles and permissions