Skip to main content Skip to complementary content

Using the Management Console

The Management Console is where you manage your Qlik Cloud tenant. For example, you can add users, manage spaces and apps, manage system security, and configure feature settings.

Only users with an administrator role (tenant admin, analytics admin, or data admin) have access to the Management Console. You must be a tenant administrator to access some areas, such as user management and system security.

Opening the Management Console

To open the Management Console, go to the launcher menu Qlik Sense SaaS launcher menu. , and then select Management Console. You can also add /console to your tenant address: https://<your tenant address>/console.

You start out in Home, which provides you with an overview of the resource consumption in the tenant. You can monitor the usage of various resources such as data capacity, generated reports, or automation runs. Home also lists the tenant's capabilities and features. For more information, see Monitoring resource consumption.

Managing users

Select Users in the Management Console to see a list of all the users in your tenant and manage user permissions. For more information, see Managing users - User-based subscriptions.

You can add new users from Users or with an identity provider. An identity provider (IdP) manages identity information for users and provides authentication services. You configure identity providers under Identity provider. For more information, see Identity providers.

Managing spaces

Select Spaces in the Management Console to see information about the spaces created in the tenant. You can also create new spaces here. For more information, see Managing spaces.

Managing user resources

You can view and manage content created by users from the Management Console, such as apps, scripts, data connections, and more. For more information, see Managing user resources

Managing system security

You can configure system security in the Management Console.

API keys: Generate API keys for authentication of users, developers, or calling programs to an API. For more information, see Managing API keys.

Content Security Policy: Manage content security policies. The Content Security Policy provides an extra layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. For more information, see Managing Content Security Policy.

OAuth: Create and manage OAuth clients. OAuth is a standard security protocol that allows third party applications to access API resources without disclosing the end-user credentials. For more information, see Creating and managing OAuth clients.

Managing Qlik extensions

Your Qlik Cloud environment can be extended using extensions and webhooks.

Extensions: Manage extensions in the tenant and upload new extensions. For more information, see Managing extensions.

Web: Create web integrations to add origins that are allowlisted to access the tenant. The web integration containing the allowlist is connected to an ID used in for example a mashup that is connecting to your tenant. For more information, see Managing web integrations.

Webhooks: Manage and create webhooks. You can also create webhooks from the Application Automation interface. For more information, see Webhooks.

Managing system customization and feature settings

Enable features and customize your Qlik Cloud environment from the Management Console.

Generic links: Create generic links to make on-premises apps available in the cloud. For more information, see Managing generic links.

Settings: Configure tenant alias and email server, toggle features on or off in the tenant, and configure feature settings. For more information, see:

Managing data gateways

Manage Qlik data gateways under Data gateways in the Management Console. Data gateways provide a secure means of accessing or moving firewalled data for use in Qlik Cloud. For more information, see Data gateways.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!