Latest product releases: August 2026

Each item below shows who can use the change:

• Directory and above — everyone and above (including Power and Admin)
• Power and above — leaders and planners and above (including Admin)
• Admin — workspace and tenant administrators
• Reporting — Reporting add-on

Product Releases

Org Design: Org Chart — Attribute overlays and editable person fields

Person cards on the org chart can show tags and people attributes — for example cost centre or job data from your HR system — as small badges, so missing or present data is easy to spot.

Where enabled, admins can also fix those person fields in the Details panel without leaving the chart. Everyone else can still see the badges.

Why it matters: You can review structure and people data in one place, and admins can correct obvious import issues on the spot.

Where to find it: Open a team → Org chart → Properties (People attributes), then click a person for Details.

Talk to Customer Success or Support for a demo.

Org Design: Org Chart — Reporting-line view and drag to reassign

Reporting line used to be guessed from team ownership, so managers could look wrong and you could not change who someone reports to on the chart.

Reporting-line view now follows real manager data and shows people only (positions stay on the team structure view). Drag a person onto another person to change who they report to. If that manager already owns a team, you can leave their allocation as-is or move them onto one of those teams. Owner badges appear when the owner is not a team member.

Why it matters: Manager changes are often the first thing reviewers look for — you can now make and see them on the chart.

Where to find it: Same Org chart tab → View reporting line.

Talk to Customer Success or Support for a demo.

Ask TeamForm AI — longer answers and a dashboard library

Complex org-wide queries and dashboards could time out, look stuck, or lock the composer.

If you already have Ask TeamForm, longer answers keep going with clearer live activity, and the composer unlocks when the answer arrives. You can rename or delete AI dashboards from the sidebar. Where data-driven dashboards are on, you can start from a library of org and personal templates (each launch builds a new dashboard for you). Pie and donut charts no longer draw stray axes.

Why it matters: Bigger questions and reusable dashboards work in product instead of timing out or living as one-off chats.

Where to find it: Sidebar → Ask TeamForm, and Dashboard library.

Talk to Customer Success or Support for a demo.

Product Improvements

Org Design — Change log: more change types and correct dates

If you already use Org Design, the change log now records owner, manager, title, and band changes, and dates them as of the organisation date (the date that matters for HR), not only the day the change was typed in. Layout is clearer, and Insights no longer duplicates a change preview (the changelog stays on its own tab). Comment dates follow the date format set for your workspace.

Why it matters: Design reviews and exports match what actually changed, on the dates that matter.

Where to find it: A team → Change log tab.

Talk to Customer Success or Support for a demo.

Org Design — Team owner overlay

You can edit the team owner in place on the owner pill (header, card, and details stay in sync). Removing a team is limited to edit mode, so browse views stay safer.

Why it matters: Ownership changes are quicker and less error-prone during a redesign.

Where to find it: Team header, org-chart card, and team details.

Future enhancements will bring this to work with Demand team types as well and then also regular TeamForm so that you no longer have to maintain this context via tags manually.

Talk to Customer Success or Support for a demo.

Planner & Forecast — tags, Actuals, and supply targets

Forecast and Planner now show featured team tags next to names, member tags on planning rows, and clearer rollup grouping. Actuals line up with target headers. Demand FTE respects workspace decimal settings, and unsaved cell edits survive a refresh of the model. Member tag fields are easier to work with.

Where enabled, supply forecast can show targets the same way demand already does, and planners can add tags to a team from inside Planner / Forecast.

Why it matters: More consistency across interfaces, more flexible uses for tags.

Where to find it: A demand team → Forecast or Planner.

To turn it on:

1. Tags next to names and Actuals alignment need no extra flag if Planner / Forecast is already on.
2. Adding tags from Planner / Forecast: a workspace admin turns on Enable adding tags to teams inside Planner and Forecast in Settings → Planner features config and use "show tag type in" in Settings → Manage Tags
3. Supply targets: a workspace admin turns on Enable supply forecast targets in Settings → Forecast config (Forecast constraints must already be on).

