Skip to content

Feature flags

Enable or disable optional platform features for your company without needing a release.

Required role

Admin.

Overview

Feature flags let your company opt into (or out of) specific platform features without a code change. Each flag controls one cohesive feature — a new report, an alternative mobile workflow, an integration — and defaults to a value chosen by Pegotec.

Typical uses:

  • Rolling out a new feature gradually — early adopters flip on while the rest wait.
  • Disabling a noisy feature — turn off a notification category or UI element that doesn't fit your workflow.
  • Trial before commitment — try a beta feature for a week and decide whether to keep it.

Not every optional behaviour is a flag. Pegotec surfaces flags for features that are:

  • Stable enough to offer.
  • Optional in the sense that some tenants would reasonably want them off.
  • Tenant-scoped (applies cleanly per company, not per user).

Prerequisites

  • You have the Admin role.
  • You have the authority to toggle a feature on behalf of your company (some flags have wider implications — read the description before flipping).

Open the Feature Flags page

Settings → Feature flags. You see a list of available flags:

Column Meaning
Flag Short name (e.g. advanced_scheduling).
Description What the flag does in plain English.
Status On / Off for your company.
Default Pegotec's default for new tenants.
Since When the flag first became available.

Enable or disable a flag

  1. Find the flag in the list.
  2. Click the toggle.
  3. Confirm.

The change is immediate for most flags — users see the new behaviour on their next page load. A few flags (e.g. ones that change data structure) require a sync on mobile devices; the UI flags these with a note.

What happens when you flip a flag

  • Users signed in at the time see the change on their next page load (or next mobile sync).
  • The change is logged in the activity log with your user ID.
  • Reports that reference flag-gated features update immediately.

Common flags (examples)

Names and availability vary by installation. Typical categories:

UI flags

  • Alternative navigation layouts.
  • Optional dashboard widgets.
  • Advanced filter panels.
  • Bulk-action bars on list views.

Workflow flags

  • Simplified vs detailed task submission.
  • Auto-assign on schedule generation.
  • Required photos on shutdown reports.
  • Dual-approval for high-cost repair requests.

Integration flags

  • Webhook auto-retry behaviour.
  • External CMMS handoff on shutdown.
  • SSO-only sign-in (disables password login).

Beta flags

  • Features in pre-release. Usually off by default.
  • Flags labelled "beta" may change behaviour or go away between releases.

Reading a flag description

Every flag's description tells you:

  • What it does — the user-visible effect.
  • Who is affected — all users / specific roles / mobile only / etc.
  • Whether it's safe to flip back — almost always yes; if not, the description says so.
  • Any setup required before enabling — e.g. "requires webhook URL configured in Settings".
  • Link to the relevant handbook page where available.

Don't flip a flag whose description you don't understand. Talk to Pegotec support first.

Flags that affect data

Most flags are cosmetic or workflow tweaks. A few flags change what data is captured:

  • Turning on "required photos on shutdown" adds a validation; existing data is untouched.
  • Turning off "run-hour-based scheduling" doesn't delete existing run-hour schedules but stops generating new instances.
  • Turning on "audit email sign-ins" begins logging sign-ins but doesn't back-fill.

For data-affecting flags, the description explicitly flags it as such.

Things to watch for

Don't flip flags during business hours without testing

A flag that changes a user's workflow will surprise them mid-task. Flip during low-traffic windows, or on a staging installation first, where available.

Read the description even if the name seems obvious

"Strict submission" sounds self-explanatory — until you realise it rejects partial drafts that your team relies on. The description spells this out.

Flags are company-wide, not per-user

You can't enable a flag for one user as a trial. Everyone in the company sees the same set. For per-user variants, use custom roles and permissions.

Troubleshooting

Problem Fix
Flag toggled but no change visible Refresh the page; for mobile users, force a sync
Flag name unclear Check the description; contact Pegotec support if still unclear
Toggle greyed out Some flags require a higher-tier account or SSO setup — description says which
Don't see the Feature flags menu Your role may not include settings.edit — request from an Admin