Product knowledge
Docs
Before you register
Prepare the infrastructure, Qlik access and licences needed for a useful evaluation or production rollout.
On this page
Define the first use case
Choose a specific outcome: analyse an existing app, develop a Qlik solution, assess a migration or automate a defined operational task. Identify the Qlik environment and the users who will take part.
For an evaluation, use a customer or partner-managed machine and approved sample or non-sensitive data. A trial still needs a reachable Gateway, valid access and the appropriate Qlik permissions. Hosted Gateway and a shared public sandbox are no longer available.
Agree ownership and access
Name the Gateway administrator, Qlik administrator and operational owner. An approved partner can help with delivery, but customer access and production responsibilities should be agreed before installation.
- Confirm Qlik Cloud, QSEoW or both, and which apps are in scope.
- Prepare the Gateway hostname, network route, service identity, persistent storage and HTTPS trust.
- Choose an AI client your organization permits, including its model provider and data-handling settings.
- Identify Builder users and consumption-only Insights users. The customer account needs at least one Builder licence; an Insights user does not also need a Builder licence for the same person.
- Arrange customer-approved Qlik identities and permissions. A Raptor licence does not replace a Qlik licence or Qlik access rights.
Evaluate before widening access
Start with a small group. Verify the actual Qlik identity, app visibility and one read-only result before testing authorized changes. Compare results with Qlik, and retain any unresolved setup or access issues.
Before production use, agree backups, monitoring, change windows, support and access reviews. Keep licence tokens, personal access tokens, passwords and certificates out of chat, screenshots and shared documents.
Previous
Gateway architecture
Next