# Strategy Hub: App setup > Install Strategy Hub, run the setup wizard step by step, and create your first Item — an admin's path from install to a working view Canonical: https://docs.caskcode.io/strategy-hub/app-setup/ Strategy Hub turns your strategic plan into a living model of **Strategic Items**—Objectives, Key Results, KPIs, or whatever your framework calls them—owned by people, assigned to Teams, and tracked through configurable Statuses. This page walks an admin from install through the setup wizard to the first useful view. Every choice the wizard asks for has a sensible default and can be changed later in Settings, so you can move quickly and refine as you go. ## Before you install Strategy Hub runs inside Jira as a Forge app, so there is nothing separate to host and your data stays on Atlassian infrastructure. Before you start, line up: - A **Jira Cloud** site you can install apps on. - Jira **admin** permission — the setup wizard is admin-only, and you'll designate who else administers Strategy Hub during it. - A rough idea of how your organization plans. The wizard can recommend a framework for you, but it helps to know whether you run OKRs, a single-page plan, or something more specialized. See [Strategy frameworks](https://docs.caskcode.io/strategy-hub/strategy-frameworks) for the full set. ## Install from the Atlassian Marketplace Install Strategy Hub the same way as any other Jira app: 1. In Jira, open **Apps** in the top navigation and choose **Explore more apps**. 2. Search for "Strategy Hub" and open its listing. 3. Select **Install** and accept the requested scopes. After it installs, Strategy Hub appears under the Jira **Apps** menu as a global page. Open it once and the setup wizard starts automatically for admins. Anyone who opens Strategy Hub before an admin finishes setup sees a short holding screen rather than an empty workspace. ## Run the setup wizard The setup wizard is four steps—framework, data, permissions, and Jira—followed by a short screen that builds your workspace. A step indicator across the top tracks where you are, and you can move back to revisit any earlier choice. Nothing is written until the final step, and every setting the wizard collects is editable afterward in Settings. ### Choose a framework A **framework** is a preset for your Item hierarchy — the levels you can create (its Types), how they nest, the Statuses they move through, and how progress rolls up. Rather than open on a wall of options, the step starts with a short conversation: answer three questions about your organization's size and planning style, and Strategy Hub recommends the preset that fits best.  The recommendation is a suggestion, not a commitment. Accept it to move on, or choose **See all options** to compare the full grid of eight presets with your recommendation pre-selected. Prefer to skip the questions? Choose **Skip — I know what I want** on the first question to jump straight to the grid and pick one yourself. Picking a framework is a single click, and it is never a lock-in — you can change the framework and reshape its Types and Status Sets at any time in Settings. For what each preset models and how to tailor or build your own, see [Strategy frameworks](https://docs.caskcode.io/strategy-hub/strategy-frameworks). Either path lands on the same grid of all eight presets, each card showing its Type hierarchy at a glance:  ### Seed your data Next, choose how your new workspace starts: - **Start empty** — a clean slate with no Items, ready for you to build. - **Generate sample data** — example Items that match your framework, so you can explore the views right away. You can remove the sample data later in Settings. - **Import CSV** — bring in Items from a spreadsheet, validated against your framework's Types. See [Import from CSV](https://docs.caskcode.io/strategy-hub/import-from-csv) for the column format.  ### Set permissions This step decides what everyone in your organization can do by default and who helps you administer Strategy Hub. - **Baseline role** — the access level every member starts with: **Viewer**, **Collaborator**, or **Manager**. Collaborator is the recommended default. This sets the floor; you can grant more on individual Items later. - **Admins** — the people who can manage settings, roles, Teams, and data. You are always an Admin and can add co-admins here.  The role model behind these choices is covered in [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions). ### Connect Jira The last step wires Strategy Hub into your Jira site. Each option is a sensible default you can change later in Settings: - **Sync Jira teams** — keep Strategy Hub's Team list in step with the Teams on your Jira site. - **Custom JQL function** — let Jira filters reference Strategy Hub Items with the `linkedToStrategyItem()` JQL function. - **Rovo integration** — let people open Strategy Hub's Rovo agent from in-app buttons and Rovo Chat. If Rovo isn't available on your site, this stays off. - **Issue panel** — show the Strategy Hub panel on the Jira issue view, so linked work is visible from the issue.  When linked work rolls up into an Item's value, this step is also where you decide whether that value is weighted evenly, by story points, or by priority. [Jira integration](https://docs.caskcode.io/strategy-hub/jira-integration) covers linked work in depth. ### Finish setup The final step applies your choices: it creates the framework's Types and Status Sets, seeds roles, syncs Teams, and—if you asked for it—generates the sample data or imports your CSV. A progress screen shows each phase as it runs. When it finishes, Strategy Hub opens on the Dashboard.  ## Create your first Item With setup done, create the first real Item from any view with **Create new**. The create dialog asks for the essentials: - **Type** — which level in the hierarchy this Item sits at (an Objective, a Key Result, and so on). - **Name**, **Owner**, and, for anything below the top level, a **Parent**. - A **start** and **target** value, plus **start** and **end** dates. Strategy Hub mints a key from the Type's prefix—an Objective becomes `O-1`, a Key Result `KR-1`—so every Item has a stable handle. You can save an Item as a draft to stage it during a planning session and publish it later. [Strategic Items](https://docs.caskcode.io/strategy-hub/items) covers the full lifecycle, including how an Item's value updates: **manual**, from **nested items**, or from **linked work items**. ## Tour the views Once you have a few Items, point your team at the view that answers their question: - [Dashboard](https://docs.caskcode.io/strategy-hub/dashboard) — "what should I look at right now?" - [Portfolio board](https://docs.caskcode.io/strategy-hub/portfolio-board) — top-level cards with subtree health. - [Team board](https://docs.caskcode.io/strategy-hub/team-board) — per-Team workload and risk. - [Roadmap](https://docs.caskcode.io/strategy-hub/roadmap) — Items on a timeline. - [Hierarchy map](https://docs.caskcode.io/strategy-hub/hierarchy-map) — Items by structure. - [Overview](https://docs.caskcode.io/strategy-hub/overview) — a flat, filterable table of everything. ## Next steps - Shape the structure to match your organization — rename Types, adjust levels, and edit Statuses under [Configure types and status sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets). - Set auto-status thresholds so progress turns into Statuses without manual updates — see [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress). - Already tracking plans in a spreadsheet? Bring them in with [Import from CSV](https://docs.caskcode.io/strategy-hub/import-from-csv). ## Related - [Strategy frameworks](https://docs.caskcode.io/strategy-hub/strategy-frameworks) — every preset the wizard offers, and how to customize or build your own. - [Configure types and status sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets) — reshape the hierarchy and Statuses your framework starts you with. - [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions) — the role model behind the baseline role and admins you set during setup. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — create, link, and track the Items that fill your workspace. --- # Strategy Hub: Strategy frameworks > The eight framework presets Strategy Hub ships with, how the setup wizard recommends one, and how to tailor or build your own Canonical: https://docs.caskcode.io/strategy-hub/strategy-frameworks/ Strategy Hub models your strategy as a hierarchy of **Strategic Items**, and a **framework** is a preset for that hierarchy. It defines the Types you can create—Objective, Key Result, Measure, and so on—how they nest, and the Statuses each level moves through. You pick a framework once, during the [setup wizard](https://docs.caskcode.io/strategy-hub/app-setup#run-the-setup-wizard), from eight presets that cover the common planning models. None of them is a ceiling: every preset is a starting point you can reshape, and you can build a fully custom hierarchy of your own. ## What a framework sets up Choosing a framework seeds four things, so a new workspace is usable immediately: - **Types** — the named levels of the hierarchy, each with its own icon, color, and key prefix. - **Nesting rules** — which Types are allowed beneath which, so the structure stays valid as your team creates Items. - **Status Sets** — the ordered Statuses each level moves through, split into a simpler set for high-level Items and a tighter one for execution-level Items. - **Progress behavior** — how each level's value updates and rolls up, tuned to how that model actually works. You choose from these presets on the wizard's first step. If you're not sure which fits, the step opens on a short conversation that recommends one for you — see [Choose a framework](https://docs.caskcode.io/strategy-hub/app-setup#choose-a-framework) in App setup. ## The eight presets Each preset names its levels differently and nests them to match a planning model. The tree beside each one is the Type hierarchy it seeds, top to bottom—the same tree the setup wizard shows on its framework card. Find the closest fit; you can rename any level afterward. ### Simple OKR  The lightest preset—two levels, with Key Results nested under the Objectives they measure. Each Objective's value rolls up from its Key Results, so progress on the measures moves the goal above them. It suits a small team putting structure on its goals for the first time. ### OKR  The full OKR model at three levels, adding a Strategy tier above Objectives. A Strategy holds one of the few priorities the organization is steering by; Objectives sit beneath it, and Key Results measure each Objective. Reach for it when you want day-to-day execution to ladder up to a handful of named strategic bets rather than a flat list of goals. ### OKR + KPI  The three-level OKR hierarchy with one addition: a KPI sits alongside Key Results under an Objective. A Key Result is a time-boxed target for the quarter; a KPI is a standing metric you watch continuously, so pairing them lets an Objective carry both its push and its ongoing health signal. It fits data-driven teams that track operational numbers next to their outcome goals. ### OGSM  Objective, Goal, Strategy, and Measure captured as one cascading plan, four levels deep. The Objective states the ambition, Goals quantify it, Strategies are the chosen paths, and Measures track whether each path is working. Teams that like to see their whole strategy on a single page reach for OGSM. ### Hoshin Kanri  A four-level cascade for long-horizon planning. Breakthrough Objectives set the multi-year ambition, Annual Objectives break it into the current year, Improvement Priorities name where to focus, and Targets make each priority measurable. The structure keeps every yearly plan tied back to the transformation it serves, which suits organizations driving a big, multi-year change through tightly aligned annual cycles. ### EOS (Traction)  The Entrepreneurial Operating System's Vision-to-Traction ladder, from a 10-Year Target down through a 3-Year Picture and a 1-Year Plan to the quarterly Rocks a team commits to. Each level narrows the horizon, so long-range vision resolves into the few priorities that matter this quarter. It fits entrepreneurial teams that run on a short list of Rocks at a time. ### North Star  A guiding North Star Metric, the Input Metrics that drive it, and the Initiatives that move those inputs. Unlike the OKR presets, North Star deliberately does not roll values up: an Input Metric drives the North Star Metric rather than summing into it, so each metric is tracked on its own. It suits product and growth teams steering by one leading number. ### 4DX (4 Disciplines of Execution)  A single Wildly Important Goal with two kinds of measure beneath it. Lag Measures are the outcomes the goal is judged by; Lead Measures are the activities your team acts on each week to move them. The two are tracked separately—the Lead Measures don't pull the goal's value around—which keeps attention on the one or two goals that matter most. ## Make it your own A preset is where you start, not where you're stuck. Everything a framework creates is editable under **Settings**, so most teams pick the closest preset and then reshape it: - **Rename a level** to match your vocabulary—"Goal" instead of "Objective"—or change its icon and color. - **Add or remove levels**, and set which Types are allowed beneath which, to deepen or flatten the hierarchy. - **Edit the Statuses** and the sets they belong to, so the pills read in your reporting language. - **Change how progress rolls up** at each level, from a value someone types in to one aggregated from nested Items or linked work. You can also start from a preset and rework it into a hierarchy that matches no standard model at all—the presets are conveniences on top of a fully configurable structure, not a fixed menu. [Configure types and status sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets) walks through every one of these edits. > **Tip** — pick the preset whose shape is closest to how you already plan, even if the names are off. Renaming levels is quick; rebuilding the nesting from an empty hierarchy is slower. ## Related - [App setup](https://docs.caskcode.io/strategy-hub/app-setup) — where you choose a framework, get a recommendation, and run the rest of the setup wizard. - [Configure types and status sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets) — reshape the Types, nesting, and Statuses a framework starts you with. - [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress) — what the Status Sets and progress behavior a framework sets up actually do. --- # Strategy Hub: Strategic Items > Strategic Items are the unit of strategic work in Strategy Hub. Create, edit, organize, and archive them from any view. Canonical: https://docs.caskcode.io/strategy-hub/items/ A **Strategic Item** is the unit of strategic work. Depending on your framework an Item might be an Objective, a Key Result, a Strategy, a KPI, a Goal, or a Measure—they are all Items, differentiated by their **Type**. This page covers the Item lifecycle and the fields you meet in the **Item details view**. ## Anatomy of an Item Every Item carries the same set of fields, grouped by what they describe. You edit most of them inline in the Item details view. - **Name, key, and Type** — the Name is the Item's headline. The key is generated from the Type's prefix (such as `O-12` for an Objective). The Type controls which parents are allowed, the default **Status Set**, and how Status and value updates behave. - **People** — the **Owner**, a single user accountable for the Item who is auto-granted Manager permissions, and any **Teams** assigned, whose members are auto-granted Collaborator permissions. Both grants apply on Default-access Items. - **Progress and dates** — the current **Status**, the **Period** the Item belongs to (such as H1 2026), the Start and End dates that frame the planning window, and the start, target, and current value the progress bar measures against. The value shows as a percentage, a plain number, or a currency amount. - **Update behavior** — whether the Status updates manually or automatically, whether the value is entered manually, rolled up from nested items, or computed from linked work items, and the weight the Item carries in its parent's rollup. - **Classification and access** — **Labels** for filtering across views, and the **Access level**, either Default or Custom. See [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions).  1. **Status and progress** — the current Status and the progress bar, at the top of the view. 2. **Progress chart** — the value tracked over the Item's planning window. 3. **Details** — the sidebar that groups Owner, Teams, Labels, Type, Period, and dates. 4. **Nested items** — the children whose value rolls up into this Item. ## Create and stage an Item Use **Create new** on the Overview—or the **Create** action on a parent Item—and pick the Item's Type from the menu that opens. You pick the Type first because it decides the rest: the new Item only offers the fields and update modes that Type allows. If the Type allows or requires a parent, a **Pick a parent item** step appears, filtered to the parents that Type permits. A new Item starts as an **unsaved item**, so you don't have to publish straight away. Build out a whole branch—an Item and its children—and Strategy Hub keeps them in an Unsaved items tray, flags any that are still incomplete, and lets you **Discard all** at once. This is how you plan a tree before the rest of the org sees it. Save the Items when the shape is right and they become visible.  ## Edit an Item Click any Item name to open the Item details view. **Status and progress** sit at the top, with the current Status and the progress bar. Strategy Hub can update the Status automatically from progress, or you can set it manually. Most fields edit inline. The **Details** sidebar groups the rest of the fields—Owner, Teams, Labels, Type, Period, Start date, End date, and Parent—and the value mode (such as nested items with equal weight) sits just below. Access is set separately from the **Manage access** control in the header. Two more sections keep the Item's record: - **Comments** hold discussion in the **Activity** section's Comments tab. They often carry free text, so keep sensitive detail out of them. - **History** is the Activity section's other tab. It records every change with who, when, and what—including Emergency access events.  ## Two ways to see an Item The Item details view opens in one of two presentations, and you switch between them from the header. By default it opens as a **modal**—a panel centered over a dimmed backdrop, with the rest of the screen pushed out of focus. The modal suits working one Item at a time, with its full record in front of you. Choose **Open as drawer** in the header to switch to a **side drawer** instead. The drawer opens in place from the right and leaves the view you came from—the Overview, a board—visible beside it, so you can read an Item without losing your place in the list. **Open as modal** switches back.   1. **View toggle** — the header control that switches between the two presentations. It reads **Open as drawer** on the modal and **Open as modal** on the drawer. ## Hierarchy and reordering Each Item has zero or one parent, and the full tree of Items is the **Hierarchy**. Reorder children with the **Move** handle on each row in the Overview and within a Portfolio board subtree. Which Items can parent which is constrained by Type—a Key Result cannot parent an Objective, for example. See [Configure types and Status Sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets#type-hierarchy) for how those rules are set. ## Archive and restore Archiving removes an Item from the active views but preserves its data and history. Archived Items are listed under **Settings → Data**, where you can restore any of them. Archiving a parent does not archive its children—you choose what to archive explicitly. Archived Items are kept for 90 days and then deleted automatically. See [Manage workspace data](https://docs.caskcode.io/strategy-hub/manage-workspace-data).  ## Related - [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress) — how a Status updates from progress, and how value rolls up the tree. - [Insights](https://docs.caskcode.io/strategy-hub/insights) — the findings Strategy Hub surfaces on Items that need attention. - [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions) — who can see and edit an Item, and how Default and Custom access differ. --- # Strategy Hub: Dashboard > The Dashboard answers "what should I look at right now?"—ranked Insights, a forecast, upcoming deadlines, and the things waiting on you Canonical: https://docs.caskcode.io/strategy-hub/dashboard/ The Dashboard is the personal landing page for everyone in your workspace. It gathers the highest-severity [Insights](https://docs.caskcode.io/strategy-hub/insights) on the Items relevant to you, alongside forward-looking and historical cards, so you can see what needs your attention without opening every Item. ## Layout and scope The Dashboard is a grid of cards, each answering one question about your work. Rearrange the grid to suit you—drag a card by its **Drag to reorder** handle to move it. Use **Dashboard settings** to choose which cards appear. Two controls at the top set what every card counts. The **Period** selector scopes the Dashboard to one planning Period, such as Q2 2026. The **Dashboard scope** toggle—**My items**, **My teams items**, and **All**—sets whose Items are in view, and the first two can both be on at once. Change either control and the cards recompute together, so the whole Dashboard answers the same question. The **Welcome** card sits at the top with a one-line summary of the Period: how many Items you and your Teams own, your average completion against where it's expected to be, how many things are waiting on you, and how many need attention.  ## Needs attention **Needs Attention** is the flagship card. It lists the Items that most need a decision, each with the [Insight](https://docs.caskcode.io/strategy-hub/insights) Strategy Hub raised on it, ranked highest-severity first and capped at eight rows. You get one row per Item—if an Item has more than one Insight, its most severe one represents it. Each row names the Item and its Type, shows who's accountable, and states what was spotted—an Item past its deadline, drifting off track, or stalled with no recent progress. When nothing meets the bar, the card shows a short empty state in place of the list.  ## Forecast The Forecast card looks ahead. It projects your Items' progress to the end of the Period along their current trajectory, then sets that projection against the target—the gap between them is the headline. A chart plots progress so far against where it needs to reach by the deadline, so an effort that won't land in time shows up before it's too late. Switch between Types to forecast Strategies, Objectives, Key Results, and KPIs separately.  ## The other cards The rest of the grid fills in the picture—a quick rollup, what's coming, what just happened, and what's waiting on you. Turn any of them on or off from **Dashboard settings**. - **Items overview** — a compact table of your Items, each row showing its progress, current Status, Owner, and Teams. It links out to the full [Overview](https://docs.caskcode.io/strategy-hub/overview). - **Upcoming deadlines** — Items whose End date falls soon, sorted by how close it is, each with the days remaining and its Status. - **Activity** — a running feed of recent changes across the Items you can see: value changes, Status changes, comments, and ownership changes, each with a relative time. - **Needs my response** — the things waiting on you: at-mentions, Items assigned to you, and Items due an update from you.  ## Related - [Insights](https://docs.caskcode.io/strategy-hub/insights) — what Strategy Hub spots on an Item, and why a row appears in Needs Attention. - [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress) — how an Item's value and Status move, and how the Forecast extrapolates them. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — open any Item from a Dashboard card to see its full record. --- # Strategy Hub: Overview > One sortable, filterable table of every Item you can see—browse the whole Hierarchy, edit in place, and export to CSV Canonical: https://docs.caskcode.io/strategy-hub/overview/ The Overview is the workhorse list view. Every [Strategic Item](https://docs.caskcode.io/strategy-hub/items) you can see appears here as a row in one tree-aware table. It is where you go to filter, sort, search, edit in place, or export many Items at once—the long-form companion to the Dashboard's at-a-glance cards. ## Reading the list The Overview is a single hierarchical table. Each row is an Item, and parent rows expand and collapse so you can open a branch or fold it away—the Hierarchy you see on the [Hierarchy map](https://docs.caskcode.io/strategy-hub/hierarchy-map), laid out as rows. A count badge on a parent row tells you how many children are tucked under it. Each row carries the Item's columns: its name and Type icon, progress, Status, Period, Owner, recent update, Teams, Labels, value, and start and end dates. Most of these are editable in place—click an Item's Status, Owner, value, or a date and a picker opens right in the row, so you can change it without opening the Item. Click the Item's name or key to open its full [Item details view](https://docs.caskcode.io/strategy-hub/items). An Item you don't have access to still holds its place in the Hierarchy, but it renders as a stub row—just its key, Type icon, and a lock marker, with nothing to expand or open. See [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions#restricted-items) for what makes an Item restricted.  ## Choosing columns The table shows a standard set of columns out of the box—name, progress, Status, Period, Owner, recent update, Teams, Labels, value, and start and end dates. Use **Configure columns** at the right edge of the header to tailor which of them appear, so the list carries the fields the work in front of you needs and nothing more. To reorder the rows themselves, use a row's **Move** handle: it picks the Item up so you can drop it under a new parent or among its siblings. Because moving an Item changes how its progress rolls up, which Insights it raises, and who can see it, Strategy Hub confirms the change before it commits. ## Filter, sort, and search Three controls at the top of the list narrow it to the Items you want. The **Period** selector scopes the table to one planning Period, such as Q2 2026. The **Search by name or key** box matches Items as you type, so you can jump to one without building a filter. The **Filter** button opens a panel that combines several filters at once: - **Status** — show only Items in the Statuses you pick, such as On Track or Off Track. - **Type** — show only the Types you pick. - **Owner** — Items owned by the people you choose. - **Teams** — Items assigned to one or more Teams. - **Labels** — Items carrying one or more Labels. - **Parent** — Items nested under a particular parent. **Clear all** resets the panel. Click a column header to sort the list by that column. A filter set you return to often can be kept: **Save filter** stores the current filters, and **Saved filters** lists what you've saved alongside built-in presets such as **My items** and **This quarter**.  1. **Filter** — the button that opens this panel. The categories you set here combine, so the list narrows to the Items that match all of them at once. ## Row actions Every row carries a **more** menu with the actions you'd otherwise open the Item to reach: - **Create** a child Item of a chosen Type directly under this row. - **Show subtree** to focus the list on this Item and its descendants, or **Collapse all** to fold every branch back down. - **Export subtree** to download just this Item and the Items beneath it as a CSV. - **Archive** the Item. - **Ask about this item** to put the question to [Rovo](https://docs.caskcode.io/strategy-hub/rovo-ai). To start a brand-new top-level Item instead, use **Create new** above the list and pick its Type.  1. **more** — the button on every row that opens its actions menu, shown here on the top row. ## Exporting Open **More actions** above the list and choose **Export to CSV** to download the list as a spreadsheet. The export follows what you see—the current filters decide which rows it contains. To go the other way, **Import from CSV** sits beside it; see [Import from CSV](https://docs.caskcode.io/strategy-hub/import-from-csv) for the column format and how rows map to Items. ## Related - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — the full record behind each row, and where in-place edits land. - [Hierarchy map](https://docs.caskcode.io/strategy-hub/hierarchy-map) — the same Hierarchy as a diagram instead of a table. - [Insights](https://docs.caskcode.io/strategy-hub/insights) — the findings flagged on Items you scan in the list. - [Import from CSV](https://docs.caskcode.io/strategy-hub/import-from-csv) — the inverse of export: build Items from a spreadsheet. --- # Strategy Hub: Portfolio board > One card per top-level Item—its own progress, the health of the Items nested beneath it, and the Insights raised across its branch Canonical: https://docs.caskcode.io/strategy-hub/portfolio-board/ The Portfolio board gives you one card per top-level Item—each Item at the top of your Hierarchy, the ones with no parent. A card reads that Item's health at a glance: its own progress, a breakdown of the Items nested under it, and the [Insights](https://docs.caskcode.io/strategy-hub/insights) Strategy Hub has raised anywhere in its branch. Use the board to scan your whole portfolio for the Items that need a decision, then drop straight into the ones that do. ## Reading the board The board lays out one card per top-level Item in a grid. The **Period** selector at the top scopes every card to one planning Period, such as Q2 2026—change it and the cards recompute together. There are no other board-wide controls. Each card carries its own detail. Every card answers the same three questions for its Item: how far along it is, how the Items beneath it are doing, and what needs attention. A card whose branch is entirely healthy says so plainly; a card with problems surfaces them as Insights and a short list of the Items behind them.  ## What a card shows A card stacks the same regions top to bottom, each labeled. Read them in order and you have the Item's full picture without opening it.  1. **Status** — the Item's current Status, such as Off Track, colored by its category. 2. **Progress** — the Item's own value against its target, as a percentage and a bar. 3. **Insights** — the findings on this Item and deeper in its branch. The [next section](#insights-on-a-card) covers them. 4. **Nested items statuses** — the Item's directly nested children grouped by Status, drawn as a segmented bar with a count. 5. **Progress chart** — a sparkline of the Item's value across the Period. It reads "No data yet" until the Item has history. 6. **Needs-attention list** — a table of the nested items that need a look, each with its progress, Status, and Owner. It reads "All items on track" when the branch is healthy. The **header** carries the Item's Type icon, its key (such as `S-1`), its name, and the planning window with a countdown to the End date. The **footer** carries the Item's Owner and the Teams on it, with a **View all items** link to the [Overview](https://docs.caskcode.io/strategy-hub/overview) filtered to this branch. ## Insights on a card The **Insights** section is where the Portfolio board earns its place—it is the fullest view of what Strategy Hub has spotted, more complete than the Dashboard's ranked summary. See [Insights](https://docs.caskcode.io/strategy-hub/insights) for the catalogue behind every pill and count, and how severity is ranked. Two kinds sit side by side: - **Per-Item Insights** — a pill for each finding on the card's own top-level Item, with a short reason. An Item whose Status is flagged unhealthy, for example, shows an "At risk" pill reading "status flagged unhealthy". - **Branch counts** — a count chip for problems found deeper in the branch, below the directly nested children—"1 problem item" or "3 past deadline", each tagged "in sub-tree, deeper than direct children". The nested children themselves are summarized in Nested items statuses; these chips reach further down. Click one to list the Items behind it (see [Drilling in](#drilling-in)).  ## Drilling in Everything on a card is a way into the detail. - **Open an Item** — click any Item's name or key to open its [Item details view](https://docs.caskcode.io/strategy-hub/items). This works for the card's top-level Item, the rows in the needs-attention list, and the Items inside an expanded count. - **Expand a count** — click a branch count chip to drop down a list of the Items behind it, each with its Status and Owner. Click through to any of them. - **See the whole branch** — **View all items** in the footer opens the [Overview](https://docs.caskcode.io/strategy-hub/overview) filtered to this Item's children. ## Related - [Insights](https://docs.caskcode.io/strategy-hub/insights) — the findings behind every pill and count on a card. - [Team board](https://docs.caskcode.io/strategy-hub/team-board) — the same Items grouped by Team instead of by Hierarchy. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — open any card to its full Item record. - [Overview](https://docs.caskcode.io/strategy-hub/overview) — the flat, filterable list the footer link lands on. --- # Strategy Hub: Team board > One card per Team—its average completion, the Statuses across the Items it owns, and the Insights raised across them Canonical: https://docs.caskcode.io/strategy-hub/team-board/ The Team board shows the same Items as the [Portfolio board](https://docs.caskcode.io/strategy-hub/portfolio-board), grouped by **Team** instead of by Hierarchy. One card stands for one Team and reads its load at a glance: how far along its Items are, how those Items split across Status, and the [Insights](https://docs.caskcode.io/strategy-hub/insights) Strategy Hub has raised across them. Use it to find the Team carrying the most risk, then drop into the Items behind it. ## Reading the board The board lays out one card per Team in a grid, split into two groups: **My teams**—the Teams you belong to—sit at the top, with **Other teams** below. The **Period** selector at the top scopes every card to one planning Period, such as Q2 2026—change it and the cards recompute together. An Item lands on a Team's card when that Team is assigned to the Item. An Item can be on more than one Team, so the same Item can appear on several cards. Teams sync from Jira; see [Configure teams and labels](https://docs.caskcode.io/strategy-hub/configure-teams-and-labels) for how they are managed and assigned.  ## What a Team card shows A card stacks its regions top to bottom. Read them in order and you have the Team's picture without opening it.  1. **Header** — the Team's avatar and name. 2. **Average completion** — the mean progress across the Items the Team owns, as a percentage and a bar. 3. **Insights** — count chips for the findings raised across the Team's Items. The [next section](#team-scoped-insights) covers them. 4. **Statuses** — the Team's Items grouped by Status, drawn as a segmented bar with a count and a legend, such as 2 At Risk and 5 On Track. 5. **Items that need attention** — a table of the Team's flagged Items, each with its progress, Status, and Owner. It reads "All items on track" when the Team is healthy. Sort it with the **Status** control. 6. **View all items** — opens the [Overview](https://docs.caskcode.io/strategy-hub/overview) filtered to this Team. ## Team-scoped Insights The Team board aggregates Insights across every Item the Team owns, as a row of count chips—rather than listing them per Item the way a Portfolio card does. Each chip names a finding, counts how many of the Team's Items it covers, and gives a short reason.  The common chips read: - **at-risk items** — Items whose Status is flagged unhealthy. - **past deadline** — Items whose End date has passed. - **items behind pace** — Items tracking below the on-track bar for this point in the Period. - **status mismatches** — Items whose manual Status differs from what Auto-status would set. One chip is different. When a single Owner is carrying several of the Team's Items that need support, Strategy Hub tags that chip with the Owner's avatar—a sign the load is concentrated on one person. See [Insights](https://docs.caskcode.io/strategy-hub/insights) for the full catalogue behind every chip and how severity is ranked. ## Drilling in Everything on a card is a way into the detail. - **Open an Item** — click any Item's key or name to open its [Item details view](https://docs.caskcode.io/strategy-hub/items). This works for the rows in the needs-attention table and for the Items inside an expanded chip. - **Expand a count** — click an Insight chip to drop down a list of the Items behind it, each with its Status and Owner. - **See the whole Team** — **View all items** in the footer opens the [Overview](https://docs.caskcode.io/strategy-hub/overview) filtered to this Team. ## Related - [Portfolio board](https://docs.caskcode.io/strategy-hub/portfolio-board) — the same Items grouped by Hierarchy instead of by Team. - [Insights](https://docs.caskcode.io/strategy-hub/insights) — the findings behind every chip on a card. - [Configure teams and labels](https://docs.caskcode.io/strategy-hub/configure-teams-and-labels) — how Teams sync from Jira and get assigned to Items. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — open any card through to a full Item record. --- # Strategy Hub: Roadmap > A timeline view of your Items—each one drawn as a bar across its planning window, with the hierarchy on the left and a Today line for orientation Canonical: https://docs.caskcode.io/strategy-hub/roadmap/ The Roadmap answers "when?". It lays your Items out on a horizontal time axis so you can see how work is sequenced, where deadlines bunch up, and what is running past its dates. The hierarchy sits on the left as a table; the timeline fills the right. Use it when the conversation is about timing rather than structure—for that, see the [Hierarchy map](https://docs.caskcode.io/strategy-hub/hierarchy-map). ## Reading the Roadmap The Roadmap is one screen split down the middle. On the left, a table lists your Items with three columns—Name, Progress, and Status. On the right, a time axis draws each Item as a bar across the dates it spans. Every row in the table lines up with one bar.  1. **Item tree** — the Name column lists your Items in hierarchy order, indented under their parents. Expand or collapse a parent with its chevron; a collapsed parent shows a count of the children it hides. 2. **Progress** — each Item's value against its target, as a percentage. 3. **Status** — the Item's current Status, such as Off Track or On Track, colored by its category. 4. **Timeline bars** — each Item runs from its start date to its end date, labeled with its key and name. The bar's dates come from the Item itself; open the Item to change them. 5. **Today line** — a dashed vertical marker for the current date, so you can read at a glance what is behind, current, or still ahead. ## Setting the time scale Two controls decide how much time the axis shows. The **Period** selector at the top scopes the whole view to one planning Period, such as Q2 2026. Change it and the table and timeline recompute together. The zoom controls at the bottom right set how densely the axis is drawn: **Auto** sizes it to fit, and **Week**, **Month**, **Quarter**, and **Year** each fix the column width. **Scroll to today** jumps the timeline back to the Today line when you have scrolled away. ## Filtering and sorting The toolbar narrows what the Roadmap shows. Type into the search box to find an Item by name or key. Open **Filter** to narrow by Status, Type, Owner, Teams, Labels, or Parent—the same filter the other views use. Sort the table by clicking the Name, Progress, or Status column header. A filter you return to can be kept: **Saved filters** lists the ones you have stored, and **Create new** saves the current set. ## Opening an Item Everything on the Roadmap is a way into the detail. - **Open an Item** — click an Item's key or name to open its [Item details view](https://docs.caskcode.io/strategy-hub/items), where you can edit its dates, value, and Status. - **Reorder the tree** — drag a row by its handle to move an Item within the hierarchy. - **Row actions** — the **more** menu on a row carries the same actions as the Item itself, such as archiving it. ## Related - [Hierarchy map](https://docs.caskcode.io/strategy-hub/hierarchy-map) — the same Items arranged by structure instead of by time. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — the dates and hierarchy that drive every bar. - [Overview](https://docs.caskcode.io/strategy-hub/overview) — the flat, filterable list of the same Items. --- # Strategy Hub: Hierarchy map > A canvas view of your Items—cards arranged in bands by Type and linked parent to child, for seeing how work ladders up Canonical: https://docs.caskcode.io/strategy-hub/hierarchy-map/ The Hierarchy map answers "how does this ladder up?". It draws your Items as cards on a canvas, organized into horizontal bands by Type and connected by lines from each parent to its children. Use it when the conversation is about structure—coverage, gaps, what rolls up into what. When the conversation is about timing instead, use the [Roadmap](https://docs.caskcode.io/strategy-hub/roadmap). ## Reading the Hierarchy map The canvas is read top to bottom. Each Type in your hierarchy gets its own horizontal band, with the highest Type at the top. Cards sit inside their band, and lines connect each parent to the children it owns in the band below.  1. **Type band** — one horizontal strip per Type, labeled on the left. Strategies sit above Objectives, Objectives above their Key Results, and so on down your hierarchy. 2. **Time cluster** — within a band, cards are grouped into boxes by their planning window, such as 2026 or H1 2026, so Items that share a timeframe sit together. 3. **Card** — one card per Item. The [next section](#what-a-card-shows) covers what it shows. 4. **Connector** — a line from a parent card down to each of its children, so you can trace a branch from top to bottom. ## What a card shows A card carries the same Item summary you see elsewhere, sized to fit the canvas. Read it without opening the Item: - **Identity** — the Type icon, the Item's key (such as `S-1`), and its name. - **Progress** — the Item's value against its target, as a bar and a percentage. - **Status** — the current Status, such as Off Track, colored by its category. - **Owner** — the avatar of the single person accountable for the Item. - **Children** — a footer that expands the card to reveal its nested Items, with a count of how many it has. ## Working with the canvas The map is a canvas, so you move around it rather than scroll a page. Drag an empty area to pan. The controls at the bottom right zoom in and out, and **Fit all** frames the whole map in view. Expand a card's children to walk down a branch in place. The toolbar scopes the map the same way it scopes the other views. The **Period** selector limits the map to one planning Period. The search box finds an Item by name or key, and **Filter** narrows by Status, Type, Owner, Teams, Labels, or Parent. To open an Item, click its key or name on the card—its [Item details view](https://docs.caskcode.io/strategy-hub/items) opens over the map. ## Related - [Roadmap](https://docs.caskcode.io/strategy-hub/roadmap) — the same Items arranged on a timeline instead of by structure. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — the Types and parent/child links that shape every band and connector. - [Portfolio board](https://docs.caskcode.io/strategy-hub/portfolio-board) — health at a glance for each top-level Item and its branch. --- # Strategy Hub: Insights > Insights are the findings Strategy Hub surfaces on your Items—what's at risk, behind pace, or past deadline—ranked by severity across every view Canonical: https://docs.caskcode.io/strategy-hub/insights/ An **Insight** is a finding Strategy Hub surfaces on an Item—that it's at risk, drifting behind pace, stalled, or past its deadline. You don't create Insights yourself. Strategy Hub watches every Item's Status, progress, deadline, and structure, and raises an Insight the moment one crosses a line. The same finding then travels to wherever you're looking—a row in Needs Attention, a pill on a Portfolio card, a count on a Team card. ## Where Insights appear Strategy Hub computes one canonical set of Insights per Item. Each view then shows as much of that set as it has room for, at the density that fits it. - **Dashboard** — [Needs Attention](https://docs.caskcode.io/strategy-hub/dashboard#needs-attention) lists the Items that most need a decision, one row per Item, ranked by severity and capped at eight. - **Portfolio board** — the fullest view: a [pill for every finding](https://docs.caskcode.io/strategy-hub/portfolio-board#insights-on-a-card) on a card's Item, plus counts for problems deeper in its branch. - **Team board** — a row of [count chips](https://docs.caskcode.io/strategy-hub/team-board#team-scoped-insights), one per finding, aggregated across the Items a Team owns. An Item with no Insights doesn't clutter these views. A healthy card or list says so plainly—"All items on track". ## What Strategy Hub spots on an Item Most Insights are about a single Item. Strategy Hub raises one when the Item crosses a line you'd want to know about:  - **At risk** — the Item's Status is Not healthy. The Status itself is the verdict. - **Behind pace** — the Item is tracking below where it should be by this point in its planning window. It may still be moving, just not fast enough to land on time. - **Past deadline** — the End date has passed and the Item isn't Done. - **Approaching deadline** — the End date is near and the Item is still short of where it needs to be. - **Stalled** — the Item's value hasn't been updated within the cadence its Type expects, so its progress may be out of date. - **Status mismatch** — the Owner's manual Status differs from the one Auto-status would set from progress. One of the two is out of step. - **Inactive children** — the Item has nested children, and none of them has moved recently. - **Unassigned** — no one is accountable for the Item, so an Insight on it has no clear owner to act. The exact wording on a pill or row is short—"status flagged unhealthy", "40 days past deadline"—but each one maps to a finding above. ## Across a group of Items A few Insights only appear when you compare Items. Strategy Hub watches a group—a branch on the [Portfolio board](https://docs.caskcode.io/strategy-hub/portfolio-board), the Items a [Team](https://docs.caskcode.io/strategy-hub/team-board) owns—and raises an Insight when the group as a whole shows strain that no single Item reveals. - **One Team carrying the risk** — most of the at-risk Items in a branch belong to a single Team, so the risk is concentrating in one place. - **One person overloaded** — a single person is accountable for several Items that need support. Strategy Hub tags the chip with that person's avatar, so you can see the load is landing on one set of shoulders. - **Children pulling apart** — an Item's children are spread far apart in progress—some racing ahead while others stall—so the parent's average hides the spread. ## Severity and ranking Every Insight carries a severity—high, medium, or low—so the most urgent findings rise to the top. - **High** — a passed deadline, an at-risk Status, or a branch's risk concentrating on one Team. These need a decision now. - **Medium** — falling behind pace, an approaching deadline, a stalled Item, a status mismatch, or one person carrying several Items that need support. - **Low** — structural hints like inactive children, children pulling far apart in progress, or an Item with no one assigned. Severity can shift with context. An unassigned Item that's also at risk matters more than an unassigned one that's fine, so Strategy Hub bumps its Insight up. Severity is what lets [Needs Attention](https://docs.caskcode.io/strategy-hub/dashboard#needs-attention) rank and choose. When an Item has several Insights, it shows the most actionable one and ranks the Item by it; the [Portfolio board](https://docs.caskcode.io/strategy-hub/portfolio-board#insights-on-a-card) shows them all. Where a stronger finding makes a weaker one redundant—an at-risk Status already implies the Item is behind pace—Strategy Hub keeps only the one that tells you most. ## Related - [Dashboard](https://docs.caskcode.io/strategy-hub/dashboard) — where Needs Attention ranks Insights by severity and shows one per Item. - [Portfolio board](https://docs.caskcode.io/strategy-hub/portfolio-board) — the fullest view of Insights, as per-Item pills and branch counts. - [Team board](https://docs.caskcode.io/strategy-hub/team-board) — Insights aggregated into count chips, one card per Team. - [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress) — the Status, pace, and update-cadence rules that raise most Insights. --- # Strategy Hub: Statuses and progress > How a Status reflects an Item's health, how its value tracks progress, and how the two connect through auto-status, rollups, and update cadence Canonical: https://docs.caskcode.io/strategy-hub/statuses-and-progress/ Status answers "how is this going?" Progress answers "how far has it moved?" Every Strategic Item carries both, and Strategy Hub can keep them in step or let you set each by hand. This page explains the model—what a **Status** is, how an Item's value updates, and how the two connect. ## Status, category, and Status Set A **Status** is the named lifecycle state of an Item—the words on its pill. The *name* is configurable, so one workspace reads "On Track" where another reads "Green". The *category* underneath is fixed. Every Status belongs to one of four: - **Not started** — the Item hasn't begun. - **Healthy** — the Item is progressing as it should. - **Not healthy** — the Item is in trouble. - **Done** — the Item is complete. The category, not the name, is what Strategy Hub reasons about. It colors the pill, drives the Status segment bars across the views, and decides whether an Item counts toward risk or completion. A **Status Set** is an ordered collection of Statuses plus the auto-status rules that map progress to one of them. Each Item Type points to a Status Set, which supplies the Statuses that Item may use. Two sets typically ship with each framework—one for leaf Items like Key Results and Measures, one for parents like Objectives and Strategies. See [Configure types and status sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets). ## How a Status updates A Status updates one of two ways, and the Item's Type decides which are available. - **Manual** — the Owner picks the Status. Auto-status still computes a suggestion in the background, but doesn't enforce it. When the manual Status and the suggestion disagree, Strategy Hub raises a [Status mismatch Insight](https://docs.caskcode.io/strategy-hub/insights) so the two can be reconciled. - **Automatic** — Strategy Hub recomputes the Status every time progress changes, reading the value against the Status Set's auto-status rules. ## Auto-status and pace Auto-status turns a number into a Status through the Status Set's **status workflow**. The workflow is a row of progress segments—a range like 0–25% maps to one Status, 25–70% to the next, 70–100% to another—and as an Item's value climbs, its Status moves from one segment to the next. Three special designations cover the edges: a starting Status applied before the start date, a completed Status applied when progress reaches 100%, and a failed Status applied once the end date has passed. The workflow grades the value against *expected* progress, not just the raw number. An Item is expected to be roughly halfway to target halfway through its planning window, so an Item tracking below where it should be by this point reads as behind pace even when its value is still rising. That's the finding the [Behind pace Insight](https://docs.caskcode.io/strategy-hub/insights) reports.  ## How a value updates An Item's value is the number its progress bar measures against its start and target. It updates one of three ways, and again the Type decides which are available. - **Manual** — the Owner types the value in. The Item's record keeps who set it and when. - **Nested items** — the value is a rollup of the children's progress. A parent in this mode shows the weighted average of its branch (see below). - **Linked work items** — the value is computed from the Item's linked Jira work items, such as the share of them that are Done. See [Jira integration → Progress from linked work items](https://docs.caskcode.io/strategy-hub/jira-integration#progress-from-linked-work-items). ## Rolling up from children When a value rolls up from nested items, each child contributes a share of the parent's number. How those shares are decided is the parent's weighting—the Item details view shows it beside the mode, as in "Nested items, equal weight": - **Equal weight** — every child counts the same. - **Manual weight** — each child carries a weight you set and contributes in proportion. - **Story points** — a child's weight is the sum of its linked Jira issues' story points. - **Priority** — a child's weight comes from the priority of its linked issues. The last two read from Jira, so they suit branches whose leaves track linked work. Priority weights are configurable—see [Configure types and status sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets). ## Staleness A value can be right when entered and wrong a month later if nobody revisits it. Each Type sets an update cadence—how long an Item may go without a manual update before Strategy Hub considers it stale and raises a [Stalled Insight](https://docs.caskcode.io/strategy-hub/insights). Only a manual update resets the clock. Rollups from children and recomputed linked values keep flowing, but they don't count as someone confirming the number. So an Item whose value moves only automatically can still go stale. ## Related - [Insights](https://docs.caskcode.io/strategy-hub/insights) — the Behind pace, Stalled, and Status mismatch findings all come from the rules on this page. - [Configure types and status sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets) — where Status Sets, status workflows, and Type update policy are set. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — where you read and set an Item's Status, value, and update modes. - [Jira integration](https://docs.caskcode.io/strategy-hub/jira-integration) — how linking issues feeds value updates and weighting. --- # Strategy Hub: Access and permissions > How Strategy Hub decides who can see and edit each Item — system roles, Default and Custom access, Restricted Items, and Emergency access. Canonical: https://docs.caskcode.io/strategy-hub/access-and-permissions/ Permissions in Strategy Hub combine two scopes: an **app-level role** that sets what you can do across Strategy Hub, and **item-level roles** that set what you can do on a single Item. Each Item also carries an **Access level** that decides whether your app-level role counts on it at all. ## The four system roles The same four roles name what someone can do, whether granted across Strategy Hub or on one Item. | Role | Scope | Typical holder | What it allows | | ---------------- | -------------- | ------------------------------ | ----------------------------------------------- | | **Admin** | app-level | Jira site admin | Every permission, on every Item; manages workspace data | | **Manager** | app or item | Strategy lead, Item Owner | Edit Item content, manage access, archive | | **Collaborator** | app or item | Team member, contributor | Edit progress and comments | | **Viewer** | app or item | Stakeholder, leadership viewer | Read-only | - App-level roles are granted on the **Settings → Permissions** page. - Item-level roles are granted on a single Item from its **Manage access** dialog. - Admin is app-level only. It can't be assigned on a single Item because it already carries every item permission. ## Default access Most Items use **Default** access. When an Item's Access level is Default, permission to see and edit it comes from three sources combined: - **Your app-level role** — an Admin can see and edit every Item; a Viewer can read it. - **Owner auto-grant** — the Item's **Owner** is auto-granted Manager-level permissions on it. - **Team auto-grant** — members of the Item's assigned **Teams** are auto-granted Collaborator-level permissions on it. This is how most work behaves. A leadership Objective is visible to the org through everyone's Viewer role, while the Owner and the contributing Teams get edit rights without anyone granting them by hand. ## Custom access Switch an Item to **Custom** access when its content is sensitive — exec planning, performance objectives, an M&A initiative. Under Custom access, app-level roles count for nothing and the auto-grants no longer apply on their own. Only the grants you set on the Item decide who gets in. You make every change from the Item's **Manage access** dialog, which offers two views: **Simple** for the common case and **Advanced** for fine-grained control. Strategy Hub keeps you on as a Manager when you lock an Item down and blocks removing its last Manager, so you can't shut yourself out. > **Tip** — turn on **Apply to nested items** before you save to push the same access change down the whole branch. A child you don't touch stays Default. ### The simple view The **Simple** view turns access into a few switches. Turn on **Make this item private** to lock the Item down — its Access level becomes Custom, global Collaborators and Viewers lose access, and only the people listed below keep it. The switches beneath decide whether the convenience auto-grants still hold: - **Admins and Managers can manage this item** — on by default. While it's on, anyone with an app-level Admin or Manager role keeps access. - **Owner is a manager** — keep the Item's Owner as a Manager, or turn it off to drop them. - **Team members are collaborators** — keep the linked Teams' members as Collaborators, or turn it off to drop them.  ### The advanced view The **Advanced** view is for handing access to specific people and Teams. Start from a preset, then tune the individual grants: - **Access preset** — **Default** follows each person's app-level role, **Private** grants only the Owner and the linked Teams, and **Open** lets everyone collaborate while Owners, Admins, and Managers manage. - **Three tiers** — everyone with access sits in one of *manage*, *collaborate*, or *view*, matching the Manager, Collaborator, and Viewer roles. Use **Change role** on a row to move someone between tiers. - **Add people and teams** — find a person or Team in **Add people or teams**, pick the tier, and choose **Add access** to grant it.  ## Restricted Items An Item is a **Restricted Item** for a given person when it's Custom-access and that person holds no grant that lets them see it. - In the tree views it appears as a stub row — its key, Type icon, and a lock marker, and nothing else. The name, value, and content stay hidden. Open it and you get a lock screen instead of the Item. - "Restricted" is always relative to the viewer. The same Item can be restricted from one teammate and fully visible to another. - Because an Admin carries every item permission, an Item is restricted from an Admin only when it's Custom-access. That is the intended escape hatch — see [Emergency access](#emergency-access) below.  ### Restricted Items registry An Item's content can be hidden from an Admin, but its existence never is. The **Restricted Items registry** on the **Settings → Data** page lists every Restricted Item by key and Type, and offers an **Emergency access** action on each row. See [Manage workspace data](https://docs.caskcode.io/strategy-hub/manage-workspace-data#restricted-items-registry) for the full page.  ## Emergency access An Admin can grant themselves Manager-level access to a Restricted Item they otherwise can't see. This is **Emergency access**, and it's what keeps Custom-access Items hidden-by-default rather than unrecoverably private. Reach it from the **Emergency access** action on the Item's registry row, then confirm.  - It is **audited** — the grant is recorded in the Item's history — but **quiet**: no notification is sent and no justification is asked for. - It adds an ordinary Manager grant for the acting Admin on that one Item. Revoke it from the same **Manage access** dialog as any other grant. - It unlocks the Item for that Admin alone. It does nothing for anyone else — surgical, reversible, single-actor. ## Worked examples - **A leadership Objective** — keep it Default. Org-wide Viewers see it; the Owner and the assigned Strategy Team edit it. - **A confidential M&A initiative** — switch it to Custom. Grant Manager to the project lead and two execs. Other Admins see only the stub row, with Emergency access available if they ever need in. - **A Key Result under a confidential Objective** — set it to Custom too. Default access would leak the child's name and value to anyone with an org-wide Viewer role, even while its parent stays hidden. ## Related - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — the Access level field sits with the rest of an Item's classification. - [Manage workspace data](https://docs.caskcode.io/strategy-hub/manage-workspace-data) — the Restricted Items registry and the workspace audit trail. - [Configure Teams and Labels](https://docs.caskcode.io/strategy-hub/configure-teams-and-labels) — set up the Teams whose members earn auto-granted access. --- # Strategy Hub: Configure types and status sets > Shape the levels of your Strategic Item hierarchy and the Statuses each level moves through — the structural setup behind every Strategy Hub view Canonical: https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets/ Types and Status Sets are the structural backbone of a Strategy Hub workspace. A **Type** is a level in your **Strategic Item** hierarchy—Strategy, Objective, Key Result, KPI—and a **Status Set** is the ordered list of Statuses the Items at that level move through. Both are managed by an Admin under **Settings**, and most workspaces configure them once during setup and revisit them rarely. Strategy Hub installs with a starter set already in place, so you are usually adjusting what's there rather than building from scratch. ## When to configure this Reach for these settings when the structure or the vocabulary stops matching how your organization works: - You want to rename a level—"Goal" instead of "Objective"—or change its icon or color. - You are introducing a new level, such as an Initiative between Objective and Key Result. - The Statuses don't match your reporting language, and you'd rather read "Off Track" than "At Risk" on a pill. - A level should track progress a different way—rolling up from its children instead of a number someone types in. ## Types A Type is one level in the hierarchy. Open **Settings → Types** to see them all and to add, rename, or rearrange them. ### The Type hierarchy The Types screen lays out every Type by level, top to bottom. Drag a Type between levels to change where it sits. Use **Children** on a parent Type to choose which Types are allowed beneath it—that constraint is what keeps the hierarchy valid, so the Create and Parent pickers only ever offer Types the structure permits. **Create type** adds a new level.  1. **Key prefix** — the short code that mints Item keys for this Type, shown beside its name. 2. **Children** — sets which Types are allowed directly beneath this one. 3. **Configure** — opens the Type's full settings. ### What each Type controls **Configure** on a Type opens its settings. A Type carries: - **Name** and **key prefix** — the prefix mints Item keys like `OBJ-1`. The name is editable at any time. The prefix is fixed once the Type exists, because Items already carry keys built from it. - **Icon** and **color** — the chip you see on every Item of this Type. - **Status set** — which set of Statuses Items of this Type may use (more below). - **Progress tracking** — which value-update modes Items of this Type may pick (manual, nested items, or linked work items) and which one is the default. - **Status update mode** — whether Items update their Status manually, automatically, or either way, and which is the default. - **Cadence** — how long an Item of this Type may go without a manual update before it counts as stale. Only a manual update resets that clock. The progress and Status options here set the menu; an Owner then picks from it per Item. See [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress) for what each mode does. ## Status Sets Open **Settings → Statuses** to manage Statuses in two layers: the shared pool of Statuses, and the sets that arrange them. ### Statuses live in one place Every Status—its name, color, and category—is defined once in a shared list, then reused across as many sets as you like. Define "On Track" once and it is the same "On Track" everywhere. Each Status lists the sets it is used in, so you can see its reach before you edit or remove it. A Status's name is yours to set. The category beneath it is one of four fixed system categories—Not started, Healthy, Not healthy, and Done—and that category, not the name, is what Strategy Hub reasons about. See [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress#status-category-and-status-set).  1. **Statuses** — the shared pool. Each Status is defined once and reused. 2. **Status Sets** — named collections that arrange Statuses into an order and a workflow. ### Building a Status Set A Status Set gives a name, a description, and an ordered list of Statuses to the Items at one or more levels. Open a set to: - Name it and describe what it is for—"For strategies and objectives" reads better in a picker than "Set 2". - Add Statuses from the shared list and drag them into the order Items should move through. - Lay out the **status workflow**—the progress segments that map a value to a Status when a Type updates automatically, plus the starting, completed, and failed Statuses for the edges. The mechanics live in [Statuses and progress → Auto-status and pace](https://docs.caskcode.io/strategy-hub/statuses-and-progress#auto-status-and-pace). A set's **Used by** panel lists the Types that point to it, so you always know who depends on a set before you change it. > **Tip** — workspaces usually keep two sets: a simpler one for high-level Items like Strategies and Objectives, and a tighter one for execution-level Items like Key Results and KPIs. ## Editing safely Most edits are safe and take effect everywhere at once—rename a Type, recolor a Status, reword a description, and every Item updates immediately. A few changes need more care: - A Type's **key prefix** can't change once the Type exists. Pick it deliberately at creation. - Removing a Status from a set, or deleting a set a Type still uses, affects live Items. Check the set's **Used by** panel first. - Deleting a Status, a set, or a Type asks you to confirm before it applies. This structure changes rarely for a reason: every view, rollup, and Insight is built on it. When you do change it, expect the change to ripple across the whole workspace. ## Related - [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress) — what the Status categories, update modes, and status workflow you configure here actually do. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — where the Types, Statuses, and update modes you set up appear for everyone. - [Jira integration](https://docs.caskcode.io/strategy-hub/jira-integration) — story-points and priority weighting for linked-work rollups are configured under Settings → Jira. --- # Strategy Hub: Configure teams and labels > Sync Teams from Jira, create internal Teams, and manage the colored Labels that filter and group Items across every view Canonical: https://docs.caskcode.io/strategy-hub/configure-teams-and-labels/ Teams and Labels are the two ways you organize Items by who owns them and how you want to slice them. A **Team** is a group assigned to an Item—it powers the Team board and grants its members access to the Items they work on. A **Label** is lighter: a colored tag you apply for filtering and grouping. Both are managed by an Admin under **Settings**, and both show up across every view once they're in place. ## Teams Strategy Hub doesn't keep its own team directory. Most Teams come from Jira—the people and groups you already manage there—and you can also create a few that live only in Strategy Hub. Open **Settings → Teams** to see both kinds, grouped on one screen.  1. **Internal teams** — Teams you create in Strategy Hub. You manage their members here. 2. **Jira teams** — Teams synced from your Jira site, each marked with a Jira badge. ### Jira teams and internal teams **Jira teams** carry their name, avatar, and member list straight from Jira. Membership is read at sync time, so a change you make in Jira—someone joins a Team, someone leaves—shows up in Strategy Hub after the next sync. **Sync Jira teams** runs that sync on demand; it also runs on a schedule, so the list is usually current. **Internal teams** are the ones you create here with **Create team**, for when your strategy work doesn't line up with how Jira is organized. An internal Team has no Jira counterpart and you manage its members in Strategy Hub, but it behaves identically everywhere else—you assign it to Items, its members get access, and it groups the Team board the same way a Jira Team does. ### Assigning a Team to an Item You assign a Team from the Item itself, in its Teams field. Assigning a Team does three things: - It groups the Item on the [Team board](https://docs.caskcode.io/strategy-hub/team-board), under that Team's card. - It grants the Team's members access—on a default-access Item, members become Collaborators automatically. See [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions). - It clears the "no Team" flag—an Item with no Team assigned raises an Insight prompting you to give it one. ## Labels A **Label** is a colored tag you apply to Items to filter and group them. Where a Team says who owns an Item, a Label is free-form—use it for a theme, a quarter, a workstream, anything you want to slice by later. Open **Settings → Labels** to manage them. ### Creating and editing Labels Each Label has a name and one of ten colors. **Create label** adds one—pick a color, type a name, and save.  Editing a Label, whether you rename it or recolor it, updates every Item it's applied to at once. Deleting a Label removes it from every Item; Strategy Hub asks you to confirm first. ### Applying and filtering Apply Labels from the Item's Labels field, which takes as many as you like. Once applied, a Label shows on the Item across the views that display it—Portfolio cards, Overview rows, and the Item header. Because Labels are built for slicing, you can filter by them on the [Overview](https://docs.caskcode.io/strategy-hub/overview) and the [Portfolio board](https://docs.caskcode.io/strategy-hub/portfolio-board). ## Related - [Team board](https://docs.caskcode.io/strategy-hub/team-board) — the view that groups Items by the Teams you assign here. - [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions) — how Team membership auto-grants Collaborator access on default-access Items. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — where you assign Teams and apply Labels to individual Items. --- # Strategy Hub: Manage workspace data > Archive and restore Items, find Restricted Items, wipe the workspace, and read the audit trail — the Admin tools that keep your data clean and recoverable. Canonical: https://docs.caskcode.io/strategy-hub/manage-workspace-data/ The **Settings → Data** page is the Admin's control panel for the data behind your workspace. It holds the Items you've archived, surfaces the Restricted Items even an Admin can't otherwise see, and offers a single destructive action to clear the workspace and start over. Everything on this page is Admin-only. ## Archive and restore Archiving takes an Item out of circulation without deleting it. The Item drops off every view—Dashboard, Overview, Portfolio board, Team board, Roadmap, and Hierarchy map—while its value, history, comments, and links stay intact. You archive an Item from its row or detail menu, and you restore it later in one step from here. Archiving acts on one Item at a time. Children are not archived along with their parent—archive each one you want gone. Restoring an Item returns it to the active views under its original parent, or as a top-level Item if that parent no longer exists. Open Archived items on the **Settings → Data** page to see everything you've archived. Each row shows the Item and its archive date, and a row menu offers **Restore** to bring it back or **Delete permanently** to remove it now.  ### Archive retention and cleanup An archived Item is not kept forever. After 90 days, Strategy Hub permanently deletes it. Until then it stays fully recoverable with **Restore**. > **Heads-up** — once the 90 days pass, the Item is gone for good and only a breadcrumb in the audit trail remains. Restore anything you might want back before then. ## Restricted Items registry A Restricted Item's content can be hidden from an Admin, but its existence never is. The **Restricted Items registry** lists every Item the current viewer can't see, each by key and Type, with an **Emergency access** action on its row. This is the discoverability complement to Custom access. An Item can be locked down, but an Admin can always find that it exists and, if they need to, grant themselves in. See [Access and permissions → Emergency access](https://docs.caskcode.io/strategy-hub/access-and-permissions#emergency-access) for exactly what the action does.  ## Wipe the workspace **Wipe installation**, in the page's Danger zone, is the full reset. It permanently deletes all data—every Item, but also your Types, Statuses, Teams, and settings—and returns Strategy Hub to its initial setup screen. Nothing is spared, and nothing comes back. Because it can't be undone, the confirmation makes you type the word `WIPE` before the button activates. Reach for it only when you mean to start completely over: clearing evaluation or trial data before a real rollout, or resetting a sandbox instance.  ## Audit trail Strategy Hub records every change to an Item—value updates, Status changes, ownership and Team changes, Label edits, archive and restore, access changes, and Emergency access grants. You read this history per Item, in the History tab of its detail view. Emergency access grants are recorded here like any other change, but quietly—the entry lands in the history with no notification sent to anyone. This trail is what makes Emergency access safe to offer: nothing an Admin does to a Restricted Item goes unlogged.  ## Related - [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions) — Restricted Items, Custom access, and the Emergency access mechanics behind the registry. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — the archive lifecycle from the Item side. --- # Strategy Hub: Jira integration > How Strategy Hub links Items to Jira work items—linking, progress from linked work items, the linkedToStrategyItem JQL function, and the work item panel Canonical: https://docs.caskcode.io/strategy-hub/jira-integration/ Strategy Hub runs inside Jira, so the connection to your delivery work is built in. You link a Strategic Item to the Jira work items that move it forward, let an Item's progress track those work items, query the links from Jira's own search, and read an Item's strategic context on the work item itself. Teams sync across from Jira too—that half lives in [Configure teams and labels](https://docs.caskcode.io/strategy-hub/configure-teams-and-labels). ## Link Jira work items to an Item A leaf Item—a Key Result, KPI, or Measure—links to the Jira work items that deliver it. The link is the bridge between the strategy and the work that fulfills it. Open the Item, expand **Linked work items**, and add work items two ways: - **Link work item** — search by work item key or summary and pick specific ones. Use it when you know exactly which work items belong. - **Add JQL rule** — save a JQL query, and every work item it matches links automatically. Use it when the set is a moving target, like everything under a release epic. A single work item can link to several Items—cross-cutting work counts toward more than one Objective. **Sync linked items** re-reads the linked work items on demand, and Strategy Hub also refreshes them as they change in Jira, so each row shows the work item's live status.  ## Progress from linked work items An Item's progress doesn't have to be a number someone types. Set the Item to track **progress based on linked work items** and Strategy Hub derives it from the work items themselves—for example, the share of them that are Done. It recomputes whenever a linked work item changes. This is one of three ways an Item's value updates. [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress#how-a-value-updates) covers all three, and how linked work items can also weight a parent's rollup. A derived value keeps the progress bar current, but it doesn't reset the staleness clock—only a manual update counts as someone confirming the number. ## Query linked work items from Jira Strategy Hub adds a custom JQL function so you can find work items by the Item they support, right from Jira's search: ``` issue in linkedToStrategyItem("KR-10") ``` This returns the Jira work items linked to that Item. Use it in board and backlog filters, saved searches, and automation rules—anywhere JQL works. The **Show in Jira search** link in an Item's Linked work items section opens Jira search already filled with this query. ## The Strategy Hub panel on a Jira work item Open a Jira work item and Strategy Hub adds a panel to its right-hand column, tying the work back to the strategy without leaving the work item.  1. **Strategy Hub panel** — sits among the work item's other panels in the right column. 2. **Linked Items** — every Item the work item contributes to, each with its Status and progress. Click one to open it in Strategy Hub, or switch between a flat list and a tree. 3. **Link item** — connect the work item to an Item without leaving Jira. ## Related - [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress#how-a-value-updates) — the value update modes, including linked work items, and how Jira work items weight a rollup. - [Configure teams and labels](https://docs.caskcode.io/strategy-hub/configure-teams-and-labels) — Team sync from Jira, the other half of the integration. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — where you open an Item to link work items and read its progress. - [Import from CSV](https://docs.caskcode.io/strategy-hub/import-from-csv) — bring existing Items into Strategy Hub in bulk. --- # Strategy Hub: Import from CSV > Bring an existing plan into Strategy Hub from a spreadsheet—a guided wizard maps your columns, matches your values, and previews the tree before anything is created Canonical: https://docs.caskcode.io/strategy-hub/import-from-csv/ The Import wizard turns a CSV spreadsheet into a tree of Strategic Items. It walks you through four steps—upload, map columns, map values, and a previewed result—so you can catch mistakes before anything is written. Use it to migrate from a spreadsheet-based OKR system, bulk-load a quarterly plan after an offsite, or restore Items you exported earlier. ## Prepare your CSV Each row in the file is one Item, and each column is a field. Two things decide whether a file imports cleanly: which columns are required, and how you express the hierarchy. For new Items, five columns are required: `Name`, `Type`, `Status`, `Start date`, and `End date`. Everything else is optional—an `Owner`, a `Team`, the `Start value`, `Target value`, and `Unit` that drive progress, and a `Parent` column that places each Item in the tree. The `Parent` column positions each row with an outline number. A top-level Item gets a whole number (`1`); its children extend it (`1.1`, `1.2`); their children extend it again (`1.1.1`). The top level only accepts your highest Type—in a standard OKR setup that's a Strategy, with Objectives beneath it and Key Results and KPIs beneath those. The `Type` and `Status` values are plain text that must match the names configured in your workspace. ```csv Name,Type,Status,Start date,End date,Parent,Owner,Team,Target value,Unit Win the self-serve market,Strategy,On Track,2026-07-01,2026-09-30,1,Dana Lee,Sales,, Grow self-serve revenue,Objective,On Track,2026-07-01,2026-09-30,1.1,Bob Smith,Sales,, Lift trial-to-paid conversion to 25%,Key Result,At Risk,2026-07-01,2026-09-30,1.1.1,Bob Smith,Sales,25,% Reach $50K self-serve MRR,Key Result,On Track,2026-07-01,2026-09-30,1.1.2,Dana Lee,Sales,50000,USD Make onboarding effortless,Objective,Not Started,2026-07-01,2026-09-30,1.2,Sam Carter,Product,, Cut median time-to-first-value to 10 minutes,Key Result,On Track,2026-07-01,2026-09-30,1.2.1,Sam Carter,Product,10,min Weekly active workspaces,KPI,On Track,2026-07-01,2026-09-30,1.2.2,Dana Lee,Product,900,workspaces ``` > **Tip** — Not sure how to shape the file? Export your current Items first—**More actions** → **Export to CSV**—to see every field as a column and the outline that lays out your tree. Labels, comments, and history aren't part of a CSV import, and new Items take Default access. Bring those in afterward from each Item. ## Start the import Open the Overview, then **More actions** → **Import from CSV**. The wizard opens on the upload step with two modes: - **Create new items** — adds Items from the file. This is the common case, and it needs the five required columns above. - **Update existing items** — changes Items that already exist. The file must include a key column to identify each Item, and only the columns you include are touched. Drop your `.csv` file onto the upload area, or click to browse. A single import handles up to 1,000 rows.  ## Map columns Strategy Hub reads your header row and lines each column up with a field. Required fields are marked with an asterisk, and the wizard auto-detects them when your headers are close—it confirms once every required field is covered. Open any field's dropdown to point it at a different column, or set a column to **Skip** to leave it out. Beyond the required five, the optional fields cover the Owner, Teams, and value columns, plus advanced settings such as how each Item's value and status are updated—left to follow each Type's default unless you map them.  ## Map values Some columns draw from a fixed set—Types, Statuses, Teams, and Owners. The wizard collects every distinct value in those columns and matches it to your workspace. A group reads **All matched** when every value lines up. Where a value doesn't match—an Owner name that isn't a Jira user, for instance—the wizard flags it and you pick the right one from the list. For Owners, **Set all unmapped to me** assigns the leftovers to you in a single click. Every value has to resolve before you can continue, so a Type or Status that matches nothing in your workspace is a signal to fix the spelling in your CSV.  ## Review and import The last step previews exactly what the import will do. Each row shows its action—**Create** for a new Item—beside a provisional key, its Period read from the dates, Status, Owner, and Teams, with the tree laid out as your outline defined it. This is where placement problems surface. If a row's Type can't sit where your outline puts it—an Objective at the top level, where only a Strategy belongs—the wizard lists the offending rows and blocks the import. Fix the outline in your CSV and upload again. When the preview looks right, confirm. Strategy Hub creates the Items, assigns each a real key, and reports the count when it's done.  ## Related - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — the fields each CSV row fills in. - [Configure types and status sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets) — the Types and Statuses your CSV values have to match. - [Configure teams and labels](https://docs.caskcode.io/strategy-hub/configure-teams-and-labels) — Teams must exist before the wizard can match them. - [Manage workspace data](https://docs.caskcode.io/strategy-hub/manage-workspace-data) — export Items as the template for a round-trip, and where archived Items go. --- # Strategy Hub: Rovo AI assistant > Ask Strategy Hub questions in plain language through Atlassian Rovo—the agent answers from your Items, Statuses, and Insights, within what you can see Canonical: https://docs.caskcode.io/strategy-hub/rovo-ai/ Strategy Hub plugs into **Atlassian Rovo**, the AI assistant built into Jira. It contributes an agent—**Strategy Hub (Jira)**—that answers questions about your strategy in plain language, reading from the same **Strategic Items** (Items for short), Statuses, progress, and Insights you already see in the views. Ask how something is tracking, what needs attention, or for a draft update, and it replies in a chat panel without you leaving Jira. ## The Strategy Hub agent Rovo opens as a chat panel docked to the side of Jira. Pick the **Strategy Hub (Jira)** agent and ask in your own words. Answers are grounded in your data—not generic web knowledge—so the agent names specific Items, reports their current Status and progress, and links straight back to them. A reply is usually a short summary plus a table, and each row links to the Item so you can jump from the answer into the view.  After an answer, the agent suggests follow-up questions—click one to drill in without retyping. The footer carries Atlassian's standing reminder that the reply is AI-generated. ## Where to open it You can start a conversation from several places. Each opens the same agent; some pre-scope what you're asking about.  1. **Header button** — **Ask Strategy Hub** sits in the Strategy Hub header, reachable from any view. It opens the agent with a blank prompt, scoped to your workspace. 2. **Card button** — the same **Ask Strategy Hub** appears on individual cards, like Needs Attention. It opens the agent focused on what that card shows. Two more entry points complete the set: - **From Jira's top navigation.** **Ask Rovo** opens Rovo with its default assistant. Switch to this agent with **Change agent**, or @mention Strategy Hub in any Rovo chat. - **From an Item.** Open an Item and choose **Ask Strategy Hub about this item**. It pre-fills a question about that Item—its current Status, progress, recent activity, and what needs attention in its subtree—and sends it for you. ## What you can ask Ask in whatever words fit. The agent understands your Items, their Statuses and progress, Owners and Teams, history, and the Insights raised against them. For example: - "Which of my Key Results are off track this quarter?" - "Summarize how the Increase Revenue Objective is tracking." - "Which Objective does this Key Result belong to, and are any related Key Results at risk?" - "What changed on this Item recently?" - "Draft a status update for my Team's work this week." A question can name an Item by key (`KR-5`) or describe it (the Revenue Objective), and you can keep the thread going—each follow-up builds on the last answer. ## What Rovo can see The agent works within your access. It reads only Items you are allowed to see, so a Restricted Item you have no grant for never appears in an answer. Asking through Rovo doesn't widen that boundary—it is the same one the views enforce. See [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions) for how access is decided. > **Tip** — Rovo is conversational, so confirm anything you'll act on. For a figure of record—an audit number, a status someone is relying on—open the Item or view and read it directly. ## Related - [Insights](https://docs.caskcode.io/strategy-hub/insights) — the findings the agent reads when it tells you what needs attention. - [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions) — the access boundary every Rovo answer stays inside. - [Dashboard](https://docs.caskcode.io/strategy-hub/dashboard) — home of the Needs Attention card and its Ask Strategy Hub button. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — open an Item to ask Rovo about it directly. --- # Strategy Hub: Privacy Policy > How Strategy Hub collects, uses, stores, and protects personal data — an Atlassian Forge app that runs entirely on Atlassian's infrastructure. Canonical: https://docs.caskcode.io/strategy-hub/privacy/ **End User Privacy Policy · Version 1.0 · June 1, 2026** This End User Privacy Policy (Privacy Policy) applies to Strategy Hub: OKRs, Goals, KPIs & Strategy Planning for Jira (Strategy Hub or App), an Atlassian Forge application provided by caskcode (caskcode, we, us, or our) and available on the Atlassian Marketplace. This Privacy Policy describes which personal data Strategy Hub collects, how we store, process, and use it, and what happens when you use the App. > **Important – Runs on Atlassian architecture.** Strategy Hub is built entirely on > Atlassian's Forge infrastructure (Runs on Atlassian). All application logic runs > within Atlassian's secure runtime environment, and all data is stored in > Atlassian-managed Forge Storage. Caskcode does not operate any external servers > or databases and has no direct access to your data or the data of your Jira > instance. ## 1. About us Strategy Hub is provided by **caskcode**, the trading name of Bartosz Wyszkowski, a sole trader (_jednoosobowa działalność gospodarcza_) established in Poland (NIP: 7732489961, REGON: 383238029). In this Privacy Policy, "caskcode", "we", "us", and "our" refer to this business. - Email: support@caskcode.io — for general enquiries - Email: contact@caskcode.io — for general and privacy-related enquiries **Our role under data protection law.** We are the **controller** for the limited personal data we collect to operate, support, and improve the App — technical and usage data (section 3.3), feedback you submit (section 3.5), and commercial and licensing data (section 3.6) — meaning we determine the purposes and means of that processing. For the **strategic content you create within the App** (objectives, key results, KPIs, comments, and related configuration — section 3.4), the **customer organisation that installed Strategy Hub is the controller** and we act as a **processor** on its behalf, with Atlassian providing the underlying Forge infrastructure as a sub-processor. Where required, that processing is governed by a Data Processing Agreement between us and the customer. A Data Processing Agreement is available to customers on request at contact@caskcode.io. ## 2. About you When you install and use Strategy Hub, you become our end user (End User). We categorise End Users so you can easily find the details relevant to your personal data. Please note that you may fall into more than one category depending on how you use the App. | Type of End User | Description | | --------------------- | -------------------------------------------------------------------------------------------- | | End User | Any person who installs and uses the App. | | Strategy Hub End User | End User who creates and manages OKRs, KPIs, Goals, or other strategic items within the App. | | Feedback provider | End User who submits feedback, a support request, or an enquiry via our JSM customer portal. | **Please note!** We do not knowingly process the personal data of End Users under the age of 16. If you are such an End User, or are a legal representative of such an End User, please contact us using the details in section 1. ## 3. Personal data ### 3.1 Sources of data We receive data when you install the App and interact with it, depending on your actions and your Jira instance configuration. Because Strategy Hub operates on the Runs on Atlassian (Forge) architecture, the data we receive is limited to what Atlassian's platform exposes to Forge apps. Caskcode does not have direct access to your Jira instance data beyond what is explicitly passed to the App through Atlassian's Forge APIs. You may update your personal data through the App's functionality or by exercising your right to rectification. The same lawful bases and storage terms apply to updated data. We may also receive data from third parties, as described in section 3.6. ### 3.2 Lawful bases for processing To process your personal data, we rely on the following lawful bases: - **Performance of the contract** — for processing personal data necessary for negotiating, concluding, and performing a contract (primarily, the End Users Terms) with you. - **Legitimate interest** — for processing necessary for the development of our services, taking into account your interests, rights, and expectations. - **Legal obligation** — for processing required by applicable law (for example, to comply with tax regulations) or when requested by a law enforcement agency, court, supervisory authority, or other state-authorised public body. ### 3.3 Technical End Users data We collect limited technical data about End Users to optimise performance, debug issues, and improve the overall user experience. Because the App runs on Atlassian's Forge infrastructure, most technical data is handled within Atlassian's environment. We process the following personal technical data for **performance optimisation, debugging, feature improvement, and App analytics**, on the basis of our **legitimate interest**: - Coarse location (country derived from IP address) - Identifiers (Atlassian user ID) — shared with our analytics and error-monitoring processors (see section 4) - Subscription and licence details - Usage data (App install and usage dates) - Technical information (default settings, HTTP user agent) **Data storage:** We store this data for 3 years from its collection. ### 3.4 Strategy Hub End Users data We process certain data when you create and manage strategic items (OKRs, KPIs, Goals, and related content) within Strategy Hub. **Note on data residency:** Data created within the App (objectives, key results, KPIs, comments, and related configuration) is stored exclusively in Atlassian Forge Storage and is not accessible to Caskcode. We process the following data **to provide you with the App's core functionality**, on the basis of **performance of the contract**: - Strategic item data (names, descriptions, types, hierarchy) - Progress and status values - Period and date configurations - Team and ownership assignments - Comments and activity history - Linked Jira work items - Labels and custom settings **Data storage:** Data is stored until you delete the strategic item or uninstall the App. ### 3.5 Feedback providers data We collect certain data when you voluntarily submit feedback, a support request, or any other enquiry about the App. Feedback is collected via our Jira Service Management (JSM) customer portal. When you submit a request through the portal, we receive and process the data you provide. We process the following data **to respond to your feedback, support request, or enquiry, and to use aggregated feedback for product improvement**, on the basis of our **legitimate interest**: - Email address of the submitter - Text of the feedback, request, or message - Any additional data you voluntarily provide in the submission **Data storage:** We store this data for 6 years from the date of submission or from the last communication regarding it. ### 3.6 Data received from third parties We may receive limited personal data from third parties. The scope, purposes, and lawful bases for such processing are governed by the respective privacy documents of those third parties. | Third party | Privacy documents | | --------------------- | ------------------------------------------------ | | Atlassian Marketplace | | We receive data from Atlassian Marketplace to place the App within the platform and provide you with its functionality. We process the following data **to provide you with the App's functionality**, on the basis of **performance of the contract**: - Company and representative data - Hosting and instance data - Number of users in the Jira instance - Subscription period (start and end dates) - Atlassian licence ID and entitlement number **Data storage:** We store this data for the duration of your use of the App. Where a paid subscription is purchased, Atlassian Marketplace processes payment on our behalf. The data may include payment confirmation, transaction date, purchased subscription details, and billing contacts. We store this data for 6 years from the date you cancel your subscription. ### 3.7 Cookies and tracking technologies Strategy Hub sets no cookies through its own application code. The analytics and error-monitoring tools it uses (PostHog and Sentry — see section 4) store nothing on your device: no cookies, and no data in your browser's local storage. The App does use your browser's local storage, but for strictly necessary, first-party purposes only — remembering your view settings (filters, columns, sorting), preserving your unsaved work, and caching your own preferences. This storage holds no tracking identifiers and no personal data beyond your own settings, is never shared with third parties, and is exempt from consent as strictly necessary storage. Because the App stores no tracking or analytics data on your device, it does not require a cookie consent banner. Any cookies present in the Atlassian interface are set by Atlassian as part of its platform and are governed by Atlassian's Privacy Policy. ## 4. Data sharing with third parties We may share your personal data with third parties without harm to you and in full compliance with applicable law. We have implemented organisational and technical measures to ensure the security of personal data during such transfers. We rely on the following lawful bases for sharing data, depending on the circumstances: consent, compliance with legal obligations, and performance of a contract. | Third parties | Description | | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Error monitoring — Sentry () | We use Sentry to capture technical error diagnostics so we can debug and improve the App. | | Product analytics — PostHog () | We use PostHog to understand aggregate usage patterns and improve the App. | | Contractors and service providers | We work with service providers and contractors to operate, develop, and improve the App, fulfil support requests, and manage the Atlassian Marketplace listing. | | Internal organisational tools | We use CRM systems, communication tools, and similar services within our organisation to provide you with our services. | | State authorities and law enforcement | We may be required to transfer certain data to tax authorities, courts, law enforcement agencies, or other governmental bodies: to comply with a legal obligation or court order; to prevent unlawful use of the App; to protect against third-party claims; or to help prevent or investigate fraud. | **What we send to Sentry and PostHog.** We send these tools a limited set of technical identifiers and aggregate metrics: your Atlassian account ID (a pseudonymous identifier), your site (cloud) ID and URL, installation and environment identifiers, licence and usage counts, and a coarse country derived from your IP address (your raw IP address is discarded). Where you voluntarily submit your name and email through the in-App support widget (see section 3.5), we send those so we can respond. We do **not** send the strategic content you create, the contents of your Jira instance, or any free-text you or your colleagues author — session replays mask all on-screen text, and error diagnostics contain identifiers and technical codes only. Both providers host EEA data within the European Union (see section 6). To obtain a detailed list of third-party recipients of your personal data, please contact us at contact@caskcode.io. ## 5. Atlassian Forge data lifecycle and Rovo ### 5.1 Forge-hosted storage data lifecycle Because all Strategy Hub data is stored exclusively in Atlassian's Forge-hosted storage, the retention and deletion of that data is governed by Atlassian's data lifecycle policies — not by caskcode. The key stages are summarised below. For full details, please refer to the Atlassian developer documentation at: | Stage | What happens to your data | | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | App installation | Atlassian provisions dedicated Forge storage for the App within your Jira site's Atlassian app partition. No data exists before installation. | | App in active use | Data is stored within Atlassian's Forge infrastructure for as long as the App is installed and your Atlassian subscription is active. | | App uninstallation | Data is soft-deleted by Atlassian and retained for a period defined by Atlassian's internal Standard Data Retention and Disposal policy. Caskcode does not control this retention period. | | App reinstallation within 21 days | If the App is reinstalled within 21 days of uninstallation, the new installation can be relinked to the previous data on request. | | App reinstallation after 21 days | Reinstallation is treated as a new installation. Previously stored data may no longer be recoverable. | | Atlassian subscription cancellation | When your Jira subscription is cancelled, Atlassian schedules all associated app data for deletion in accordance with its data retention policy. | | Site deletion | When an Atlassian site is permanently deleted, all associated app data is deleted immediately once the soft-delete period has elapsed. | **Please note:** The retention periods described above are set and controlled by Atlassian. Caskcode is not able to recover data that has been deleted by Atlassian in accordance with its policies. If you require data export before uninstalling the App, please use the Data export functionality within Strategy Hub settings before uninstalling. ### 5.2 Atlassian Rovo integration Strategy Hub may integrate with Atlassian Rovo, Atlassian's AI-powered assistant platform, to provide AI-enhanced features such as intelligent search, goal suggestions, or conversational interaction with your strategy data. When the Rovo integration is active, certain data from your Strategy Hub instance — such as objective names, key results, or KPI data — may be accessed by Rovo to generate responses or surfaces within the Atlassian platform. The following applies to such processing: - Data accessed by Rovo is processed within Atlassian's own infrastructure and is subject to Atlassian's Privacy Policy and AI usage policies. - Rovo respects your existing Jira permissions model — it will only surface data to users who already have access to it within Strategy Hub. - Rovo may use third-party large language model providers (such as OpenAI, Anthropic, and Google) to generate responses. Atlassian states that these providers do not retain your inputs and outputs or use them to train their models. - Atlassian states that Rovo retains inputs and outputs for a limited period (currently 30 days) for safety and security purposes. - The specific scope of data accessed depends on how the Rovo integration is configured. We will update this section as the integration is developed and scoped. Use of Atlassian Rovo is governed by your Atlassian Customer Agreement and Atlassian's Privacy Policy. For full details of how Rovo processes data, please refer to: ## 6. Data sharing outside the European Economic Area Because Strategy Hub runs on the Runs on Atlassian (Forge) architecture, data stored within the App resides in Atlassian's infrastructure and is subject to Atlassian's data residency commitments under your Atlassian Customer Agreement. To the extent that caskcode processes any personal data outside the App (such as support communications or analytics), such data may be stored on servers within the European Union for EEA End Users and in the USA for US End Users. Where we share personal data with recipients in the USA or other non-EEA countries, we ensure it is protected in accordance with the General Data Protection Regulation. We rely on the adequacy decision of the European Commission or the recipient's participation in the Data Privacy Framework. If a recipient does not participate in the Data Privacy Framework and their country is not deemed adequate, we adopt Standard Contractual Clauses, based on appropriate data protection assessments. ## 7. Data protection We apply security measures appropriate to the risks involved in processing your personal data. In addition, because the App runs on Atlassian's Forge infrastructure, your in-App data benefits from Atlassian's own enterprise-grade security controls. **Organisational measures** - Staff training and awareness - Internal policies and procedures - Non-disclosure agreements (NDA) - Access controls and least-privilege principles **Technical measures** - Two-factor authentication - Encrypted data transmission (TLS) - Firewalls and network controls - Regular backups - Atlassian Forge runtime isolation - Forge Storage encryption at rest ## 8. Data subjects rights As a data subject, you have the right to interact with your personal data directly or by submitting a request to us. The sections below describe your rights depending on your country of residence. ### 8.1 European Economic Area and United Kingdom residents | Right | Description | | ---------------------------- | ------------------------------------------------------------------------------------------------------- | | Right to access | You may request an explanation of how your personal data is processed. | | Right to rectification | You may request correction of inaccurate or incomplete data. | | Right to erasure | You may request deletion of your personal data. We will comply unless retention is required by law. | | Right to restrict processing | You may partially or fully restrict our processing of your personal data. | | Right to data portability | You may request a copy of the data you provided and ask for it to be transferred to another controller. | | Right to object | You may object to the processing of your personal data. | | Right to withdraw consent | Where processing is based on consent, you may withdraw it at any time. | | Right to file a complaint | If your request is not satisfied, you may file a complaint with the relevant supervisory authority. | To exercise your rights, contact us at contact@caskcode.io. **EEA residents:** We will respond to your request within one month. If not satisfied, you may submit a complaint to your local Data Protection Authority. A list is available at . **UK residents:** We will respond within one month. If not satisfied, you may contact the Information Commissioner's Office at 0303 123 1113 or . ### 8.2 United States residents For the purposes of US state privacy laws such as the CCPA, Caskcode acts as a **"business"** for the personal data described in this Policy that we process for our own purposes, and as a **"service provider"** for the strategic content we process on behalf of a customer organisation. Your privacy rights vary depending on your state of residence, as outlined below. | Right | Description | States | | --------------------------------- | ------------------------------------------------------------------------ | -------------------------------------- | | Right to access | Request an explanation of how your personal data is processed. | CA; CO; CT; IN; IA; MT; TN; TX; UT; VA | | Right to correct | Request correction of inaccurate or incomplete data. | CA; CO; CT; IN; MT; TN; TX; VA | | Right to delete | Request deletion of your personal data. | CA; CO; CT; IN; IA; MT; TN; TX; UT; VA | | Right to portability | Request your data and transfer to another controller. | CA; CO; CT; IN; IA; MT; TN; TX; UT; VA | | Right to opt out of sales | Opt out of the sale of personal data to third parties. | CA; CO; CT; IN; IA; MT; TN; TX; UT; VA | | Right to opt out of profiling | Opt out of processing for targeted advertising or profiling. | CO; CT; IN; MT; TN; TX; UT; VA | | Right against automated decisions | Protection against solely automated decision-making without human input. | CA; CO; CT; IN; IA; MT; TN; TX; VA | | Private right of action | Seek civil damages for statutory violations. | CA | To exercise your rights, contact us at contact@caskcode.io. We will respond within 30 to 60 days depending on your state's legislative requirements. If your complaint is not resolved, you may contact the Federal Trade Commission at . **Please note!** Some US states do not have comprehensive privacy laws. Residents of such states are governed by applicable federal law. If your state is not listed above, please contact us. ### 8.3 Do not sell my personal information California residents have the right under the California Consumer Privacy Act (CCPA) to opt out of the sale of their personal information. Caskcode does not sell your personal information to any third party, nor does it use your data as a business model. However, we support the CCPA by allowing California residents to record their preference against any future sale. To do so, please contact us at contact@caskcode.io. ### 8.4 Do-not-track requests California residents using the App may request that we do not automatically gather and track information about their online browsing activities across the Internet. Such requests are typically made through browser settings that transmit signals or other mechanisms allowing consumers to exercise choice over the collection of personal data across third-party websites and online services over time. We currently do not have the ability to honour these requests. We will update this Privacy Policy if our capabilities change. ### 8.5 Canada residents Canadian residents have privacy rights under the Personal Information Protection and Electronic Documents Act (PIPEDA), the Personal Information Protection Act of British Columbia, the Personal Information Protection Act of Alberta, and the Act respecting the protection of personal information in the private sector of Quebec. Under these laws, you have the right to access your personal data, request corrections, and withdraw consent for non-essential processing. To exercise any of these rights, please contact us at contact@caskcode.io. We will respond within 30 days. ## 9. Privacy Policy updates We may update this Privacy Policy from time to time to reflect changes in the App, legal requirements, or our data practices. If changes are material, we will notify you in advance via email or through the App's Atlassian Marketplace page. The current version and effective date are shown at the top of this document. Continued use of the App following the effective date of any update constitutes acceptance of the revised Privacy Policy. For any questions about this Privacy Policy or to exercise your rights, contact us at contact@caskcode.io. --- © 2026 Caskcode · All rights reserved · caskcode --- # Strategy Hub: Security > Strategy Hub's security posture as an Atlassian Forge app that runs entirely on Atlassian's infrastructure, storing no customer data of its own Canonical: https://docs.caskcode.io/strategy-hub/security/ **Security Policy · Version 1.0 · July 14, 2026** This page describes the security posture of **Strategy Hub** for Jira, published by CaskCode. Strategy Hub is built entirely on [Atlassian Forge](https://developer.atlassian.com/platform/forge/security/), Atlassian's managed cloud app platform. That architecture is the foundation of our security model: the app has no servers, databases, or infrastructure of its own — application code runs inside Atlassian's cloud, and customer data is stored in Atlassian-managed storage. ## Hosting and infrastructure - Strategy Hub runs exclusively on Atlassian Forge. We do not operate any servers, containers, or self-hosted services that process customer data. - All infrastructure security — physical security, network security, host patching, encryption at rest, availability — is provided and operated by Atlassian. See the [Atlassian Trust Center](https://www.atlassian.com/trust) for details on Atlassian's certifications and practices. ## Data storage and residency - All customer content created in Strategy Hub (strategic items, comments, settings, backups) is stored in Atlassian-managed Forge storage (Forge SQL, Forge Key-Value Store, and Forge Object Store) within Atlassian's cloud. - Because storage is Forge-hosted, app data automatically inherits your Jira site's **data residency**: if your site is pinned to a region, Strategy Hub's data is pinned to the same region. No action is required from administrators. - Data is encrypted in transit (TLS) and at rest by Atlassian. ## Data leaving the Atlassian platform Strategy Hub sends **no customer content** outside the Atlassian platform. The only data egress is content-free operational telemetry: - **Product analytics** (PostHog, hosted in the EU — Frankfurt, Germany): pseudonymous usage events (feature used, screen viewed). Never item names, descriptions, comments, or any other user-authored text. - **Error monitoring** (Sentry, hosted in Germany): error reports containing technical identifiers and stack traces. Error messages are restricted to entity keys and codes — never user content. All egress endpoints are declared in the app's Forge manifest and disclosed on the Marketplace **Privacy & Security** tab. Session replay, where enabled, masks all on-screen text and images by design. See our [Privacy Policy](https://docs.caskcode.io/strategy-hub/privacy) for full details. ## Access control - The app acts only within the OAuth scopes granted at installation (read-level Jira and Teams scopes plus app storage); administrators review and consent to these scopes when installing or upgrading. - Strategy Hub does not use Personal Access Tokens and does not store any credentials, tokens, or passwords. - In-app permissions (roles such as admin/editor/viewer) are enforced server-side on every request. ## Secure development - All changes are made through version control with code review and a mandatory automated test suite (unit, integration, and end-to-end tests) before release. - Dependencies are monitored and updated regularly. - As a Marketplace cloud app, Strategy Hub is continuously scanned by Atlassian's [Ecoscanner](https://developer.atlassian.com/platform/marketplace/ecoscanner/) security monitoring program. ## Vulnerability reporting If you believe you have found a security vulnerability in Strategy Hub: - Email us at **contact@caskcode.io**, or - Raise a ticket via our [support portal](https://caskcode.atlassian.net/servicedesk/customer/portal/1). Please include steps to reproduce and do not access data that is not yours. We acknowledge reports within 2 business days and remediate confirmed vulnerabilities within the timelines defined by Atlassian's [Security Bug Fix Policy for Marketplace apps](https://developer.atlassian.com/platform/marketplace/security-bugfix-policy/). Vulnerabilities may also be reported through Atlassian's [Vulnerability Disclosure Program](https://www.atlassian.com/trust/security/vulnerability-management), which covers Marketplace apps. ## Incident response In the event of a security incident affecting Strategy Hub, we follow Atlassian's Marketplace incident process: we notify Atlassian promptly, cooperate with their security team, and inform affected customers without undue delay. ## Related - [Privacy Policy](https://docs.caskcode.io/strategy-hub/privacy) — how Strategy Hub collects, stores, and protects personal data. - [Atlassian Forge platform security](https://developer.atlassian.com/platform/forge/security/) — the managed platform security model Strategy Hub inherits. - [Atlassian Trust Center](https://www.atlassian.com/trust) — Atlassian's certifications and infrastructure security practices. --- # Strategy Hub: API overview > Authenticate against the Strategy Hub REST API, read its error and scope conventions, and make your first request Canonical: https://docs.caskcode.io/strategy-hub/api-overview/ Strategy Hub exposes a REST API for reading and writing Strategic Items, Types, Statuses, Status Sets, and Labels from outside Jira. This page covers what every endpoint has in common — authentication, scopes, error handling, and rate limits — so the [API reference](https://docs.caskcode.io/strategy-hub/api) only has to describe what's unique to each endpoint. ## Authentication The API authenticates with Atlassian's 3LO OAuth 2.0 (authorization code) flow. Your integration directs a user through Atlassian's authorization URL, exchanges the returned code at Atlassian's token URL, and calls the API with the resulting bearer token in an `Authorization: Bearer ` header. Every call acts as that authenticated user — it sees and edits only what their Jira permissions and Strategy Hub access already allow. The exact base URL for every endpoint is shown in the [API reference](https://docs.caskcode.io/strategy-hub/api). ## Scopes Request only the scopes your integration needs when starting the OAuth flow. | Scope | Grants | | --- | --- | | `read:items:custom` | Read Items, their details, children, and search results | | `write:items:custom` | Create, update, archive, and restore Items | | `read:config:custom` | Read Types, Statuses, Status Sets, and Labels | | `write:config:custom` | Create, update, and delete Types, Statuses, Status Sets, and Labels | | `read:notifications:custom` | Read a user's notifications and unread counts | ## Errors and rate limits Every error response shares one shape: ```json { "error": { "code": "VALIDATION_ERROR", "message": "startDate must be an ISO date" } } ``` `code` is a stable machine-readable string — safe to match on in your integration. `message` is a human-readable detail that can change without notice. | Code | Meaning | | --- | --- | | `VALIDATION_ERROR` | The request body or query parameters failed validation. | | `NAME_EMPTY` | A required name field was blank. | | `USER_ID_MISSING` | The request needed a user (an Owner, for example) that wasn't supplied. | | `NOT_FOUND` | The referenced Item, Type, Status, Status Set, or Label doesn't exist. | | `FORBIDDEN` | The authenticated user's permissions don't allow this action. | | `INVALID_CHILD_TYPE` | The child Item's Type isn't allowed under the given parent Type. | | `HIERARCHY_VIOLATIONS` | The change would break the Type hierarchy's parent/child rules. | | `CONFIG_MODE_VIOLATIONS` | The change conflicts with the workspace's configuration mode. | | `STATUS_SET_ORPHAN_WARNING` | The change would leave a Status Set with no Items referencing it. | | `LABEL_COLLISION` | A Label with that name already exists. | | `NOT_INITIALIZED` | The workspace hasn't finished setup yet. | | `RATE_LIMITED` | Too many requests. Back off and retry after a short delay. | | `DATABASE_ERROR` | An unexpected storage error. Retry, and open a support request if it persists. | | `UNKNOWN_ERROR` | An unexpected server error. Retry, and open a support request if it persists. | A `RATE_LIMITED` response (HTTP 429) means your integration is calling the API faster than its limit allows. Reduce request frequency and add a short backoff before retrying. ## Quickstart Once you have an access token, list Items with a single authenticated request: ```bash curl "/items" \ -H "Authorization: Bearer " \ -H "Accept: application/json" ``` Replace `` with the base URL shown in the [API reference](https://docs.caskcode.io/strategy-hub/api) and `` with the bearer token from your OAuth exchange. ## Related - [API reference](https://docs.caskcode.io/strategy-hub/api) — every endpoint, request, and response schema. - [Strategic Items](https://docs.caskcode.io/strategy-hub/items) — what an Item is and how it's structured, independent of the API. - [Access and permissions](https://docs.caskcode.io/strategy-hub/access-and-permissions) — how Custom access and system roles shape what an authenticated call can see or change.