Skip to main content
Organization admins and members with the Security role can set defaults for new agents created in the organization. Open Settings > Agent Defaults to customize them. The separate organization conversation policy on this page applies to existing and new tasks, not just new agents.
The new-agent defaults are available to the organization Admin and Security roles on the Pro plan or higher. Both roles can view and manage these settings. See the organization role matrix.
There is one set of defaults per organization.
Agent Defaults page with Default model (Auto, Balanced preset, Smartest preset), a note that editing a preset changes every agent that uses it, Fallbacks, and Privacy with File Sharing Behavior and Personal Conversations Only

Settings > Agent Defaults. The model controls shown are the Enterprise view. Available settings depend on your plan.

​
Available settings

On Pro, reasoning, speed, and context-window defaults are model-aware. Available controls depend on the model you pick. Enterprise organizations manage model runtime defaults through presets. See AI model governance & configuration for configuration and transitions from older defaults. For File Sharing Behavior, the available values are:

​
Messaging mode

Messaging mode sits under Default settings on Agent Defaults. It sets how new custom agents send replies in the web chat and connected channels:
  • Classic: sends one reply with its final response when the turn finishes. This is the default.
  • Conversational: sends messages while it works, including more than one per turn.
Default settings section of Agent Defaults with the Messaging mode row: How new agents send replies in chat and connected channels. Each agent can change this in its own settings. Set to Classic
Each agent can change it under Messaging Mode on its Settings tab. Existing agents keep their current mode. See Messaging mode for what each mode changes.

​
How defaults apply

Every new custom agent created in the organization inherits these defaults for anything its creator doesn’t set:
  • The initial model selection and model-specific defaults where supported
  • File-sharing behavior
  • The agent’s default abilities configuration, including which native abilities are on and which image model Image Generation uses
If your organization has no defaults, Gumloop’s built-in defaults apply. Changing the initial model selection or other new-agent defaults doesn’t update agents that already exist. Preset edits are different from new-agent defaults. Enterprise preset changes can affect existing agents. See AI model governance & configuration. A few settings are never inherited:
  • The agent icon
  • The agent’s self-improvement settings, which follow the creator, such as their timezone
Removing the organization defaults puts new agents back on Gumloop’s built-in defaults.

​
Organization conversation policy

Personal Conversations Only, in the Privacy section of Settings > Agent Defaults, limits every member to their own conversations, which are otherwise shared with their teams by default. Unlike new-agent defaults, this policy applies to both existing and new tasks.
Agent Defaults Privacy section with File Sharing Behavior set to Default and the Personal Conversations Only toggle: Limit every member to their own conversations, which are otherwise shared with their teams by default
When enabled:
  • You keep access to conversations you started, conversations explicitly shared with you, and conversations that invite you.
  • Existing Slack and Teams collaboration access stays in place. The policy doesn’t make those conversations private to their initiator.
  • Agent Owners and organization admins retain agent configuration access, but their role alone no longer grants access to every saved conversation.
  • Task history, listings, and search exclude conversations you can’t access, including their titles and snippets.
  • Gumloop hides the agent-level Task Visibility control, which can’t override the organization policy.
File permissions remain separate. The policy doesn’t make private chat files accessible through agent ownership or organization administration, and a file’s own sharing permissions can grant access independently of its source conversation. When disabled, Gumloop restores each agent’s saved Task Visibility preference. It doesn’t change every agent to Team tasks. See Agent access for the agent-level settings.