Feature availability matrix

Performance Blocks ships with a single set of features and exposes most of them as feature flags that org admins toggle in Settings → Features. This article documents every flag, which plan it ships on, which role can use it, what it depends on, and whether it is on by default.

If you are new to feature flags, read the area summaries first, then come back to the matrix.

How to use this page

• Plan column (Team / Agentic) — whether the flag is available to enable on that plan. Available does not mean on by default.
• Required role — the lowest role that can use the feature once it is enabled. Org admin rows are admin-only surfaces.
• Depends on — other flags that must be enabled first. The product enforces these dependencies; you cannot enable a flag whose prerequisites are off.
• Default state — whether the flag is on by default for new tenants. Most advanced features default off so admins make a deliberate choice.

Toggle a flag at any time. Disabling a flag hides the related surfaces but does not delete data. Re-enabling restores it.

Full feature matrix

Feature flag	Team	Agentic	Required role	Depends on	Default state
feedbackAssignment	Yes	Yes	Manager	employeePortal	Off
attributes	Yes	Yes	Manager	—	On
managerAttributes	Yes	Yes	Manager	attributes	Off
objectives	Yes	Yes	Manager	—	On
managerObjectives	Yes	Yes	Manager	objectives	Off
employeeObjectives	Yes	Yes	Employee	objectives, employeePortal	Off
aiGeneratedConversations	Yes	Yes	Manager	—	On
aiGeneratedSummaries	Yes	Yes	Manager	—	On
teamSummaries	Yes	Yes	Manager	—	On
shareConversations	Yes	Yes	Manager	employeePortal	Off
shareSummaries	Yes	Yes	Manager	employeePortal	Off
employeePortal	Yes	Yes	Employee	—	Off
employeeFeedback	Yes	Yes	Employee	employeePortal	Off
henryAgentEnabled	No	Yes	Org admin	—	Off
henryAgentApp	No	Yes	Manager	henryAgentEnabled	Off
henryAgentTeams	No	Yes	Manager	henryAgentEnabled	Off
henryAgentSlack	No	Yes	Manager	henryAgentEnabled	Off
henryAgentChrome	No	Yes	Manager	henryAgentEnabled	Off
henryAgentEmail	No	Yes	Manager	henryAgentEnabled	Off
aiKnowledgeBase	No	Yes	Org admin	henryAgentEnabled	Off
henryAnalytics	No	Yes	Org admin	henryAgentEnabled	Off
sso	No	Yes	Org admin	—	Off
hrisIntegration	No	Yes	Org admin	—	Off
apiKeys	No	Yes	Org admin	—	Off
skipLevelSummaries	No	Yes	Manager	teamSummaries	Off

Feature areas explained

Features fall into five functional areas. Each area below explains what the flags in that group do, when to enable them, and what an admin should consider.

Core performance management

These flags govern the day-to-day workflow of managers capturing observations, running conversations, and producing summaries.

• attributes — controls whether managers can tag observations with org-defined attributes (sometimes called competencies). Enabled by default; disable only if your org has not yet defined an attribute set and wants a clean UI.
• managerAttributes — adds a manager-specific attribute axis on top of attributes. Useful when promotion criteria for managers differ materially from individual contributors.
• objectives — turns on the objectives feature at the organization and manager levels. Enabled by default. Disable only if your org tracks goals exclusively in another system.
• managerObjectives — lets managers set objectives for their own team beyond org-wide ones. Requires objectives.
• employeeObjectives — exposes objectives in the employee portal so employees can author and update their own. Requires both objectives and employeePortal.
• teamSummaries — enables manager-level summaries that aggregate multiple direct reports. Required for skip-level summaries.

For more on the underlying model, see observations and blocks and summaries.

AI authoring (in-app drafts)

The Team plan includes AI drafting features built directly into the app. These are distinct from the Henry agent surfaces.

• aiGeneratedConversations — drafts a conversation agenda from recent observations.
• aiGeneratedSummaries — drafts a summary from observations across a date range and attribute set.

Drafts are starting points; managers always review and edit before saving or sharing. Disable these flags if your org's data policy requires that all written content be authored from scratch.

Employee-facing surfaces

These flags govern what employees see and can do in their own portal.

