Product settings

Product settings are the admin lever room, one section below for each page. Since the September 2026 settings redesign they sit where their subject lives: Settings → Workspace → Time periods and Tags, Settings → Goals → Check-ins, Advanced features, Terminology and Progress & logic, Settings → AI & agents → Capabilities, and Settings → Features → Digest & briefs, Artifacts and the three request pages. Only org admins and owners see these rows; anyone else who opens one of these addresses is sent back to the app. Most switches here affect every user in the org, and a switch saves the moment you flip it. They used to share a single Product page; a link to that page now opens Workspace → General, which holds your company profile.

Time periods (planning rhythm) #

• Business Cadence: shows Quarterly, the planning rhythm your time periods are generated on, and cannot be changed here today. Which of those periods a view filters to by default is controlled by Default Period Filter below.
• Custom Fiscal Year Start: turn it on if your fiscal year doesn't start January 1, then click the date to pick a month and day and Save. Brev shows what will change in 'Update Fiscal Year Configuration?' before it re-dates your quarter, half-year and year periods; month and custom periods are left alone. Turning it off from a date other than January 1 asks the same way. Known issue: after a change, the period marked Current is not moved to the one that now contains today, so check the Current badge and set it again with 'Set as current time period'.
• Default Period Filter: which Active time periods a view falls back to when it has no saved filter. Most granular active periods (the default) uses only your finest-grained Active periods, so if both quarters and fiscal years are Active you'll see the quarters and annual goals are hidden. Pick All active periods if you run annual and quarterly plans side by side and want both visible by default. A view where someone deliberately picked time periods keeps those periods; a view that just used the default keeps following it as periods roll over.
• Time Periods: every period as a badge, grouped by type. Hover a badge for 'Set as current time period', which marks it as the active period of its type (e.g. 'Q2 2026 (Current)'), and 'Edit time period', which renames it or changes its dates. The + at the end of a row adds the next period of that type. Add Time Period creates one of your own: give it a name, a type (Month, Quarter, Half Year, Year or Custom), a status and its dates. Known issue: a new period with the same name as an existing one is not saved and no error appears, yet a badge for it still shows in your browser, even after a reload. Give each period a unique name.
• Set from a goal import: if an import's goals are all for a period that is not your active one, it offers to switch before it drafts any goals, naming both periods (for example 'Your file's goals are for Q1 2027, but your active period is Q3 2026'). It suggests one period from the file, preferring a quarter, then a half, then a year, and the one closest to today. Accepting is the same change as 'Set as current time period' here, so it needs an organization admin (see Roles & permissions); anyone else is offered the option to leave the active period alone. If you switch, goals in the file that name no period go into the period you switched to, even when a year is also active. Nothing is asked when the import already includes your active period, when you have no active period set, or when the file names no period this workspace has. A period the file names that this workspace does not have by name, but whose dates are exactly those of one of your periods (FY26 running 1 January to 31 December 2026, when you have a 2026 year), is filed into that period without a question, and Operator says so in its plan. Failing an exact match, so is one whose name matches one of your periods and whose start and end are each within one calendar day of it, and the plan says its dates differ slightly. Only dates in the file's own date columns count, and if two of your periods match equally well you are asked.

