Release Notes

Google Workspace directory field mapping arrives for admins

This release lets admins choose exactly which Google Workspace directory fields fill in Division, Department, Team, and Office, instead of Abloomify guessing. It also keeps Company Structure edits from losing your place, adds bulk delete for org units, and fixes several smaller issues in Roles & Permissions, org chart exports, and the macOS device agent. Each change is available now.

What's new

Map Google Workspace fields to your org structure

Google Workspace sync now follows an admin-configured mapping instead of guessing which field goes where.

• Admins can map Google Workspace directory fields, including department, employee ID, building ID, and the levels of your organizational hierarchy, to Abloomify's Division, Department, Team, and Office fields, per connection.
• A preview shows what each Google field contains before the mapping is saved.
• Employees synced from Google Workspace now stay linked to the departments and teams already created in Company Structure, instead of drifting to duplicates.
• Employee numbers entered by hand are no longer overwritten when a sync finds no value from Google.

Company Structure edits hold their place

Editing your org structure no longer resets you back to page one or collapses what you had open.

• Renaming or editing a team, department, division, or office keeps the page, open sections, and current view exactly where you left them.
• Admins can bulk delete multiple teams, departments, divisions, or offices at once, with a confirmation step before anything is removed.
• The active tab in company settings is now saved in the page's URL, so a reload or a shared link opens to the right tab.

Fixes in Roles, org charts, and device agents

A handful of smaller fixes landed across Roles & Permissions, org chart exports, and the macOS device agent.

• Role cards in Roles & Permissions now show the same active-employee count as the employee table.
• Hovering an avatar in Roles & Permissions now shows the employee's preferred name.
• Org chart exports no longer break when a teammate's profile photo fails to load; a placeholder appears instead, and the exported image now captures the full org chart.
• A failed org chart download now shows a visible error instead of failing silently.
• The recommended macOS device agent, version 1.16.1, fixes a permission prompt that could interrupt setup.

Who benefits

• Admins configuring Google Workspace sync: choose exactly which directory fields set division, department, team, and office, with a preview before saving.
• Admins managing Company Structure: edit and bulk delete org units without losing your place, and share direct links to a specific settings tab.
• HR and IT admins relying on Google Workspace sync: employees stay linked to existing departments and teams, and employee numbers entered by hand are no longer overwritten.
• Anyone using Roles & Permissions or org chart exports: see accurate employee counts, preferred names on hover, and exports that hold up even when a profile photo fails to load.
• Teams using the macOS device agent: a fixed permission prompt keeps setup moving.

Try it

• Open a Google Workspace connection's settings to map directory fields to Division, Department, Team, and Office.
• Edit or bulk delete teams, departments, divisions, or offices in Company Structure without losing your place.
• Check Roles & Permissions for accurate active-employee counts and preferred names on hover.
• Export your org chart and confirm it includes the full chart and handles a missing profile photo cleanly.
• Update the macOS device agent to 1.16.1 if setup previously showed a permission prompt.

Background activity comes to the Activity Log

This release adds background app activity, open in background, minimized, and running with no window, into every view of the Activity Log. It also fixes device agent installer downloads and status display for teams on the EU app, and lets Bloomy answer questions from complete long documents instead of a truncated excerpt. Each change is available now.

What's new

Device agents work reliably in the EU app

Two separate issues affecting only the EU app are fixed.

• Device agent installer downloads and the agents' own self-update process now complete successfully for EU app tenants, instead of failing.
• The EU device agent console now shows the real collection state, active or not, for tenants that never saved an allow-list setting, instead of an inaccurate default.
• Where that state shows no addresses collected, admins get a one-click action to switch to collecting everything.

Background activity in the Activity Log

Background app activity is now part of the Activity Log everywhere the log appears.

• The Activity Log now includes background activity, open in background, minimized, and running with no window, next to active time in the table, CSV exports, day timeline, and Top Apps chart.
• A new toggle in the Columns menu turns background activity on or off. It is on by default and explains itself when a scope has none to show.
• The Top Apps chart tooltip now reliably shows the app being hovered, including on a chart with a single bar, and adds a "Top users" section naming who used that app most.
• The day timeline labels its active and background rows directly, so the two read apart at a glance.

