Program settings

What Settings is

Every program has a Settings area — the cross-cutting configuration that shapes how the whole program behaves, as opposed to the day-to-day content you build inside the program (sessions, exercises, forms, and so on — the “journey items”). Journey items are what participants move through; Settings are the rules and defaults that govern how those items work, how the program looks, and who can do what.

Settings is organized into a set of focused areas (shown as cards on the Settings landing page, or as a dense one-page “power view” for admins who prefer it). Each area opens into its own editor. A breadcrumb and prev/next controls let you move between areas without going back to the landing page each time.

Below, the areas are grouped by theme rather than by their order in the navigation, since that’s a more natural way to think about what they do.

Identity, look, and language

General covers the basics: the program’s name, code, description, what kind of program it is (coaching, mentoring, LIA, or reverse mentoring), and whether it runs on a fixed calendar or rolling enrollment (with start/end dates for fixed programs).

Branding controls the colors, logo, hero imagery, typography, and custom styling participants see. Branding works on a cascade: a program can either inherit the tenant’s (company-wide) default branding, or override it with its own theme. Branding also keeps a version history, so a previous look can be restored. Because branding is inherited from the tenant level by default, it’s also visible read-only in a couple of other places in the product — but the Settings tab is the authoritative place to change it or to switch a program between “inherit” and “override.”

Terminology & Labels lets you rename the vocabulary participants see — what a “Support Giver” or “Support Receiver” is called, session/training/goals labels, and so on — per language, including grammatical variants for languages that need them (e.g. Turkish dative/genitive forms). This is different from Program Roles below: Terminology only changes display names, not which roles actually exist in the program.

People and roles

Program Roles decides which roles from the role library a program actually uses for matching (e.g. which flavors of “mentor” or “mentee” this program supports), and enforces that every program has at least one Support Receiver role and one Support Giver role so matching can function.

Competencies maps a competency framework’s competencies to the different purposes they’re used for in a program — self-assessment, development goals, 360 feedback, matching, and more. This mapping is what Goals and Competencies screens elsewhere in the product actually read.

Manager Engagement configures what line managers (and HRBP, where applicable) see and can do in their own canvas — which tabs are visible (reports, sessions, exercises, goals, handshakes, and so on) and how much detail each tab shows.

Scheduling and sessions

Calendar sets the program’s time zone (falling back to the tenant’s default when left blank), which governs how session times are interpreted and displayed for this program.

Video sets the default video/meeting platform (e.g. Teams, Zoom, Google Meet, or none) used when the system generates a session link automatically. This setting is shared with the program’s Sessions configuration — the value can also be seen there — but Settings is a convenient place to change just the platform default.

Matching and marketplace

Matching covers the matching algorithm mode, timeout behavior for support-giver responses, whether HRBP approval is required before a match is finalized, and which fields of a support giver’s profile are visible during and after matching.

Marketplace governs whether support receivers can browse and self-select from a pool of support givers rather than being matched automatically — including access mode, cool-off periods between requests, manager-approval requirements, and the marketplace’s own descriptive text per role and language. A tenant-level master switch can turn the marketplace off entirely for a company; when it’s off, a program’s marketplace tab becomes read-only.

Program lifecycle

Welcome sets the first-run content — title, body text, a call-to-action, and optional video/infographic — that each role sees on entering the program, per language.

Closure defines how and when a program wraps up: which completion requirements apply (all sessions done, handshake signed, goals reviewed, final evaluation complete), whether a completion certificate is shown, and the grace period before a program is considered overdue.

Progress Weights is an emerging area for overriding how much each item type (sessions, exercise packages, forms, handshakes, 360 feedback, training) contributes to a participant’s overall progress percentage. It is not yet reflected in participant-facing progress today — changes made here are saved, but do not yet change what a participant sees.

Safety

Risk Alerts controls which risk signals are surfaced, to which roles (support giver or manager), and the wording used for them. Like branding, this cascades from a tenant-wide default that a program can override.

Advanced

Content & Features groups a few program-level controls. Its most useful part is menu visibility — a per-role matrix that shows or hides specific areas (sessions, reports, goals, and so on) for support givers, managers, and HRBP, and for some of those it blocks access to the underlying page entirely. It also holds content-engagement settings that shape supplementary content surfaced to support receivers over the course of a program. Note that whether a capability such as exercises, handshakes, or 360 feedback is part of a program is determined by the items on the program’s journey, not by a toggle here.

Where does it live

Most settings areas are self-contained — the Settings tab is the only place to view or change them. A few have a presence elsewhere by design:

Branding cascades from a tenant-level default; the tenant default lives in company-level branding configuration, and the program’s Settings > Branding tab is where you either inherit that default or override it for this program specifically.
Video’s default platform is also visible from the program’s Sessions configuration, since it’s genuinely the same underlying setting — Settings is a shortcut to change just that one value.
Risk Alerts similarly cascades from a tenant-level default policy, overridable per program here.

In every case, the Settings tab is the authoritative editor for that program’s value — other surfaces either read the same underlying value or offer their own scoped override path, but they aren’t a second, independent copy of the configuration.