Projects Settings
The Projects settings page (Settings → Projects) is a hub for the configuration that drives /projects: portfolio initiatives, the integrations work flows through, author mappings that name PR and Linear contributors, and the ARR source for roadmap rollups. Decision inbox weighting lives separately under Settings → Administration → Decisions.
Initiatives
Portfolio themes that sit above projects — "Expansion", "Retention", "Conversion", etc. Initiatives appear in the Areas view of the Projects list when you toggle from Taxonomy to Initiatives, and on each project's detail rail.
Click Configure initiatives to open the settings modal. Inside you can:
- Create new initiatives — name, optional description
- Define shared fields — properties shown on every initiative card (status, target date, owner, etc.) with multiple field kinds (text, select, date, number, etc.)
- Link projects — connect existing projects to an initiative
The settings page shows three stats at a glance:
- Initiatives — total count of portfolio themes available
- Fields — shared fields defined on initiatives
- Linked projects — total project↔initiative links in the system
Integrations
Linear, Jira, and GitHub are the providers project work flows through. The settings page surfaces each one's connection status — Connected (green), Error (red), or Not connected (gray).
Click Manage all integrations to open the full Integrations page where you can connect, reauthorize, or disconnect providers.
GitHub ↔ Teammates
Maps GitHub usernames to BuildBetter teammates so PR triage and project assignees show real names instead of raw handles.
Two metrics on the settings card:
- Mapped — GitHub handles linked to a teammate
- Unmapped — recent PR authors that haven't been mapped yet (highlighted amber when greater than 0)
Click Set up mappings (or Edit mappings) to open the dedicated page where you can:
- See every PR author across your tracked repos
- Match handles to teammates by email or manually
- Override automatic matches
The mappings drive assignee provenance badges on the Projects list (the G badge on avatars).
Linear ↔ Teammates
Most Linear users auto-resolve by shared email — no setup needed. The mappings page is for the edge cases: consultants, contractors with personal email addresses, anyone who isn't on your org domain.
When a Linear ticket is promoted to a project, BuildBetter auto-fills the assignee from the ticket's assignee or creator email. If their email matches a teammate, the assignee gets the L provenance badge on the avatar. For off-domain Linear users, the explicit mapping is what makes attribution work.
ARR Source Field
The same setting documented on Triage Settings. One workspace-wide choice that drives:
- ARR rollups on the Projects list
- Per-project ARR on the Project Detail page
- ARR columns across Triage signals, PRs, clusters, and topics
The dropdown lists every company metadata field, sorted by populated company count. Pick the field with the best coverage.
Triage Item Types
The Projects settings page surfaces a card linking to Settings → Features → Triage for managing item types (Bug, Feature Request, etc.). Tracked item types are the categories that classify every project and every triaged signal.
See Triage Settings for the full details.
Decision Inbox Weights
Located under Settings → Administration → Decisions (not in the Projects settings hub itself). Tunes the formula that ranks items in the Triage Decisions tab.
Four factor weights, each adjustable and normalized to sum to 1 on save:
| Factor | What It Favors |
|---|---|
| Customer value | Companies paying more, or high-priority accounts |
| Severity | Signals / reviews / calls with high severity or urgency |
| Volume | Clusters with many linked signals |
| Frequency | Things happening now — fresh signals, just-requested reviews |
Tune the weights to match how your team prioritizes. If you want recency to win over volume, raise Frequency and lower Volume. Per the 2026-04-19 release, edits from the settings UI persist correctly across sessions.
Cycle Settings
If your workspace has the cycles feature flag, Settings → Features → Cycle lets you define release cycles (quarters, sprints, etc.) that projects can be assigned to. Cycle definitions carry properties (start date, end date, theme) that surface on project detail.
The Cycle settings page is its own sidebar entry; the Projects settings hub doesn't surface it directly.
Tip: The Projects settings page is a hub, not a dumping ground. Heavier configs (the full provider list, the Triage item types editor) deep-link to their dedicated pages so this page stays focused on what powers the roadmap rollups.