navieo

Live Guidance & Privacy

Availability: live guidance is supported by React 3.0.0 with Core 2.0.0 and Types 3.0.0. Check Release compatibility before enabling it in your integration.

Viewport requirement: below 768 CSS pixels, the SDK hides the widget and disables the assistant and live guidance; widen the browser window to use them.

How guidance works

Live observation supplies the inventory; explicit policy determines eligibility; Google chooses among eligible controls; the user acts; fresh observation verifies progress.

  1. The SDK observes supported controls on the current page. Your scanned sitemap supplies destinations, names and context, so keep the scan up to date after changing your application.
  2. Navieo filters out unsupported actions, controls you have excluded and unavailable destinations.
  3. Google chooses among the permitted options. It does not operate your application or override permissions.
  4. Accept Take me there to start guidance. Navieo highlights the control; you click it.
  5. Navieo checks the resulting page and any required destination controls before completing guidance.

A visible link can be used even if the scanner did not map that individual link, provided its destination is indexed and the link meets the guidance policy. Without usable page information, Navieo may answer without offering a guide.

Page titles and headings help identify destinations. Route hierarchy supplies context—for example, distinguishing account settings from settings for the current project. Ask for the scope you mean; you can request account settings while viewing a project. Better descriptions improve context but do not grant access to restricted destinations.

Guidance enabled or informational only

New apps and compatible SDK providers enable live guidance by default. Either the app's Settings → Widget → Live guidance setting or enableDynamicNavigation={false} can disable dynamic offers while retaining informational answers. An SDK opt-in cannot override the app setting. Existing explicit opt-outs are preserved.

// For Next.js App Router with React SDK 3.0.0:
<NavieoNextProvider enableDynamicNavigation={false}>
  {children}
</NavieoNextProvider>

This controls question-driven guidance, not the separate authored-tour trigger configuration. Hiding the widget is also a separate presentation setting; it is not an authorization control.

When disabling guidance takes effect

Disabling guidance can take up to five minutes to apply across the service. During that window another request may still receive an offer or continue guidance. SDK configuration refreshes separately; refreshing one browser does not make the change immediate across the service. This setting is not an immediate emergency stop or access-revocation mechanism.

Use Stop to end the current guide. The host application must continue enforcing its own authentication, authorization and business-action permissions. Do not rely on Navieo's guidance toggle to protect a sensitive operation.

Live-label consent is checked independently: the backend re-reads it for each page-planning request and excludes labels if consent is off or unavailable. It does not inherit the five-minute server guidance-permission cache. An already-mounted SDK may still hold older capture configuration until refresh; backend consent checks prevent using those labels for selection after revocation. Turning consent off cannot retract information already shared.

Observation and optional live labels

Navieo uses a limited snapshot of supported controls, rather than a recording of everything on the page. It rechecks that a target is still available before highlighting it. Very large or changing pages may not provide enough information to offer guidance.

  • Observations contain bounded request-local identities, visibility/actionability, control classifications, exclusions and same-origin destination pathnames. Dynamic pathnames may themselves identify records.
  • Form values, passwords, free-text page contents, observed selectors/DOM IDs, query strings, fragments and external URLs are not observation fields. Excluded controls do not carry their labels or sensitive contents.
  • Live labels are off by default. Guidance can use approved scanner metadata and indexed route names without them.
  • Sharing requires both app policy navigation_landmarks and the SDK liveLabels opt-in. Only permitted navigation, header, footer and complementary landmarks qualify; main-content labels do not.
  • Labels are bounded to 40 characters and filtered for email addresses, currency symbols and long digit runs. Protected and configured sensitive routes are excluded. These filters are not a guarantee that a workspace or person's name is harmless: review the application before opting in.
  • Permitted labels go to Navieo and Google's current page selector for that request. Navieo does not persist them in guidance context, analytics or logs, or return them in assistant answers. This is not a blanket no-retention promise for all assistant inputs or for the external provider.

Your typed request and approved knowledge are separate from live labels. Navieo stores request context to continue guidance; authorized app members may see prompt text in analytics. Embed only documentation safe for all widget users. See Docs and Analytics.

Supported actions and owner exclusions

Supported navigation anchors must navigate to their href without also performing a business mutation. An anchor that deletes a record, submits a payment or otherwise mutates data on click must be excluded by its owner. Post-click verification cannot undo an action.

Add data-navieo-navigation-intent="exclude" to a control that must not be offered for dynamic guidance. The scanner records this as guidancePolicy: "exclude", and the SDK also checks the live annotation. Re-scan after changing your source declarations. This exclusion does not rewrite separately authored tour steps; review those tours independently.

Forms, submit/reset actions, downloads and external links are not live-first navigation candidates. Already-visible, otherwise eligible ordinary links may be used inside open panels; opening hidden tabs/menus still needs supported scanner evidence. Protected disclosure-bound destinations remain answer-only. Navieo does not infer host sign-in or user roles.

Completion, failures and current limits

An answer explains what to do; a Take me there offer lets you start a guide. Guidance completes after Navieo verifies the destination and required controls—not merely after a highlight or URL change. That verifies guidance progress, not that the user completed a business task.

Use Previous/Next/Done for passive steps and Stop to exit; there is no Skip. Action steps observe real user interaction. When a target disappears, guidance cannot continue, or the provider is unavailable, Navieo explains the interruption without choosing a substitute target. A hand-over may ask you to act manually; acknowledgment alone is not progress.

Some panels load their controls only after opening and cannot yet be guided automatically. You may need to open the panel yourself. When asked to clarify, send a complete request such as “Open settings for this project” rather than “the first one.” See Common workflows for checking your integration.