Revvly
Docs
Reference

Workspace features and what they unlock.

Every workspace feature, what it gates, who can turn it on, and what you see when it is off. Workspace features are separate from the product feature flags you attach to modules and bundles, which are covered in section 06.

01How workspace features work

Where it is stored
A list of features on your Tenant (workspace). The dashboard reads the list for the workspace you have selected.
Who can grant
Only a Revvly platform admin. The control is the Access and features card on the client record, and the API call behind it rejects anyone who is not a platform admin. A workspace admin cannot turn a feature on for their own workspace.
What can be granted
The features listed in section 02. Asking the API to grant any other feature is refused. Features a workspace already holds outside that list are left untouched when these are changed.
Platform workspace
The Revvly platform workspace holds every grantable feature. That is reconciled on every boot.
Default set
A regular workspace without a stored list is treated as holding the nine standard features in section 03. None of the grantable features is in the default set.

02Features Revvly grants

Each of these is off until a platform admin turns it on. The name is the label on the grant card; the code is the value the API uses.

CRM
CRM
Gates Companies, Contacts and Pipeline in the Customers menu. The CRM API behind them: pipelines and stages, leads, notes, documents, meetings, email logging, lifecycle stage and owner. CRM import, CRM email templates, booking intake routes, Gmail connection and email signatures, Calendly connection, contact suggestions, email thread visibility, and contacts on a client. The public API mutation createProspect. Library documents and the Library Documents screen are open to CRM or Support.
Granted by Revvly platform admin only.
Note Tasks are available to every workspace and are not gated by CRM. The first time CRM is granted, a default pipeline is seeded.
Billing schedules
BILLING_SCHEDULE
Gates The prepaid-term and deferred-activation presets on the subscription wizard, the pending-activation list on Renewals, and the Activate action.
Granted by Revvly platform admin only.
Note Only the schedule surfaces are gated. Credit notes, typed invoice lines and cash-flow projections that skip invoiced-ahead periods work without it.
OKRs
OKR
Gates The OKR API (cycles, objectives, key results, work links, alignment) and the OKR Cycle, My OKRs and Coverage entries under Strategy.
Granted by Revvly platform admin only.
Note Granting it is the commercial step. A workspace admin must also turn the module on under Settings, Modules; until then the API answers that OKRs are not switched on for the account.
Email triage (Tier 1)
EMAIL_TIER1_TRIAGE
Gates The hourly AI pass that classifies inbound email the first-stage rules escalated. No screen is gated.
Granted by Revvly platform admin only.
Note A workspace is swept only if it carries this feature and Revvly has configured the triage model and a positive monthly budget. Either one missing means nothing runs.
Commitment extraction (Tier 2)
EMAIL_TIER2_EXTRACTION
Gates The hourly AI pass that reads triaged email for commitments, which feed overdue-commitment situations. No screen is gated.
Granted by Revvly platform admin only.
Note Independent of Tier 1, but it only sees messages Tier 1 has qualified. Also needs the extraction model and a positive monthly budget configured by Revvly.
Support
SUPPORT
Gates The Support section (Inbox, End users, Knowledge, Metrics) and every Support API: tickets, settings, knowledge, imports, metrics, notifications, work-item links, the live stream and the sandbox. On the public API, createEndUserToken, upsertSupportUsers, the knowledge mutations and workItemLinks. Library documents (CRM or Support) and sharing a library link from a ticket.
Granted by Revvly platform admin only.
Note The first time Support is granted, ticket types, workflows and settings are seeded.
Forms
FORMS
Gates Library, Forms; the form builder API; the Assistant and MCP form tools; public hosted and embedded forms; the API-key mutation submitForm; and the runner for follow-up steps on each submission.
Granted by Revvly platform admin only.
Note If a workspace loses Forms, its public form routes answer 404 and steps still waiting are held, not run.
Daily check-ins
CHECKINS
Gates Settings, Check-ins and the check-in API behind it; the daily Slack direct messages, the answers and summary posted to each check-in’s channel; the /revvly standup command; and the Assistant’s check-in tools. Admins only. See Run daily check-ins in Slack.
Granted by Revvly platform admin only.
Note Entitlement does not need a Slack connection, so a workspace can set check-ins up first, but nothing is sent until Slack is connected. A disconnected Slack pauses every check-in.
Tax
TAX
Gates Settings, Tax; the Tax tab on Finance; the tax panel on draft invoices; the tax API (settings, registrations, rates, customer tax profiles, reports, ledger).
Granted by Revvly platform admin only.
Note Granting is the entitlement. The workspace then switches tax on in its own tax settings, which is refused until an active registration exists. Nothing on an invoice changes before that.
Work Inbox
WORK_INBOX
Gates Inbox at /inbox and its settings, the daily inbox digest notification preference, and the Assistant and MCP inbox tools. See Work Inbox.
Granted by Revvly platform admin only.
Note Each person connects their own Gmail mailbox, and nobody sees anyone else’s mail.
Drive client folders
DRIVE_FOLDERS
Gates A Google Drive folder per client and prospect, kept in sync with the files Revvly holds: the client folders settings under Settings, Integrations (admins), the folder panel and Drive marks on a client’s documents, and the paused-sync notification. See Client folders in Google Drive.
Granted by Revvly platform admin only.
Note Needs Google Drive connected with write access to do anything; entitlement does not require it.

