Choose how Bearly uses external tools

Use Permissions beside the chat input to choose when Bearly asks before using enabled tools outside the chat.

Standard asks for approval when needed and respects approvals you have already saved. Full access lets Bearly use enabled external tools without asking each time. The selected model does not change this permission mode.

Limited availability

Full access must be available for your account and app version. For a managed organization account, it’s available unless an organization administrator turns it off. Each tool still needs to be available on your device: local commands, Computer Use, and Bearly Browser or connected Chrome control require the desktop app.

On a phone or tablet, Full access applies to supported connectors enabled for that chat. Mobile browsers support HTTPS connectors, including service sign-in. In the iOS and Android apps, custom HTTPS servers can use a bearer token, custom headers, or no authentication; services requiring OAuth sign-in need Bearly in a regular browser. Full access on your phone does not control another device.

Enable full access for a chat

1. Open the chat and select Permissions beside the input.
2. Select Full access.
3. Review the enabled tools and warning, then select Enable full access. Choose Cancel to keep Standard.

The composer shows Full access while it is active. It applies only to this chat on this device. Other chats, shared copies, another account, and other devices do not inherit it. You can separately choose a default for new chats on this device.

Review the access you are giving

Enabled tools may read, change, or delete files, run programs, and act in signed-in apps and websites. Mistakes or instructions in untrusted content can cause unintended changes. Keep sensitive work in Standard when you want to review actions individually. A selected working folder is context, not a security sandbox.

Organization restrictions, operating-system permissions, and required safety checks still apply. Full access does not turn on a disabled tool, connect an account, or grant access that the account does not have.

Tools and accounts you deliberately enable later are included. Their setup screens explain that chats using Full access can use them without asking for tool approval. Scheduled Routines require their own separate Full access approval.

Return to a chat

Full access stays on in that chat on this device until you choose Standard or revoke it. Restarting Bearly and time away do not turn it off.

It pauses when Bearly cannot confirm it is still allowed, for example while offline, when an app update is needed, or when your administrator has turned it off. The composer shows Full access paused. Open it and select Resume full access after Bearly checks availability, or Standard to turn it off. If authorization is revoked while Full access is active, Bearly switches the chat to Standard.

While paused, the chat follows Standard. Sending a message does not resume Full access. If your administrator has removed eligibility, Resume remains unavailable.

If Bearly cannot check availability, reconnect and open Permissions or Full access paused again. If the panel asks for an app update or an enabled external tool, complete that step first. An organization restriction needs your administrator’s help; it cannot be changed from the chat.

Start new chats in Full access

Open App Settings → Privacy & Security and turn on Start new chats in Full access. Review the warning, then select Turn on. Choose Cancel to leave the setting off.

New chats on this device use your enabled tools without asking. Agents make mistakes, and instructions hidden in web pages, files, or emails can steer them. Don’t turn this on unless you know what you’re doing.

The setting applies only to your account on this device. If Full access cannot start in a new chat, that chat uses Standard and Bearly tries the default again when you reopen it. A chat where you already chose Standard keeps that choice, and routines still require separate approval. You can switch any chat back to Standard from Permissions. Turning the setting off affects new chats; it does not turn off Full access in existing chats.

Return to Standard or remove saved approvals

Select Full access beside the input, then Standard. Bearly withdraws Full access and stops current work where it can. Actions already completed outside Bearly are not undone.

Changing modes keeps your earlier saved approvals. Review them under Saved approvals in the same panel. In Standard, select Revoke beside one, or Revoke all saved approvals, to stop current work and ask again for those actions. Clear all permissions switches to Standard and removes every saved approval together. Stop by itself ends the current task without changing your permission mode.

Choose full access for a routine

A routine does not inherit Full access from its chat. Save the routine first, then use Tools → Permission mode in its editor on the desktop device that runs it. Select Enable full access and review the warning and selected tools before confirming. Enabling it stops any current run and leaves the schedule unchanged.

Routine consent stays on across app restarts and time away. Each run still needs current authorization and can use only the supported tools and accounts selected for that routine. Changes to its saved instructions, schedule, model, delivery settings, tools, or selected connector and skill setup require review. Full access needs review means the routine cannot continue in that mode until you approve its current setup. If its schedule has paused, select Resume after reviewing. Copying or moving a routine starts it in Standard.

Use Standard withdraws routine Full access and stops current work on its running device while keeping existing per-tool unattended permissions, including local or browser access you enabled separately. Standard routines can still use those permissions without asking. Stop run keeps the mode and schedule. A change made from web, mobile or another computer applies when it syncs to the running device. Those other devices can manage the routine, but Full access must be enabled on its installed desktop device.

Routines cannot use Computer Use, Google Workspace or Chrome DevTools in either mode. Their browser tools keep their own tabs and stay on the sites and actions approved for the routine. See Run prompts on a schedule with Routines for the complete setup and limits.

Manage full access for an organization

Organization administrators manage eligibility for members on the organization’s managed domain. Group administrators cannot grant Full access.

1. Open the account menu, select Organizations, then select your organization.
2. On Overview, find Agent access.
3. Set Allow full access by default. It’s on unless an administrator turned it off.
4. To set an exception, open Members, select the member’s Member settings gear, and choose Use organization default, Allow full access, or Do not allow full access under Full access. This setting saves immediately.

The default applies to members using Use organization default. Individual Allow full access or Do not allow full access choices take precedence, so turning off the default alone does not remove individual allowances.

An allowed member still chooses whether to enable Full access for a chat or separately for a routine. This setting is separate from ordinary feature policies; allowing Full access does not enable tools that your organization has disabled.

To withdraw eligibility across the organization, select Turn off for everyone under Agent access. Review the current number of eligible members, then confirm. This turns off the default and removes individual exceptions. Full access authorization for active chats and routines ends within 60 seconds; saved approvals for individual tools remain. Previously authorized external actions may already have taken effect. Routines require a new review before using Full access again. Changes appear in organization Activity.

If settings cannot load or another administrator changed them, select Reload before trying again. In the confirmation dialog, use Reload affected members to check the count again. An unavailable setting does not grant access.

For the tools themselves, see Work locally, Computer Use, Browser, and Connectors.