Skip to main content

Enabling Intelligence

Enabling Intelligence

What has to be true before a team gets value from Intelligence, in the order it makes sense to do it.

1. Confirm the accounts

Everyone who needs Intelligence needs a SiteTrax.io account and at least one shared project. Without a project there is nothing in scope, and the experience will look empty rather than broken.

2. Confirm the capture

Intelligence reports what was observed. Before rollout, settle whether each gate has capture on both directions and which yard zones are covered. Doing this first prevents a team concluding the product is wrong when the real finding is a blind spot.

3. Have each person publish a profile

Intelligence becomes available to an account once that account publishes the eight-question interview. It is self-service and takes a few minutes. Until then the Intelligence item does not appear in that person navigation.

Ask people to answer honestly rather than aspirationally. The interview asks what costs them the most and where they need visibility; an accurate answer produces a useful coverage review, and a flattering one does not.

A published profile revision

4. Decide the assistant position

Decide whether assistant access is in scope, and which assistant. On Claude Team and Enterprise plans only Owners can add a custom connector; in ChatGPT workspaces an administrator controls whether apps may be added. Settle that before individuals try and fail.

Then decide whether anyone needs the notifications write scope. Most users do not.

5. Retire the old references

Update runbooks, bookmarks, onboarding material and saved links that point at service.sitetrax.io. The current application is app.sitetrax.io.

A rollout that works

  1. Start with one site and a handful of people who feel a specific pain, such as detention disputes.
  2. Have them publish profiles and work the coverage review to a conclusion.
  3. Connect one assistant for that group.
  4. Compare an assistant answer against the application for the first week until the team trusts it.
  5. Expand once they can explain the difference between a reading and an event.