Dashboard integration

SharedData's operational WebUI can run alongside an existing Dashboard application. This is separate from the static public website. Upstreams, routes, identities and credentials belong to each installation and are not supplied by this guide.

Authentication boundary

Choose the supported authentication mode for the versions being integrated. When applications share browser sessions, verify signing configuration, cookie scope, HTTPS, expiry, logout and permission checks in both directions. API tokens remain separate from browser cookies. Grant administration from permissions in the user record.

Routing

A reverse proxy can direct WebUI routes, API routes and legacy Dashboard pages to their respective applications. Preserve each application's callback, asset and WebSocket paths. Use same-origin paths where required by the WebUI content security policy. Avoid forwarding credentials in URLs. Route registration does not launch an application.

Configure SHAREDDATA_WEB_DASHBOARD_UPSTREAM privately for the chosen upstream. Review existing proxy configuration before merging changes; prepare a reversible release and test it against disposable services first.

Navigation and suggestions

SHAREDDATA_WEB_AUTOCOMPLETE_URL selects a same-origin suggestions path. The response may contain symbols, queries and a same-origin queries_url. Suggestions do not grant permission to open a page. Commands still come from the user's permitted catalog.

Question history and provider-backed suggestions are optional. Enabling suggestions sends the typed text to the configured provider; choose a provider and data policy deliberately. Store provider credentials in the environment and refer to their variable name through SHAREDDATA_WEB_SUGGEST_KEY_ENV.

Branding

SHAREDDATA_WEB_BRAND_NAME, SHAREDDATA_WEB_LOGIN_SUBTITLE, SHAREDDATA_WEB_LOGO and SHAREDDATA_WEB_FAVICON customize the operational interface. Image paths refer to files supplied privately by the operator. Do not publish their actual filesystem locations.

Acceptance

Verify sign-in, denied routes, logout, expired sessions, embedded legacy pages and callbacks with real browser tests in an isolated environment. Treat OAuth and cross-application SSO as separate checks. Embedded pages may contain controls that write data; a preview must use disposable fixtures. Coordinate any production lifecycle change through the deployment's tracked worker management and approval process.