Skip to main content Skip to complementary content

Engine Sessions

Engine sessions are used so the client can display the same content regardless of the platform used to access Qlik Sense.

When you are connecting to a Qlik Sense app you are working with engine sessions. The engine session specify who should see changes in an app, and they are based on combining userId and session key. If you open an app, make changes and close the app, this is done within a single engine session. All users who are in the same engine session are experiencing the same thing.  The server creates a new session object for each new user, and destroys the session object when the session expires. The engine session object contains information that identifies the user, and it stores information about a engine session.

There are four types of engine sessions:

  • Default session

  • Fully globally unique session

  • App session

  • Custom session

Session handling

Shared sessions

If you log in as the same user and open the same app in, for example, a PC and on a tablet you will share the same engine session. Your changes will happen simultaneously and selections will also be visible on both devices.

Separate sessions

If an app is open in two different sessions, and you remove, change, or add an object in one of the sessions, the changes will only be visible in that specific session. The same thing applies for selections. To make the change made in one session visible in the other session, save the change and then reload the other session. The last person to save will make the final changes.

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!