Docs

Hosted gateway access is for Qlik Cloud teams that want the Raptor MCP experience without asking their own infrastructure team to run the gateway service.

It gives your account a managed gateway for an approved Qlik Cloud tenant, with the dashboard showing setup progress, connection details, health checks, user access, and token controls.

• Use it when a managed route is acceptable to your security and governance teams.
• Use a customer-hosted Enterprise Gateway when the gateway must run inside your own network or under your own operations team.
• Confirm the hosted gateway subscription and gateway capacity before setup begins.
• Confirm the Qlik Cloud tenant URL and authorized tenant administrator before setup begins.

An account owner or admin creates the hosted gateway from the dashboard, confirms the Qlik Cloud tenant, completes the Qlik-side setup, and checks the gateway health before inviting users.

Admins can also prepare InsightOps settings for the hosted gateway. This includes the approved delivery channels and the LLM providers that may be used when an automation needs an AI-written insight brief.

• Provide the Qlik Cloud tenant URL and an authorized tenant administrator API key during setup.
• Review setup progress and health before sharing access with users.
• Invite only the users who should be allowed to use the gateway.
• Configure Teams, Slack, email, Telegram, or generic webhook channels before users schedule notifications.
• Add LLM provider settings for agent-written summaries where your policy allows generated narrative.
• Suspend access, revoke tokens, recheck health, or remove the gateway when access should stop.

Each invited user connects their own Qlik account and generates their own gateway token. This keeps access personal instead of sharing one team credential.

Tokens are shown once. Store them somewhere secure, and replace them if they are exposed or no longer needed.

Users can create InsightOps schedules for the hosted gateway once an admin has configured at least one channel. These schedules can send a short business notification on a timetable or when a Qlik reload event happens.

• Use only AI clients approved by your organization.
• Do not share gateway tokens between users.
• Choose an approved channel, a notification template, and when the automation should run.
• For reload-based alerts, choose whether the automation should run on success, failure, or either outcome.
• For app-specific reloads, select the app from the Qlik account connection instead of pasting IDs by hand.
• If a client loses its session, reconnect and start a fresh session before retrying work.
• If health, permission, or token issues repeat, contact the account owner or support partner with the gateway name and user context.

InsightOps turns governed Qlik checks into timely business notifications. It is useful when teams want reload outcomes, KPI movement, data quality exceptions, or an AI-assisted insight brief delivered to the people who need to act.

Notifications can be sent to collaboration and operations tools that your team already uses, while the gateway keeps an evidence record of what was checked and where the message was delivered.

• Use schedule-based notifications for daily, weekday, weekly, or custom recurring checks.
• Use Qlik event notifications when a reload or app event should trigger the message.
• Deliver to Microsoft Teams, Slack, email, Telegram, or a generic webhook for tools such as n8n, Zapier, Node-RED, and Power Automate.
• Use agent insight briefs when you want the automation to review selected Qlik apps and summarize the business signal in plain language.
• Delivery evidence keeps source references, template details, delivery outcome, and acknowledgement state without exposing secrets in the dashboard.