SETTINGS | GENERAL

Preferences

How organization-wide defaults, workflow modes, fiscal timing, support access, and retention rules are configured in Scale B.O.S.S.

Why this page matters

Preferences is where Scale B.O.S.S. transitions from a generic platform into your organization's operating system. Settings here affect the entire organization: what users can access, how evaluation journeys appear, when AI reports are generated, how fiscal periods are labeled, and when completed work is automatically cleared from active views.

This guide covers	Why it matters
How each Preferences card works	So administrators can configure the platform intentionally rather than by trial and error
What each setting changes downstream	So operational, reporting, and support consequences are visible before a change is made
What well-configured settings look like	So the page serves as an operating standard, not just a settings screen

Audience: Strategy Team members and platform administrators responsible for organization-wide setup and operating defaults.

Page overview

Preferences sits inside Settings > General and functions as the policy layer for the rest of the system. Rather than holding day-to-day work, it governs how work behaves: who can access support, whether evaluation types open in guided or hub mode, when weekly AI reports run, how fiscal periods are labeled, and how quickly completed work is archived from active boards.

Administrative impact

These are organization-wide controls. Review them deliberately, communicate material changes, and verify the downstream experience immediately after any update.

How to get there

• Open the account menu from the avatar in the top-right corner of the application.

• Select Settings.

• Stay in the General settings area.

• Open the Preferences sub-tab.

Figure 1. Preferences is accessed through the account menu under General settings.

What this page controls

Card	Primary function	Typical questions it answers
Features	Turns key organization-wide capabilities on or off	Should Notes & Todos be available? When should weekly AI reports run? Should users activate manually?
Support	Controls who can use support ticketing and how updates are delivered	Which roles can submit tickets? Should updates appear in-app, by email, or both?
Evaluate Journeys	Switches TM, BE, and KBD between guided setup and hub mode	Are teams still learning the framework, or ready for a management-first view?
Fiscal Year	Defines how time is labeled for reporting, goals, and KPI rollups	Does the organization operate on a calendar year or a fiscal year?
Auto-Archive	Sets retention windows for completed or rejected items	How long should finished or rejected work remain visible before being archived?

Figure 2. The Preferences workspace is organized into five administrative cards.

Features

The Features card controls product capabilities and onboarding behavior that shape the everyday user experience across the organization.

Figure 3. Features controls Notes & Todos, Weekly Insight Reports, and Manual User Activation.

Setting	What it changes	What an admin should decide
Notes & Todos	Makes the personal notes and task workspace available to users throughout the platform.	Should team members manage lightweight personal follow-through inside Scale B.O.S.S. or in an external tool?
Weekly Insight Reports	Enables AI-generated weekly business health summaries and lets you set the delivery day.	Which day should insights arrive so leadership can review them before the main operating meeting?
Manual User Activation	Creates new users in an Uninvited state until an administrator sends the invite from User Management.	Should users go live immediately, or only after roles, reporting lines, and other setup details are confirmed?

What good looks like

Notes & Todos is enabled when the organization wants work context and personal follow-through kept inside the platform. Weekly Insight Reports is scheduled to arrive before leadership needs it. Manual User Activation is used only when the onboarding process is disciplined enough to send invitations intentionally.

Watch-out

If Manual User Activation is enabled but the team forgets to send the invite, users will exist in the system without being onboarded.

Support

The Support card defines whether the built-in support workflow is available, which roles can use it, and how ticket updates are delivered after a request is submitted.

Figure 4. Support controls access, permitted roles, and ticket update delivery.

Control	What it controls	What to consider
Enable Support	Turns the Help & Support experience on or off for the organization.	If disabled, role permissions are irrelevant — ticketing is unavailable to everyone.
Allowed Roles	Defines which role types can access the support system.	Determines whether support is leadership-only or available more broadly.
System Notifications	Sends in-app updates when ticket activity changes.	Best when users are active in the product and need to see support updates quickly.
Email Notifications	Sends email alerts for ticket updates.	Best when ticket follow-up must be visible even when users are not logged into Scale B.O.S.S.

Support access typically follows one of two patterns:

• Leadership-filtered: Strategy Team and Senior Leader roles submit tickets on behalf of teams. This reduces noise and keeps escalation disciplined.

• Broader direct access: More roles can create tickets directly. Useful when speed matters more than centralized triage.

Recommendation

During early rollout, start with narrower support access and expand only after support volume, ticket quality, and response rhythm are well understood.

Evaluate Journeys

