Skip to content

Experimental features (beta)

Some capabilities ship in beta before they land on your paid tier. You choose what to try — nothing turns on without an explicit opt-in.

  1. Sign in at app.arborbuddy.com.
  2. Go to Settings → Beta features (owners and dispatchers only).
  3. Read the disclaimer, check the box, and click Enable beta access.

The tab only appears when ArborBuddy has at least one beta feature open for preview. If you do not see it, nothing is in active soak for your workspace yet.

One disclaimer covers every beta:

I understand this is experimental. It may change, break, or require a paid upgrade when released.

We store which version you accepted. If we update the legal copy, you will be prompted to accept again before the feature stays on.

If you are below the feature’s normal tier (for example, Crew previewing something that ships on Autopilot or Canopy):

  • You get a free preview per feature from the day you opt in.
  • During the preview, the feature behaves as if you met the tier requirement.
  • When the preview ends, access turns off unless you upgrade.

If you are already on the required tier, the feature is included in your plan — no beta opt-in needed.

SituationWhat happens
You upgraded to the required tierKeep using the feature — no interruption.
You are still below tierFeature turns off. Settings → Billing shows an upgrade path for the tier you need.
You want to stop earlySettings → Beta featuresRevoke beta access.

We do not grandfather cross-tier beta users at general availability. Upgrade to the listed tier, or ask support for a one-off override (filming, migration help).

Enabled betas carry a Beta badge on the surface they unlock — for example Settings → Integrations for calendar import or webhooks.

Beta is not a secret tier. It is a time-boxed preview so you can test real workflows before you commit on billing.

RoleBeta features tab
OwnerYes — can opt in, revoke, and upgrade
DispatcherYes — can opt in and revoke
Field leadNo — mobile field view only

Some betas read or write third-party data (Google Calendar events during import, webhook payloads, and similar). We only process that data to provide the feature you opted into. See our Privacy Policy for how beta integrations are handled.