03Standard features

Regular workspaces start with these. They cannot be switched off from the grant card. Only Finance is checked in the code today; the rest are recorded on the workspace but no screen or API call depends on them.

Finance
FINANCE
Enforced in the API: payment reminders and reminder templates, invoice payments, credit notes and the accounting mailbox. In the dashboard: the Templates page and the payment-reminder entries in search.
Subscriptions
SUBSCRIPTIONS
No backend check and no dashboard check found.
Organizations (Clients)
ORGANIZATIONS
No backend check and no dashboard check found.
Analytics
ANALYTICS
No backend check found; the dashboard FeatureGate component names it but no screen depends on it.
Feature flags
FEATURE_FLAGS
No backend check and no dashboard check found.
Product config
PRODUCT_CONFIG
No backend check and no dashboard check found.
Market config (Regions)
MARKET_CONFIG
No backend check and no dashboard check found.
Pricing
PRICING
No backend check and no dashboard check found.
Import
IMPORT
No backend check and no dashboard check found.

04Structural and deprecated

Tenant management
TENANT_MANAGEMENT
Held by the Revvly platform workspace. Not grantable. No backend or dashboard check on this value was found.
Incubators
INCUBATORS
Not grantable. The Incubators menu entry is commented out in the dashboard and the incubator routes redirect to Dashboard, so the feature unlocks nothing you can see.
User management
USER_MANAGEMENT
Not grantable. The accelerator-specific Users menu entry is commented out. The Users page under Admin is shown to every workspace regardless of this value.
Auto renewal
AUTO_RENEWAL
Deprecated. It gates nothing. Renewals run for every active workspace; whether one subscription renews is decided by its own auto-renew setting. The value is kept only so older workspace records stay valid.

05What you see when a feature is off

Menu and search
The entry is not shown in the sidebar or in the command palette. A group with several entries, such as Library, shows only the ones you hold.
Typing the URL
Guarded routes redirect to Dashboard. Settings, Tax and Settings, Check-ins fall back to Settings, General.
Calling the API
Dashboard GraphQL operations answer 403 with: The "CRM" feature is not enabled for this tenant (the message names the feature). Operations open to either of two features list both. On the public API, the CRM, Forms and Support operations answer 403 FORBIDDEN with a message that says the product is not enabled for this tenant.
Public forms
A workspace that loses Forms takes its public form routes offline (404) and holds pending follow-up steps.
Entitled but not switched on
OKRs and Tax need a second step by the workspace after the grant. Until then the feature is available and the module reports that it is not switched on.

06Product feature flags are a different thing

A Feature Flag in the catalog is a capability you sell, such as advanced reporting. It describes what your customers have. It does not switch Revvly screens on or off for your own team.

Where
Catalog, Feature Flags in the Admin menu.
Fields
Name, key (the identifier your own application reads), description, optional category, and an active switch.
Entitlements
Flags are attached to Module tiers and to Bundles.
Per client
A client’s flag assignment records its source: bundle, module or manual. Manual assignments can enable or remove a single flag for one client.
Who edits
Writes to the flag catalog and to a client’s assignments require a workspace admin, not just membership.
Sync to your app
API mutations can push a client’s manual assignments to an external application and pull flags from it. The target is set by Revvly deployment configuration, not in workspace settings, and the current dashboard has no screen for it. Nothing in Revvly reads these flags to change what a screen shows.