The Evaluate Journeys card changes the evaluation experience for Team to Market, Business Essentials, and Key Business Drivers. Each toggle switches that evaluation type from guided setup to management hub mode.

Figure 5. Hub Mode toggles control whether TM, BE, and KBD open in the management hub instead of guided setup.

Mode	Best when	Tradeoff
Guided setup	The team is still learning the framework or needs step-by-step prompts.	More instructional; can feel slow for experienced leadership teams.
Hub mode	The organization is running evaluations as an ongoing management rhythm.	Assumes familiarity; provides less guided scaffolding.

How to think about each toggle

• TM Hub Mode: Use when Team to Market is no longer being learned for the first time and is managed as a recurring leadership system.

• BE Hub Mode: Use when Business Essentials operates as an ongoing management check rather than a guided annual setup.

• KBD Hub Mode: Use when leadership understands its Key Business Drivers and wants a direct management view instead of a prompted discovery flow.

Practical rule

During early adoption, guided setup is the safer choice. Switch to hub mode only when leaders know the framework and want a management-first view.

Fiscal Year

The Fiscal Year card determines how Scale B.O.S.S. labels time for goals, KPI projections, reporting windows, and rollups. It is one of the most consequential settings on this page because it changes how the platform interprets period boundaries throughout the system.

Figure 6. Fiscal Year controls the start month, period display labels, and quarterly rollups.

Setting	What it does	Why it matters
Start Month	Defines the first month of the organization's fiscal year.	Anchors how fiscal months, quarters, and evaluation and reporting periods are labeled.
Period Display Format	Switches between Calendar and Fiscal labels.	Calendar labels are easier for casual reading; Fiscal labels are better for internal planning and board review.
Show Quarterly Rollups	Groups monthly projections and reporting into quarter-level views.	Useful when leadership manages both monthly accountability and quarterly decision-making.

Important note

Changing the start month recalculates evaluation period and KPI projection labels. Target values, notes, and measurement data are preserved, but period labels will change. Treat this as an operating-calendar decision, not a cosmetic one.

Before changing this card, confirm four things:

• The company's true fiscal year start month.

• Whether executive reporting should use calendar or fiscal language.

• Whether the leadership team wants quarterly summaries alongside monthly detail.

• Whether teams need advance notice that period labels will change after the update.

Auto-Archive

The Auto-Archive card keeps active workspaces usable by defining how long finished or rejected items remain visible before being archived from main working views.

Figure 7. Auto-Archive sets retention windows for rejected ideas, completed My Board items, and done charters.

Archive rule	What it affects	When to shorten vs. extend
Rejected Ideas	Ideas that were reviewed and explicitly rejected.	Shorten if the ideas board feels crowded; extend if leaders still need time to review recently rejected items.
Done Board Items	Completed items on My Board.	Shorten if personal boards feel cluttered; extend if users rely on recently completed items as a short-term reference.
Done Charters	Completed company charters.	Shorten if charter boards are heavy with historical work; extend if completed charters need to stay visible during review cycles.

The goal of auto-archive

Auto-archive is not about hiding history — it is about preventing active workspaces from becoming historical storage. The right settings keep current boards easy to read without making completed work disappear so quickly that leaders lose needed context.

Operating rhythm and final checklist

Preferences works best when reviewed as part of a regular operating rhythm rather than adjusted ad hoc. Most organizations do not need to revisit every control weekly, but a deliberate cadence ensures the platform stays aligned with how the business actually runs.

Trigger	What to review
Quarterly operating review	Fiscal labels and rollups, archive windows, and support access relative to the current organization.
Onboarding process change	Manual User Activation and whether the invitation flow still reflects the actual onboarding model.
Leadership workflow redesign	Hub Mode settings for TM, BE, and KBD.
Adoption or productivity concerns	Notes & Todos availability and the Weekly Insight Reports schedule.
Support volume or escalation issues	Allowed support roles and notification settings.

Common mistakes to avoid

• Treating these settings as harmless toggles rather than organization-wide operating controls.

• Enabling Manual User Activation without updating the onboarding process to include the Send Invite step.

• Scheduling Weekly Insight Reports to arrive after the team has already held its main review meeting.

• Switching to Hub Mode before users are comfortable operating without guided scaffolding.

• Ignoring Auto-Archive until boards are already cluttered with historical work.

Final takeaway

The Preferences page is the policy layer for how Scale B.O.S.S. behaves across the organization. When configured thoughtfully, the rest of the platform feels cleaner, more intentional, and better aligned to the company's real operating model.

Managing Organization-Wide Preferences in Scale B.O.S.S.