Forecast — large page loading

Very large demand-request Forecast pages load more reliably. The page layout appears first; scheduled (purple) FTE numbers fill in when ready, instead of flashing 0. Some remaining hang cases are still being fixed.

Why it matters: Finance-level views are more usable on big pages.

Where to find it: Forecast on large teams (no new flag — for workspaces that already use Forecast).

Jira integration — scoped tokens and managed teams

Jira Teams Export can use scoped Atlassian API tokens (plus cloud ID) and a managed-teams path that matches how Jira Cloud works today. Errors are clearer when a team or membership update cannot be applied.

Why it matters: Admins can keep TeamForm teams in sync with Jira without relying on classic API tokens that were starting to fail.

Where to find it: Settings → Jira Teams Export (or Data integrations → Jira). Look for scoped token and cloud ID fields.

To turn it on:

1. Ask Customer Success to enable Jira Teams Export.
2. A workspace admin pastes the scoped token and cloud ID in the export settings.

Tags — edit unique attributes without full edit mode

When a tag has unique (per-person or per-team) attributes, you can edit those without putting the whole tags editor into full edit mode. Shared / global tag changes still need edit mode.

Why it matters: Small attribute fixes are faster and safer.

Integration Workflows and Admin Settings

Admins can download a CSV of who has access to which teams, request single sign-on (SSO) from settings instead of raising an engineering ticket, and rename or disable tag values in catalog import. Allocation notification emails can be limited to a population, and recipient tags (such as role tags) are accepted.

If Workflows is on, admins can also:

• Opt a workflow into reinstating departed people (off by default)
• Use secure file transfer extracts (SFTP), optionally with encryption (PGP)
• Download file on a completed step whose output is stored

Why it matters: Access reviews, SSO, and tag catalogue work can be done in product at the scale admins actually run them.

Where to find it: Settings (access CSV, SSO request, tag catalog import, allocation notification population). Workflows → completed step → Download file, when Workflows is on.

To turn it on:

1. Access CSV, SSO request, tag import, and allocation-email population need no feature flag.
2. Workflows: a workspace admin turns on Enable Workflows in Settings → Workspace settings → Feature toggles.
3. Reinstating departed people is then an option on the workflow (default off).

Coming Soon

Roadmap horizon — proposed placement pending team confirm. These are not generally available. Talk to Customer Success or Support for a demo.

Positions — funded seats for org design and planning

In most HR systems a job is the abstract work, a position is the budgeted seat (whether or not someone sits in it), and a person occupies that seat. Until now TeamForm mostly saw people — when someone left, the vacancy disappeared from the chart and the plan.

Positions add the seat layer: filled, vacant, or shared seats next to the people in them. That is how org design and workforce planning stay aligned with establishment (the seats you funded) vs who is in the building this week.

Why it matters: Org design and planning need the roles you approved, not only who is present this week.

• Workforce → Positions: occupancy, FTE, managers, Fill / Vacate (one seat can be shared)
• Dedicated position page (Details + History)
• Vacancy badge in global search when Positions is on
• Org chart team structure: people nested in seat boxes; Show positions and Show people can be independent
• Tags on positions (admin can allow tag types on positions)
• Requisitions / hiring requests that stay on the position, including ending a seat and opening a successor on another team
• Positions and requisitions in Planner / Forecast

Org Design — Design options

Compare design options as overlays on the same structure, without forking the whole workspace. Creating, renaming, and switching options is landing behind a flag; more of the chart editing experience is still in progress.

Why it matters: Reviewers can compare scenarios side by side instead of maintaining separate copies of the org.

Org Design — Change log summaries and export

Summaries of people and team changes over a period, with export to support moving a design into your people systems. Richer changelog rows this month are the groundwork.

Why it matters: Design sign-off and HR handoff need a clear period summary, not only a raw row list.