To delete a time period, hover its badge, click 'Edit time period', then Delete. A period with no goals on it asks you to confirm with 'Delete time period'. If any goals sit on that period, the delete dialog asks what to do with them first. You must choose either Move to another time period (pick a period; each goal's dates update to match it) or Delete these goals (permanently deletes each goal and all of its sub-goals). Archived goals on the period are counted and handled too, and are listed separately so the number matches what you can see.

Tags #

Settings → Workspace → Tags lists every tag in your workspace, the same tags members put on goals and actions. Type in the filter to narrow the list by name.

• Rename: click a tag's name, edit it, then click away or press Enter. The new name saves straight away and shows everywhere the tag is used. Two tags cannot share a name, ignoring capitalisation.
• Change color: click the colored dot beside a tag and pick one of ten colors.
• New tag: type a name in the new row and press Enter. Press Escape to cancel.
• Delete: open the ... menu on a row and choose Delete tag. The tag is removed from every goal and action that uses it, and this cannot be undone.

Check-ins (reminders) #

• Check-in rhythm: a switch plus a schedule button (e.g. 'Mon at 08:30', 24-hour time). Click the schedule to pick the day, time and time zone; it saves when you close it.
• Email reminder: fires per the rhythm to every member with active goals. This row only shows while the rhythm is on.
• Slack reminder: same as email, but via Slack DM. The switch is greyed out until Slack is connected ('Connect Slack to receive reminders').
• Teams reminder: same as email, but as a Microsoft Teams 1:1 message. Greyed out until Microsoft Teams is connected.
• Test Run: Test sends a one-off check-in reminder to yourself across your enabled channels (email, Slack, Teams) so you can preview the copy. It shows while the rhythm is on and at least one channel is switched on. If your Slack or Teams connection needs attention, a Reconnect Slack or Reconnect Teams button takes its place.

Turning the rhythm off hides the schedule, the Email reminder row and Test Run. Turning it back on starts again from Mon at 08:30 with the email reminder off, so switch that back on by hand.

The Slack and Teams switches stay available whether or not you have a check-in rhythm turned on. They decide which chat platforms Brev may message your members on, and turning the rhythm off no longer switches them off for you.

A new organization starts with the Slack and Teams switches off. Connecting Slack turns the Slack switch on, whether an admin connects it from Integrations or a member's AI coworker connect is what adds Brev to your Slack. A member connecting their coworker to a Slack that is already set up leaves the switch as it is, so a switch an admin turned off stays off. An admin connecting Microsoft Teams turns the Teams switch on. Finishing onboarding sets the check-in rhythm and the email switch and leaves both chat switches as they were.

Digest & briefs #

Settings → Features → Digest & briefs has two switches, both off until an admin turns them on: Daily briefing (one message each weekday around 9am) and Weekly digest (one message on Monday morning). They are org-wide, and separate from each person's own Daily briefing switch in Notifications. Sending also needs the feature to be enabled for your workspace by Brev, so if a switch is on and nothing arrives, contact support.

The daily briefing goes out on whichever chat platform you have connected, Slack or Microsoft Teams, as one message per person, once a day, Monday through Friday. Weekends are quiet, and most of what comes up on a Saturday or Sunday is carried into Monday's briefing, though a briefing shows a few things at a time, so a busy weekend may not all fit. If both platforms are connected, people get it in one place, not two. It does not count against the usual limit on how many messages a person receives in a week. Where your organization has the AI coworker's daily rhythm, a person whose Slack coworker sends them its own daily brief gets that instead of this one.

People you have invited but who have not signed in yet get the briefing too, as long as they are reachable on your connected chat platform under the email you invited them at. They have nothing of their own yet, so theirs carries what the company has been doing. It is the only chat message they get, everything else waits until they sign in, and it stops about a week after they were invited, when the invitation expires. Re-sending an invitation does not start it again. People added without an invitation, and people whose access has been turned off, receive nothing either way.

The weekly digest arrives the same way, one message per person on whichever chat platform is connected, and it does not count against the weekly message limit either. It carries a link to a private page written for whoever received it: what the company worked on last week, ordered by what mattered most, anything Brev thinks is worth a look, and that person's own goals below. Only the person the message was sent to can open their page.

Capabilities (Brev AI) #

Settings → AI & agents → Capabilities. Switches you can turn on and off:

• Suggested Check-ins: the AI-drafted check-in offered in the check-in dialog, and the suggested check-in card on a goal's check-in timeline.
• AI Goal Insights: generated commentary on each goal detail page.
• AI Goal Coach: AI help in the goal dialog: title autocomplete, and, when you create a new goal, a suggested goal you can apply. Editing an existing goal never generates a suggestion. Turning it off removes both.
• Child Goal Suggestions: quick-cascade AI proposals when you create a parent goal.
• AI Summary: summarizes progress on company and team dashboards.
• Prompt Recipes: lets view owners steer what the AI writes for a view, from the digest Insights card and the AI Summary sheet. Off by default. See Views. Dismissing a bad generated version is separate and stays available with this off.

Three more rows are available by request. Each carries a BETA tag and a switch you cannot flip, with a Contact sales to enable link to the demo request page; once Brev turns one on for you, the row shows it as on:

• Meeting Guidance: adds anti-pattern detection and forward-motion analysis to meeting recaps.
• Meeting Insights: detailed metric breakdowns + expandable sub-metrics for meeting scores.
• Status Provenance: shows who set a goal's status, when, and on what evidence.

There is no switch for the Operator chat page: this page does not turn it on or off.

Terminology #

Toggle 'Custom Terminology' to relabel goals, metrics and projects org-wide (e.g. call them 'Objectives', 'Key Results' and 'Initiatives' instead). The renaming propagates to every surface, including AI prompts and Operator replies.

Framework is the goal-setting framework your organization uses, the name for all three together, which the sidebar, breadcrumbs and preset views ('My Goals', 'Company Goals') call 'Goals' by default. Set it to 'OKR' and those read 'OKRs', 'My OKRs' and 'Company OKRs'. Enter the singular; the field shows the plural it will use, and warns past 12 characters because longer names get cut off in the sidebar and page headers. Links and page addresses don't change.

Progress & logic #

Default roll-up basis sets how every parent goal's progress is calculated from its children, org-wide. Time-based coverage (the default) weights each child by how much of the parent's time window it spans and counts uncovered time as 0%; Equal weighting averages all children equally, ignoring dates. Individual goals can override this from their roll-up control: see How parent progress rolls up.

Advanced features #

Toggles that change how the goal tree works org-wide. Each one is off by default; an Org Admin flips them on when the org is ready for the extra concept.

• Multiple Alignment: allow a single goal to roll up to more than one parent.
• Shared Ownership: let two or more people co-own a goal. Each co-owner can edit and check in.
• Shared Team Ownership: let a single goal belong to multiple teams (it shows up in each team view).
• Projects: shown as coming soon. Its switch is greyed out, with a line under it saying to contact [email protected] for access.
• Milestones: track checkpoints within a goal, metric, or project.
• Goal Weights: weighted rollups, so some child goals contribute more to the parent's progress than others.
• Private Goals: limit visibility on a specific goal to the owners + sharers, instead of org-wide.
• Tags: categorize and filter goals using free-form labels.
• Advanced KPIs: enable the Stay above / Stay below / Stay between tracking modes for metrics. Any org admin can turn it on, and every member then gets the modes.
• Advanced Filters: replace the goal view filter chips with a filter bar under the Goals header where each condition reads field / operator / values, including exclusion operators like "Is not" and "Is none of". Once on, every member gets the new filter bar; off, goal views keep the classic filter chips.

Each switch saves straight away; if it cannot be saved, an error appears and the switch flips back.

Artifacts #

Settings → Features → Artifacts holds one switch, Artifacts Home. On (the default) your workspace keeps the Artifacts row in the left sidebar, which opens a page listing every artifact your team has generated: who created it, when, and which cadence it belongs to. Off, that row disappears for everyone in the org, and so does the Artifacts result in Settings search. Admins and owners only.

Features your plan doesn't include yet #

Settings → Features → Company brain, Settings → Features → Execution signals and Settings → Features → Daily briefing each cover a feature that is sold separately, so those pages have no settings on them yet. Each shows a banner naming what the feature does, with a Request access button. The dialog asks what the feature would unlock for you; the answer is optional. Sending it shows 'Request sent' and records the request for the Brev team, who follow up about enabling it; Cancel closes the dialog without recording anything. Nothing about your workspace changes on its own. Once your request is in, the button reads 'Feature requested' and stops being clickable, and it stays that way when you come back to the page; it is per feature and per person, so a colleague's request does not spend yours. Only admins and owners can open these pages: see Roles & permissions.

Known issue: these pages show their banner and Request access button even when your workspace already has the feature turned on.

Reports and Usage used to sit under Settings → Workspace. They are now their own pages in the app: see Reports.