Visual Tour Authoring

Visual authoring creates a draft tour by selecting elements in a running application that has the Navieo SDK mounted. It uses the live DOM; it does not ask an AI model to invent selectors or executable steps.

Start a session

1. Open Tours and select the create-tour action.
2. Enter the HTTP or HTTPS URL where the application is running.
3. Continue to create a signed authoring session.
4. Open or copy the generated builder link.

The link appends a short-lived token in the #navieo-author=... URL fragment. The backend allows one active session per app, and the dashboard shows the remaining time. A session expires after ten minutes. If a previous session is still active, an app administrator can end it before starting another.

The target application must mount a compatible Navieo SDK and use the same Navieo app integration. Treat the authoring link as sensitive while it is active; do not commit, log, or share it publicly.

Build the tour

The floating Navieo Builder toolbar separates two modes:

• Select intercepts a click and records the selected element as a step.
• Navigate lets the application handle clicks normally so you can open controls or move to another route.

Selected elements receive numbered markers. The SDK derives a selector, confidence, initial action, route, and starter tooltip copy from the live element. Review every generated field; the author remains responsible for the saved route, selector, action, title, and description.

You can edit a step, replace its element, delete it, reorder it, or undo recent changes. When a concrete route matches a scanned dynamic pattern, the builder can keep the pattern or pin the concrete route. Cross-route steps receive explicit navigation intent when the tour is saved.

Preview and save

Preview starts only when the current page matches the first step's route. It runs the current step sequence through the tour renderer so you can verify targeting and copy before saving.

Enter a tour name and select Save Tour. The backend validates the active session and stores the tour as a draft; return to the Tours page to review its trigger and activate it. Ending a dashboard session without a successful builder save does not create a tour.

Keyboard shortcuts

Shortcuts that would interfere with typing are suppressed while a form control or editable element has focus.

Safety boundaries

• Only app administrators can create or terminate authoring sessions.
• Tokens are signed, app-scoped, time-limited, and consumed through the active-session contract.
• Normal runtime users never receive authoring controls.
• Visual authoring creates authored-tour steps only. It does not grant question-driven navigation authority.
• Test the saved draft on every required route before activation, especially after host UI changes.