Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Enabling note creation

You can enable or disable Notes in the tenant as a tenant admin. Notes are enabled by default.

For information on how to create notes, see Capturing and sharing insights using Notes.

The tenant admin can see all the notes in the tenant from Catalog by selecting Notes from the Types filter. However, to view the contents of a note, the tenant admin needs:

  • The proper role in the space where the note is located.

  • Either of the following:

    • Access via the note content being accessible to all space members.

    • Explicit view or edit access via a note share.

Data security

Note authors can add a snapshot to a note from any data that they can access. This includes sensitive data that could be restricted to other users based on section access rules. If the note is in a shared or managed space, all other space members with access to the note can see the snapshots that are in the note. Note authors should use caution when sharing data that other users may not be authorized to see.

Warning noteA user may have access to visibility of all other users within the same tenant - such visibility may include (but may not be limited to): user names, email addresses and the user’s subject, which is a unique string used to identify the user that is provided to Qlik Cloud by the configured Identity Provider.

Enabling or disabling Notes

Notes are enabled by default. Enable or disable Notes in the Administration activity center, on the Settings page, under Feature control.

Configuring user access to Notes

Rather than turning off Notes entirely for the tenant, you can also customize which users can work with Notes. For more information, see:

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!