Data sharing with Workforce Intelligence
Choose whether bug reports also send Workforce Intelligence a small technical summary, review the text a person, a Coworker or an app wrote for a report before it is sent, see exactly what is sent and what never is, and turn sharing off.
Bug reports filed in your deployment stay in your deployment. If you choose, each report can also send Workforce Intelligence a small technical summary so problems can be found and fixed sooner. Reports, and any text in them, are shared only if you turn sharing on. Workforce Intelligence always knows this deployment's ID, company name and version, whether or not sharing is on (see This deployment's ID).
Where the setting is#
Open Settings, then Data sharing. Only people with the admin ability see this page.
The Share bug reports with Workforce Intelligence card holds one switch. It is off in every deployment
until an administrator turns it on.
Turn sharing on#
- On the Share bug reports with Workforce Intelligence card, switch it on.
- Read the confirmation, Share bug reports with Workforce Intelligence?, which lists what is and is not sent.
- Select Turn on sharing.
Once it is on, the card shows who turned it on and when, and the result of the most recent item. Turning the switch on or off is recorded in the audit log as Sharing with Workforce Intelligence; see Audit log.
What is sent#
For each bug report filed after you turn sharing on, Workforce Intelligence receives only these fields:
- The report's identifier (a random identifier, not the report's text).
- When the report was filed.
- Who filed it, as a kind only: a person, a Coworker, an App or the service itself.
- The error category: empty model response, tool error, confusing tool result, navigation trouble, user report or other.
- The product version you are running: the build identifier of your installed image, such as
sha-1a2b3c4. An update changes it; nothing in your configuration sets it. - For reports of an empty model response only, technical diagnostics: the provider name, the model requested and the model served, the stop reason, token counts (input, output, cache read, cache write and reasoning) and the trace identifier.
- Only after an administrator reviewed it: the text written for the report. That is the description a person chose to share for that one report, or the summary and the detail a Coworker or an app wrote. See A description a person chooses to share and Reports a Coworker or an app files.
Every value is checked against a fixed format before it is sent. A value that does not fit is left out.
A description a person chooses to share#
While sharing is on, the Report a problem form shows an unchecked box, Also send my description to Workforce Intelligence, under the description. It is off for every report unless the person ticks it. When it is ticked, a preview titled Workforce Intelligence will receive exactly this text: shows the text as it would be sent. While sharing is off the box does not appear, and nothing is queued.
- Only a report filed by a person through that form carries the person's description, and only when they tick the box. Nothing is ever written or copied into a person's description automatically.
- Line endings are made uniform, control characters are removed, and at most the first 2000 characters are sent. The form and the review card say Only the first 2000 characters are sent. when the text is longer.
- A report with a description is not sent on its own. It waits for you. A report without text is sent automatically, as described above.
Reports a Coworker or an app files#
A Coworker or an app can file a bug report of its own, with a summary and a detail: the output or notes it attached. That text is written by the Coworker or app, so it may include information from your work. It is never sent on its own.
- While sharing is on, a report a Coworker or an app files with any text waits for your review, in the same Waiting for your review card. Nothing the Coworker or app wrote leaves your deployment until you send it.
- A Coworker or app report with no text is sent automatically, with only the fields listed above.
- Reports from the service itself (an empty model response, for example) are never held and never carry text. They are sent automatically with only the fixed fields and diagnostics.
- The category a Coworker or an app chose is not sent as written: it is sent as other unless it is one of the fixed categories.
Review text before it is sent#
When a report is waiting, the Waiting for your review card appears on Settings, Data sharing, and a count appears on Settings in the avatar menu (and in the phone menu) so you can find it. The card title shows how many reports are waiting, such as Waiting for your review (7).
The list is collapsed. Each report is one row showing who filed it (Person, Coworker or App, never a name), when it was filed, and a one-line preview of its summary (No summary when it has none). A Has detail tag marks a report that carries a detail. The list shows the first 5 reports. Below it, Showing 5 of 12 says how many are on screen and Show 5 more reveals the next ones.
Select a row, or its Review control, to open it. One report is open at a time: opening another closes the first, and text you changed is kept while the row is closed. An open report shows the full information. For a Coworker or an app, a warning reads This text was written by a Coworker. It may include information from your work. Read it before you send it. and there are two text boxes you can change:
- Summary to send, up to 2000 characters.
- Detail to send, up to 4000 characters. It holds everything the Coworker or app attached, as plain
text: each item has a heading line such as
ls_output:followed by its text with the original line breaks. Remove anything you do not want to send.
A report a person filed has one box, Description to send. Each box shows a character count and says Only the first 2000 characters are sent. (or 4000 for the detail) when the text is longer. The report also lists the other fields that go with it: who filed it, the category and the version.
- Send to Workforce Intelligence sends the report with the text as it is in the boxes. Clear a box to leave that part out. When every box is empty the button reads Send without text and the report is sent with only the fixed fields.
- Don't send (after a confirmation) discards the report's sharing: Workforce Intelligence receives nothing for it. The report itself stays on the Bug reports page.
- A report you leave for 14 days is not sent. It is closed as not shared and its text is removed from the queue.
- Turning sharing off also closes every report that is still waiting, and removes its text from the queue.
Sending a description is recorded in the audit log as Sent a bug report to Workforce Intelligence and discarding one as Chose not to send a bug report to Workforce Intelligence. The entries record which report, whether each text was edited and how long it was, never the text.
Text that has been sent cannot be recalled by your deployment. Deleting the local report, or erasing the person who wrote it, removes the copies held here (text still waiting for review is dropped and never sent), but it does not remove what Workforce Intelligence already received. Workforce Intelligence keeps a report, including its text, for 180 days.
What is never sent#
- Conversation content and documents.
- Names and email addresses, including the name of the person who filed the report.
- Text a person, a Coworker or an App wrote for a report, unless you reviewed it on the Waiting for your review card and chose to send it. A person's description also needs that person to have chosen to include it for that report.
- Conversation content, documents, names, email addresses and keys stay out on their own. They reach Workforce Intelligence only if they appear in text you choose to send, so read that text first.
- Page addresses, and the identifiers of conversations, Coworkers and Apps.
- Keys and other secrets.
Reports filed before you turned sharing on are never sent.
See exactly what was sent#
On Settings, Data sharing, the Recent items card lists items that were shared, are waiting to be shared, or could not be shared. The list shows the 10 most recent items, with Showing 10 of 25 and Show 10 more to reveal older ones. Each row shows When, Status (Shared, Waiting, Waiting for review, Could not be shared or Not shared) and a button that opens the exact content of that item. The button says What was sent for a shared item, What will be sent for an item that is Waiting or Waiting for review, and What was not sent for an item that Could not be shared. An item that is Not shared has no button, because nothing was sent.
The Bug reports page shows the same status for each report while sharing is on, with the same button, worded the same way for each status.
Turn sharing off#
Switch Share bug reports with Workforce Intelligence off. The change applies at once:
- No new report is queued.
- Items still Waiting or Waiting for review are not sent.
- Anything already shared with Workforce Intelligence is not removed. Deleting a report on the Bug reports page removes it from your list only.
When Workforce Intelligence's service cannot be reached#
Sending never affects the person who files a report. The report is saved in your deployment and stays visible on the Bug reports page either way. If Workforce Intelligence's service cannot be reached, the item shows Waiting and is tried again, up to five attempts in all: straight away, then after 1, 3, 6 and 12 hours. If the fifth attempt also fails (about 22 hours after the report was filed), or if Workforce Intelligence's service rejects the item, it shows Could not be shared and is not sent again.
This deployment's ID#
On Settings, Data sharing, the This deployment card shows the Deployment ID, with a Copy button, the Company name sent, and a short status line.
- Connected to Workforce Intelligence means Workforce Intelligence has accepted this deployment's ID.
- Connecting… means it has not yet. The deployment keeps trying in the background, so nothing needs to be done.
The first time the application starts, it creates a signing key pair for this deployment. The ID is derived from the public half of that key (the first 32 characters of its SHA-256 hash). The application then tells Workforce Intelligence the public key, together with a signature that proves it holds the private key. This happens automatically, whether or not sharing is on, and it never delays or blocks startup. Workforce Intelligence stores only the public key and the ID, plus when the deployment was registered, when it was last heard from and whether it is active, and your company name. It does not store your host name, address or any content, and the ID identifies no person.
The company name#
The deployment sends your company name every time it sends its ID, so Workforce Intelligence can tell whose deployment a call came from: once when it connects, and on every bug report. It is sent whether or not sharing is on, because it describes the deployment, not the content of any report. It is shown only to Workforce Intelligence's operators and never changes what the deployment may do.
- The Company name sent line on the This deployment card shows exactly what is sent, or No company name set when the company name is empty.
- To change it, rename your company in Settings, Company. The new name is picked up within a minute and sent to Workforce Intelligence at the next connection check (within about five minutes), and goes with every bug report from then on.
- The name is sent with line breaks and other control characters removed, and at most the first 100 characters.
The private key is stored encrypted in your database under your master key (WI_MASTER_KEY), like
provider keys. It is never shown, logged or sent. It survives updates, container recreation and a master
key rotation. Because it lives in the database, a restored backup or a database copy carries the same
identity: two deployments started from the same data share one ID, so use a copy for recovery only.
While a deployment is not connected, a bug report that is ready to share stays Waiting and is sent once the connection is made. This wait does not count toward the five attempts. When connected, every bug report is signed with the deployment's key. If an operator at Workforce Intelligence revokes a deployment, Workforce Intelligence refuses its reports, which then show Could not be shared, and the deployment stops trying to connect until the application restarts. Everything else in the product keeps working.
The first connection is recorded in the audit log as Connected this deployment to Workforce Intelligence; see Audit log.
Network and configuration#
The application makes an outbound HTTPS connection from the app container to the address in
WI_CENTRAL_URL (see Configuration reference).
It makes one small call to connect the deployment's ID and company name, whether or not sharing is on, and retries it in
the background (after 5 and 15 minutes, then every hour and eventually every 6 hours) until it
succeeds. Bug reports are sent over that connection only while sharing is on. If your firewall blocks
it, nothing else in the product is affected: the ID shows Connecting…, and reports are kept locally
and show Waiting, then Could not be shared. Redirects are not followed.