• employeePortal — turns on the employee portal at all. This is the prerequisite for every other employee-facing flag.
• shareConversations — when a manager marks a conversation as shared, it appears in the employee's portal.
• shareSummaries — same as above for summaries.
• employeeFeedback — allows employees to submit feedback (for example, on a shared summary) back to their manager.
• feedbackAssignment — lets managers assign specific 360 feedback prompts to peers via the portal.

Many organizations roll out the employee portal in a second phase. Enable employeePortal first; the dependent flags become available immediately afterward.

Henry Agent and AI assistants (Agentic only)

Henry is the conversational AI surface. All Henry flags are Agentic-only.

• henryAgentEnabled — the master switch for Henry. All other Henry flags require this.
• henryAgentApp — Henry panel inside the Performance Blocks web app.
• henryAgentSlack — Henry as a Slack app (channel mentions and DMs).
• henryAgentTeams — Henry as a Microsoft Teams bot.
• henryAgentChrome — Henry Chrome extension for capturing from any web page.
• henryAgentEmail — forward content to a per-tenant Henry email address to draft observations.
• aiKnowledgeBase — knowledge base ingestion and RAG retrieval. Henry will ground responses in your uploaded documents when relevant. Requires henryAgentEnabled.
• henryAnalytics — admin dashboards showing Henry usage, intent breakdowns, and quality signals. Requires henryAgentEnabled.

When you first enable Henry, we recommend a phased rollout: enable henryAgentEnabled and henryAgentApp first, train managers, then enable Slack or Teams. See Henry rollout guide.

Admin and analytics

• skipLevelSummaries — managers of managers can view aggregated summaries from their indirect reports. Requires teamSummaries and is Agentic-only because it draws on Henry's analytics layer for aggregation.
• henryAnalytics — see the Henry section above.

Identity and integrations (Agentic only)

• sso — single sign-on via SAML or OIDC. Once configured, you can require SSO for all sign-ins or allow magic link as a fallback.
• hrisIntegration — sync employees, reporting lines, and departments from your HRIS (Workday, BambooHR, Rippling, Gusto, and others). Configure connections in Settings → Integrations.
• apiKeys — issue API keys for programmatic access. Each key is scoped (read-only or read-write) and rate-limited.

Dependency rules in plain language

The product enforces these rules at the toggle level — disabling a parent flag hides dependents in the UI:

• feedbackAssignment requires employeePortal. Feedback assignments are delivered through the employee's portal.
• managerAttributes requires attributes. Manager attributes layer on top of the base attribute model.
• managerObjectives requires objectives. Manager objectives extend the objective system.
• employeeObjectives requires objectives and employeePortal. Employees author objectives in their portal.
• shareConversations, shareSummaries, and employeeFeedback all require employeePortal. They are portal surfaces.
• skipLevelSummaries requires teamSummaries. Skip-level rollups aggregate team summaries up the management chain.
• All henryAgent* surface flags require henryAgentEnabled. Disabling the master flag turns off every Henry surface in one action.
• aiKnowledgeBase and henryAnalytics require henryAgentEnabled. Both are Henry capabilities.

If you try to disable a parent flag while dependents are enabled, the product will warn you and prompt you to disable the dependents first.

Defaults and rollout sequence

For new tenants, the on-by-default flags are: attributes, objectives, aiGeneratedConversations, aiGeneratedSummaries, teamSummaries. Everything else is off so admins make a deliberate choice.

A typical rollout sequence is:

1. Week 1 — Confirm the on-by-default flags fit your org. Define attributes if you have not.
2. Week 2 — Train managers on observations, conversations, and summaries.
3. Week 3 — Enable employeePortal. Communicate what employees will see.
4. Week 4 — Enable shareSummaries and shareConversations. Roll out manager guidance for sharing.
5. Week 5+ — Add feedbackAssignment, employeeFeedback, employeeObjectives as your practice matures.
6. Agentic only — Enable Henry surfaces one at a time, starting with henryAgentApp.

Auditing flag changes

Every flag toggle is recorded in the audit log with the actor, timestamp, previous state, and new state. To review:

1. Open Settings → Audit log.
2. Filter by event type feature.flag.toggle.
3. Export to CSV if you need a record for compliance.

Audit log entries are immutable and retained for the lifetime of the tenant. See audit logs for details.

Related reading

• Plans and pricing — what each plan includes and how billing works.
• Glossary — definitions for terms used in this matrix.
• Admin overview — where to find each settings surface.