Bloomy answers from complete documents

Bloomy no longer stops partway through a long document.

• Bloomy no longer stops partway through a long document with no way to continue; it now works through the complete document across as many passes as needed.
• Questions about long documents, such as extended transcripts or reports, are now answered from the full document instead of a truncated excerpt.
• This removes a limit that previously affected any long document Bloomy is asked about.

Who benefits

• Admins managing device agents in the EU app: installer downloads and self-update work correctly, and the console shows the real data-collection state, with a one-click switch to collect everything.
• Managers and admins reviewing the Activity Log: see background activity everywhere the log appears, with a reliable Top Apps tooltip and a per-app top users view.
• Anyone asking Bloomy about long documents: gets an answer built from the complete document instead of a truncated excerpt.

Try it

• Reconnect or update device agents in the EU app if downloads or self-update previously failed.
• Open the EU device agent console to confirm the collection state matches what you expect, and switch to collecting all addresses if needed.
• Turn on "Show background activity" in the Activity Log's Columns menu, or check the Top Apps chart for per-app top users.
• Ask Bloomy about a long document, like an extended transcript or report, and expect a complete answer.

Tech Usage arrives in Engineering Insights

This release adds a permissioned Tech Usage tab to Engineering Insights, corrects how its usage counts handle departed employees and growing tool catalogs, and brings Bloomy's Tech Usage answers in line with the tab's own permissions. Each change is available now.

What's new

Permissions, export, and more views for Tech Usage

Admins can now control who opens Tech Usage and who sees it broken down by employee.

• New "View Tech Usage" and "Tech Usage - Employee Filter" permissions let admins grant access per role; only admins see the tab until it is granted to others.
• Tech Usage now exports to Excel, with an optional employee-level breakdown sheet.
• The Usage Over Time chart adds a "Users" view, showing how many distinct people used a tool, alongside the existing hours view.
• Tech Usage supports the same Physical / Virtual device filter already available in Usage Insights.

Tech Usage keeps departed employees in the count

Tech Usage numbers now correctly handle employees who leave mid-period, cleared filters, and duplicate tool entries.

• Employees who left partway through the selected date range now stay counted for the time they were employed, instead of dropping out of the whole range.
• Resetting filters now clears every Tech Usage picker, including employee and category selections along with the date range.
• Chrome no longer shows up twice in the tool list; its usage rolls into a single Google Chrome entry.
• The Users chart's axis is labeled to show it counts people per day, week, or month, not the total across the whole range.

Bloomy answers Tech Usage questions

Bloomy can now answer Tech Usage questions with the same permissions, scope, and completeness as the tab.

• Bloomy's Tech Usage answers now follow the same permissions as the tab: employees without access are told so, and employee-level detail is withheld exactly where the tab would withhold it.
• Bloomy's Tech Usage answers used to time out on larger date ranges; they now complete reliably.
• Bloomy now defaults to the organization's full Tech Usage scope, matching the tab, instead of narrowing to a single person's team when no scope is specified.
• Bloomy's answers now include employees who left partway through the period and newly added tools in busy categories, and say when data is incomplete instead of showing a lower count without explanation.

Who benefits

• Admins managing Engineering Insights access: can grant View Tech Usage and Employee Filter permissions per role, and export tool usage to Excel.
• Engineering leaders reviewing tool adoption: get a Users view alongside Hours, a Physical / Virtual device filter, and counts that correctly include employees who left mid-period.
• Anyone asking Bloomy about tech usage: gets answers that respect the same permissions as the tab and complete without timing out.
• Teams tracking a growing tool catalog: no longer see usage silently undercounted when a tool is newly added or data is incomplete.

Try it

• Open Engineering Insights and confirm your role has the new View Tech Usage permission.
• Export Tech Usage to Excel, including the optional employee breakdown.
• Switch the Usage Over Time chart to "Users," or filter by Physical / Virtual devices.
• Ask Bloomy about your team's tech usage; grant the Employee Filter permission to get employee-level answers.

Background app activity tracking, named meeting participants, and Bloomy Tasks that deliver again

This release adds visibility into background app activity for allow-listed apps, corrects who gets named in device meeting recordings, and fixes a configuration issue that could stop certain scheduled Bloomy Tasks from delivering a result. Each change is available now.

