Skip to content
GitHub

Organization settings

The Settings menu item by item, who sees each one, and the organization-wide agent defaults and personal preferences it holds.


On this page

Settings holds what applies beyond a single agent: defaults for every new agent, your own preferences, security controls and billing. Not everyone sees every item. Some depend on your role, some on your plan, and some are rolled out per organization.

What appears in Settings#

GroupItemWho sees it
AccountPreferencesEveryone
AccountProfileEveryone. Opens your account page
OrganizationAgentsEveryone
OrganizationIntegrationsEveryone
OrganizationMembersEveryone. Opens your organization's account page
SecuritySingle sign-onAdmins and Owners, on plans that include SSO
SecurityAPI keysAdmins and Owners, in organizations where Runbear has rolled it out
SecurityTool approvalsAdmins and Owners, in organizations where Runbear has enabled it
SecurityAudit logAdmins and Owners, on plans that include the audit log
BillingPlanMembers whose role includes billing access. Where the organization doesn't enforce access control, every member
BillingUsageOrganizations where Runbear has rolled it out (currently aimed at Team, Pro, Business and Enterprise plans)

If an item you expect is missing, check your role first. For a plan-gated item, see Billing and credits. For a rolled-out item, contact support@runbear.io.

API keys are managed on Settings → API keys where it appears. If your organization doesn't show that item, open Settings → Members, which opens your organization's account page, and manage keys in its API Keys section. See Authentication and API keys.

Agents#

Settings → Agents holds defaults for the agents in your organization. An agent's own settings override them.

Default instructions#

Instructions that pre-fill a new agent created through Create manually. Leave the field empty to use Runbear's own starter instructions. Agents created from the Create Agent dialog start from Runbear's starter instructions either way, and changing this field doesn't change existing agents. See Instructions.

Built-in tools#

"Give new personal agents Runbear's own tools. Existing agents keep what they have."

This is on by default. Despite the wording, which is being updated in a pending fix, it covers more than personal agents: with it on, every agent created in the dashboard or through the MCP server, and every personal agent, gets Runbear's built-in tools, so you can ask the agent itself to adjust its instructions, tools or triggers. Agents created with POST /v1/agents don't get them. Turning the switch off affects only agents created afterward.

Scheduling from chat#

"Let an agent create a recurring job when someone asks in chat. You can still add schedules yourself."

On by default. Turn it off if agents should never set up their own recurring runs; people can still create schedules as triggers.

Preferences#

Settings → Preferences holds your personal preferences. Only you see them.

  • Appearance: Light, Dark or System. It applies as soon as you pick it and is saved in this browser, so each device keeps its own choice.
  • Support access: lets Runbear support sign in as you while they work on a ticket you filed.
  • Time saved: Minutes saved per thread and Minutes saved per message, the formula behind the Estimated Time Saved figure in analytics. Because it is a personal preference, each person sees the estimate from their own formula.