Skip to main content

User Profile and Preferences

Select dropdown link to right of the logged-in User Name.

Select Profile to access User Profile and Preferences. Three tabs are available:

  • Profile
  • Summaries & Statistics
  • Properties for Grid


Three sections are available in Profile: USER PROFILE, USER ACCESS, and USER PREFERENCES. Select the tabs on the left to navigate to that section.

USER PROFILE: Basic demographic information and password storage.

USER PROFILE: Identity information

USER ACCESS: Group associations and roles

USER PREFERENCES: Managing global settings

The USER PREFERENCES section of the User Profile and Preferences page contains a selection pane on which the user can set preferences around how the solution displays and formats data. These settings dictate how data appears when Qlik Data Catalyst opens.


Source, Entity, and Field grids refer to objects in Discover module. External Source, External Entity, and External Field refer to object grids in Source module.

The USER PREFERENCES section offers the following settings:

  • Data Grid: Use the drop-down to select data grid options. A sample of Data Grid options can be seen in the illustration below
  • Visible/Hidden Columns: Global Setting prevents re-setting filters every time users view grids
  • Order of Columns: Sets the order of preference for columns displayed, left to right
  • Sortable Columns: Sets which columns will or will not be sortable by the viewer
  • Default Sort Column [ASC/DESC]: Determines how the columns are sorted, ascending or descending
  • Display Length: Number of objects to display in the grid, per page.
  • Row Selection: Select Tick or Checkbox preference for object selection
  • Enable Personal Webhooks: Enable personal notifications for Jobs Completion by supplying application-specific (Outlook, Slack, Gmail, etc.) webhooks. Webhooks are also called a web callback or HTTP push API. See here for more details on setting up webhooks and enabling notifications.
  • Publish to Qlik Sense Default Starting View: Set default target destination when Publishing to Qlik Sense Advanced from My Cart
  • Qlik Sense Connection Name: In single node environments, users can provide the name of the connection to the Qlik Data CatalystPostgres distribution database in Qlik Sense to facilitate per-user connection security. The value can be found by finding the connection name in Qlik Data Catalyst (Admin>QVD Import>QVD Paths>QS Connection column) or in Qlik Sense Qlik Management Console (<hostname>.qmc/dataconnections) Name Column. (Note this value can also be present and populated first from entity property if the value exists at entity level, if it does not exist at entity level this profile level field is queried, the third place the application will look for the value is core_env property

USER PREFERENCES: Global settings

Summaries & Statistics

This tab shows all available profiling summaries and validation statistics for the Source and Discovery modules. Select up to 15 items from the list on the left to add to the preferred list on the right. Hovering over the value on the left displays a tooltip for that metric. Click Save to preserve your choices.

Summaries & Statistics

Properties for Grid

This tab shows all viewable properties for the Source and Discovery modules. Select from the complete list on the left and click to add to the preferred list on the right. Choose an entire property or expand categories by clicking the caret on the left to select individual properties instead of the entire set (see All Properties for Grid column in the illustration, below: ü symbol for all properties for that grid, symbol for some properties for that grid). Click Save to set a preferred list.


The Undo button reverts back to the last saved settings.

The Reset button applies default settings (no properties are selected).

Preferred Properties (My Preferred List) will display on the listed grids and will also show up in User Preferences: Hidden/Visible Columns. There, the column order can be modified, and selected properties can be set to be sortable with default sort options. Grid properties that can be managed from this tab include: Dataflow Execution Logs, External Entity, External Field, External Source, Internal Entity, Internal Field, Internal Source, and Source Connection. Hover over the property on the left to display a tooltip description.

Properties for Grid

User notifications upon job completion setup

Users are able to configure Notifications upon Load, Prepare, or Publish Job Completion at global level through core_env properties or individual user level on ‘User Preference’ screen. Many applications provide instructions and functionality to easily build webhooks for group or individuals that can be embedded in the job.notification.uri property (for both global and personal settings). Both setting locations utilize same Webhooks convention and tokens (available fields) with which to build a notification.

Available tokens with which to build job completion notifications are:

  • id: Long
  • user: String
  • type: String
  • deliveryId: String
  • status: String
  • recordCount: Long
  • startTime: Date
  • endTime: Date
  • loadTime: Date
  • goodCount: Long
  • badCount: Long
  • uglyCount: Long

These tokens are embedded globally in the "job.notification.content" property "text" field in core_env or individual User Preference screen section "Webhook Content" in the "text" notation.

Example: Example of token usage:

# "text": "Job status: '%JOB_STATUS.startTime%' %JOB_STATUS.endTime%, record count = %JOB_STATUS.recordCount%" \

The core_env property examples below displays a Job Completion notification configured for a Slack Channel.

Global core_env Property Configuration:

### Global Webhook Notifications ###



# If both job.notification.uri and job.notification.content are set then, upon completion of a load, prepare or publish job, a Webhook notification will be HTTP POST'ed to the specified URI containing the specified content. The token '%JOB_STATUS%' may be embedded in the content – it will be replaced with a JSON notification payload. Individual fields of the JSON payload may be included using the following notation: '%JOB_STATUS.deliveryId%'.


Examples are included for Slack and Outlook. Per-user (not global) notifications may be configured in the Podium UI under 'User Preferences'.



#job.notification.content={ "text": "%JOB_STATUS%", "channel": "#integration-test" }




#{ \

#  "@context": "", \

#  "@type": "MessageCard", \

#  "summary": "Podium Job Notification", \

#  "text": "Job status: %JOB_STATUS.type% '%JOB_STATUS.deliveryId%' %JOB_STATUS.status%, record count = %JOB_STATUS.recordCount%" \


User preferences configuration:

Users can add a personal Webhook for receiving notifications through 'User Preferences' by selecting the radio button and configuring the properties similarly to those for Many applications provide specific functionality and instructions for creation of webhooks. For example, if a user would like to receive completion notices for jobs they initiate in their Outlook Mail, they can create a Webhook with the following instructions:

  1. Log into the Outlook mail app and click the gear icon in the upper-right-hand corner of the page, and select Manage Integrations.
  2. Choose Connectors.
  3. Locate the Incoming Webhook connector in the list of available connectors, and choose Add.
  4. Enter a name for the connector and Create.
  5. Copy the Webhook URL and paste it in the Webhook URI field.

User Preferences configured for Outlook Mail Personal Webhook