What's new

Background app activity in Usage Insights and Bloomy

Admins with an enforced app allow-list can now see how those apps are used even when they are not the focused window.

• Turn on "Collect background app activity" for Windows or macOS devices; it applies to the same apps already on your allow list, and turning it on and choosing its audience now saves in a single step.
• Usage Insights' Activity Log tab gains a Background apps card showing, per employee and app, how much time was spent running in the background, minimized, visible on screen, or focused, including how much of that time was on a secondary monitor.
• Bloomy can now answer questions about background app activity using the same data as the new card.
• The background activity switch moved to a cleaner spot in Collection settings, and the Background apps card's legend no longer overlaps its labels.

Meeting recordings name the right participant

Device meeting recordings on macOS now identify who is speaking instead of using a generic label.

• The recording participant's own voice is now labeled with their name in the transcript, or as "Me" when their identity cannot be resolved.
• Company search and knowledge base results no longer list "Speaker 1" or "Me" as separate people.
• Applies to recordings captured on macOS agent 1.13.7 or newer; earlier recordings keep their existing labels.

Bloomy Tasks deliver results again

A configuration issue that could stop certain scheduled Bloomy Tasks from delivering a result is fixed.

• Scheduled Bloomy Tasks using certain AI models now run and deliver results instead of failing without explanation.
• Task model settings, including which AI provider and effort level a task uses, now save and persist correctly.
• A retired AI model in a task's settings now shows the current default instead of displaying incorrectly.

Who benefits

• Admins managing device agent rollouts: can turn on background app activity tracking for allow-listed apps and review it in Usage Insights.
• Anyone using Bloomy to ask about app usage: gets background activity answers from the same data as the Usage Insights card.
• Teams reviewing meeting recordings: recordings captured on macOS name the actual participant instead of "Speaker 1."
• Bloomy Task owners: scheduled tasks using AI models complete their runs and keep their saved settings.

Try it

• Turn on "Collect background app activity" from Device Agents admin (requires Windows agent 1.12.0 or macOS agent 1.16.0 or newer).
• Check the new Background apps card under Usage Insights, Activity Log tab.
• Ask Bloomy about background app activity for a quick summary.
• Confirm your macOS agents are on 1.13.7 or newer to get named meeting participants in recordings.

Per-employee targeting for device agent features, corrected Bloomy links, and accurate Usage Insights

This release lets admins target specific device agent features to select employees, teams, departments, or divisions instead of turning them on for the whole company. Bloomy links opened from the macOS agent menu and from search previews now resolve to the correct document, and Usage Insights no longer double-counts browser time for employees on Edge, Safari, or Firefox.

What's new

Per-employee targeting for device agent features

Admins can now narrow who receives specific device agent features instead of only choosing company-wide on or off.

• The menu-bar icon, AI Central Memory, and Meeting Notes can each be limited to specific employees, teams, departments, or divisions, with a searchable preview of who's included before saving.
• Turning on a narrowed feature and choosing its audience now saves in a single step instead of two.
• The recommended macOS agent version is now 1.13.6.

Bloomy opens the right document every time

Links into Bloomy from the macOS agent menu and from file previews now resolve to the exact file instead of a mismatched one.

• Recordings and documents opened from the macOS agent menu now open directly to the correct file in Bloomy.
• "View in Bloomy" no longer opens the wrong file list when loaded from a fresh page.
• Bloomy's model catalog reflects updated capability and pricing details for supported Claude, GPT-5.6, Gemini, and Kimi models.

New-account defaults and Usage Insights accuracy

New accounts start with the right defaults, and browser time in Usage Insights now reflects actual usage.

• Companies created through self-signup now start with the standard set of productivity categories, so device usage labeling works from day one instead of requiring a support fix.
• An account-setup issue on one company's data no longer interrupts nightly usage and activity updates for other companies.
• Usage Insights no longer double-counts browser time for employees on Edge, Safari, or Firefox; screen-time totals now reflect actual usage instead of an inflated total.

Who benefits

