Docs

Use the Enterprise Gateway when your organization wants direct control over how AI clients connect to Qlik.

This is usually the right choice when security, network, procurement, or operations teams require the gateway to be managed by your organization or an approved partner.

The Enterprise Gateway gives your team a single governed access point for Raptor MCP workflows. Users connect through the gateway, and their available actions stay aligned with subscription, assignment, and Qlik access.

It is designed for real delivery work, including longer-running tasks such as app inspection, reload support, migration assessment, governed automation, and InsightOps notifications.

• Administrators approve who can use the gateway and which Qlik environments are in scope.
• Your subscription and user assignment decide whether base delivery, migration, or specialist workflows are available.
• Approved AI clients connect through the gateway with controlled access.
• InsightOps schedules, channels, LLM provider settings, and delivery evidence are managed inside the customer-hosted gateway environment.
• Writeback and workflow targets can be governed through the gateway so operational updates, approvals, and planning changes are controlled and audited.
• Optional administration and monitoring tools help teams manage access, health, and usage.
• Reporting should focus on operational health, access outcomes, and usage governance. Sensitive credentials and private key material should stay out of reporting exports.
• Partner-managed deployments should define hosting, monitoring, support, data handling, and handover responsibilities before production use.
• Client retry, reconnect, and timeout behavior can still vary by AI client.

Run the gateway behind approved network, TLS, firewall, identity, logging, and incident response controls. Production exposure should follow your security architecture rather than a generic public endpoint pattern.

Keep Qlik Cloud, Qlik Sense Client-Managed, QlikView, migration, and analytics secrets in the approved gateway environment. Do not move those secrets into the hosted Raptor web portal.

Licensed customers receive the gateway package needed for the approved deployment model. Supporting packs may also be available depending on the subscription and project scope.

• Gateway package for customer-hosted or partner-managed deployment.
• Configuration examples for controlled environments.
• Administrative and monitoring tools where licensed.
• Supporting materials for partner-managed deployment and handover.
• Qlik SSE Tools remain a separate supporting download for eligible Client-Managed analytics use cases.

Licensed Enterprise Gateway deployments can support governed writeback and workflow actions from Qlik. This lets approved users capture updates and decisions from the analytics experience while keeping data access, permissions, reload behavior, and audit evidence under gateway control.

Typical use cases include approval notes, editable business records, scenario planning, budget planning, customer profile updates, operational planning grids, escalation tracking, and workflow notifications.

• Admins define which writeback stores, actions, workflows, and database schemas are in scope.
• Users act from Qlik through approved extensions rather than direct database access.
• Agents can help build and manage writeback-enabled experiences when the writeback module is licensed.
• Audit trails should be reviewed as part of normal operational governance.

If your team uses Qlik Cloud and does not need to operate the gateway directly, hosted gateway access may be a better fit. It gives admins dashboard visibility into connection details, setup progress, health checks, user access, and token controls.

Use the customer-hosted Enterprise Gateway path when your security review requires direct control over network placement, hosting, or operations.

• Hosted gateway setup requires an active subscription and available gateway capacity.
• Account admins manage user invitations, health checks, suspension, token revocation, and gateway removal from the portal.
• Users generate their own tokens after connecting their Qlik account and passing the required role check.
• Tokens remain customer responsibilities and should be handled through approved secure storage.