Product knowledge

Docs

Docs
Gateway workspace
View Markdown

Experience Hub and Assistant

Explore authorised Qlik apps, work with shared analytical pages and use the Assistant through your own Gateway.

On this page

Open your Gateway workspace

The Experience Hub is served by your Gateway at /hub when enabled. It is separate from the external Raptor Portal. Sign in using the Qlik environment offered by your installation; an existing Portal account alone does not grant Hub access.

The overview shows available authored pages and connection information. Apps & sources lists accessible Qlik applications and links to them. The pages, apps and administrative controls you see depend on your verified identity, Raptor assignment, connected Qlik estates and the relevant access policies.

  1. Open the Gateway's /hub address and select the appropriate Qlik sign-in.
  2. Review Apps & sources and confirm the app and connection you intend to use.
  3. Open an available page, apply the required selections and check the resulting data before drawing conclusions.
  4. If an app or page is missing, ask the administrator to check your exact assignment and Qlik access. Do not connect using another person's token.

Draft, validate and publish pages

Users with an authoring role can work in My workspace. A private draft lets you prepare changes without replacing a shared page. Supported page components include analytical displays and references to native Qlik visualisations; required source objects must already exist or be created through a separately authorised Qlik operation.

Publishing makes a page available through shared Hub navigation subject to Hub access and Qlik permissions. It does not publish an arbitrary Qlik app, reload data or approve unrelated database changes. A conflict means the shared version changed; review it before trying again.

  1. Create or open a private draft and select its intended Qlik connection, app and source objects.
  2. Edit the page and preview it. Validate the exact draft revision against Qlik, then review any missing objects, access failures or other validation findings.
  3. Publish only after validation succeeds. Review the intended shared audience and the current published revision before confirming.
  4. Open the published page as an intended reader. Use History to inspect published versions; rollback requires an administrator role and creates a governed change to the shared page.

Hub access and shared knowledge

Administrators use Hub access to manage workspace restrictions backed by Qlik access objects. A workspace without an access object is open to licensed Hub users; creating one restricts access to the corresponding Qlik assignment. Removing it opens the workspace again. Review the audience before changing either setting. The rule is enforced for direct URLs and MCP access as well as navigation.

These Hub workspace access objects are distinct from Gateway licence and role assignments in Seats. They also do not grant access to Qlik apps or data that Qlik itself denies.

The shared knowledge base provides a controlled place for guidance and project files. An agent connected to the Hub domain can discover the repository tools available to its role. Publishing a repository file does not deploy an extension, execute a script, reload an app or submit a writeback.

Use the Assistant

The Hub Assistant can work with the active page, draft or workspace context and the user's permitted tools. Administrators configure LLM providers in /raptor/admin/ under LLM providers and assign provider access in Seats. Review the provider and your organisation's data policy before sending business context to a model.

For Qlik Sense Enterprise on Windows, the Raptor MCP Assistant sheet extension loads its active interface from the Gateway. The supported Qlik visualisation packages are raptor-assistant and raptor-gateway-status. The former raptor token and raptor-admin Qlik extensions are retired; use /raptor/ and /raptor/admin/ instead.

The Qlik sign-in bridge and any native bridge installed by Setup support the approved connection route; they do not grant a user a seat or replace Raptor and Qlik authorisation. Ask the administrator to repair the configured bridge when sign-in fails.

Stored Assistant provider settings are separate from the model and credentials used by an external MCP client or Copilot Studio. Enabling an Assistant provider does not configure those clients automatically.

Previous

Copilot Studio integration

Next

Analytics and app development