• Admins managing device agent rollouts: can limit the menu-bar icon, AI Central Memory, or Meeting Notes to specific employees, teams, departments, or divisions.
• Anyone opening recordings or documents from the macOS agent or Bloomy: links and previews now open the correct file.
• New companies signing up directly: productivity categories and device usage labeling are ready from day one.
• Leaders reviewing Usage Insights: screen-time totals for employees on Edge, Safari, or Firefox are now accurate.

Try it

• Open Device Agents admin to limit a feature's audience or confirm the recommended macOS agent version (1.13.6).
• Review the Bloomy model catalog for updated capability and pricing details on supported models.
• Check Usage Insights for corrected screen-time totals on non-Chrome browsers.

Accurate engineering metrics, a Get Documents tool for connected assistants, and self-healing meeting recordings

This release corrects how Cursor usage, company-wide totals, and DORA deployment metrics are calculated across Metrics Explorer, the engineering dashboard, and Bloomy chat. MCP-connected assistants such as Claude Desktop gain a way to retrieve full documents after a search, and meeting recordings recover automatically instead of getting stuck.

What's new

Accurate Cursor and company-wide metrics

Cursor usage and company-wide totals now calculate correctly everywhere they show up.

• Cursor usage data (accepted code suggestions, tab completions, and agent requests) now populates reliably across the AI-Assisted Engineering card and Metrics Explorer, instead of showing blank or stale numbers.
• Company-wide totals, like total licensed seats, now show today's actual count in Metrics Explorer instead of an inflated sum across the selected date range.
• Team-wide adoption rates, like Cursor's suggestion-acceptance rate, are now calculated correctly instead of overstating actual usage.
• Asking Bloomy about company-wide numbers, like total Cursor seats or GitHub activity, now returns an answer instead of "no data found" for every company.
• Task and reminder mentions in Bloomy notification emails now render as clickable links to the task, instead of raw text markup.

DORA counts merge-based deployments correctly

DORA deployment tracking adds a per-repo setting for teams that deploy on merge, and gets easier to follow.

• Repos where deployment happens automatically when a pull request merges, rather than through a separate release step, can now be set to count merges as deployments, so deployment frequency is no longer undercounted.
• Deployment rows in the DORA view now link directly to GitHub, with the pull request title shown inline.
• A crash that could interrupt DORA reporting for companies with data split across two regions is fixed.
• Bloomy's DORA answers in chat now reflect the same per-repo deployment setting shown on the dashboard.

Full document retrieval for connected assistants

MCP-connected assistants, like Claude Desktop, can now fetch full documents and page through search results without hitting old limits.

• MCP API keys can now grant access to a Get Documents tool, so a connected assistant can pull the full content of a specific transcript, coding session, or upload after finding it in search.
• Filtering search results by document type now actually filters, instead of silently ignoring the filter and returning mixed results.
• Paging through a long list of documents no longer risks looping back to the start if a page token gets corrupted.
• External MCP clients can now request up to 200 results per page instead of 50.

Meeting recordings recover automatically

A recording from a device that isn't yet matched to an employee now recovers on its own, and Google Meet transcripts show real participant names instead of raw identifiers.

• Google Meet transcripts that previously showed raw system identifiers instead of participant names now show clear labels, and can pull in real names and meeting subjects from your calendar when available.
• A meeting recording from a brand-new or not-yet-matched device now recovers automatically within a day, instead of staying stuck until someone manually reruns it.
• The recommended macOS device agent (now 1.13.3) no longer lets itself update in the middle of an active meeting recording.

Who benefits

• Engineering leaders reviewing Cursor and DORA data: accurate usage, seat, and deployment numbers across Metrics Explorer, the dashboard, and Bloomy chat.
• Teams whose deployment process ships on merge: DORA deployment frequency is no longer undercounted, once configured per repo.
• Developers and admins connecting AI assistants like Claude Desktop over MCP: access to full documents by ID, and pagination that no longer loops on a bad page token.
• Anyone reviewing meeting recordings or transcripts: fewer stuck recordings, and participant names that show correctly on Google Meet calls instead of raw system identifiers.

Try it

• Review the AI-Assisted Engineering card or Metrics Explorer to see corrected Cursor and company-wide totals.
• Set a per-repo deployment signal in your DORA settings if your team deploys on merge.
• Grant the Get Documents tool to an MCP API key from your connector settings.
• Check Device Agents for the recommended macOS agent version (1.13.3).