Requesting access to spaces | Qlik Cloud Help
Skip to main content Skip to complementary content

Requesting access to spaces

When datasets from a data product are stored in spaces to which you do not have access, you can request access from the space owner or the space manager.

Once the access is granted, you have access to the entire space. Depending on your role, you may have access to resources beyond the dataset from which you have requested the access.

The permission for requesting access must be activated. For more information, see Customizing the access request process

Information noteDatasets in personal spaces are not accessible even if you have requested access.

Requesting access

  1. Open a data product. When datasets are in spaces to which you do not have access, you see a message in the Datasets section.
  2. Click Request access.
  3. In the Request access dialog, provide a reason for your request and click Send request.

    The request has been sent. The space owner and the space manager will receive a notification and you will receive one once they have approved or denied your request.

Tracking your access request status

You can track the status of your access requests from within the data product. When you have pending access requests, the Request access button displays a status indicator showing that your request is awaiting approval. Once the space owner or space manager approves or denies your request, you receive a notification and the status is updated.

Managing the access requests

As a space owner or a space manager, you can approve or deny access to spaces.

  1. Open Qlik Talend Data Integration.
  2. In the top-right corner, open the Notifications menu.
  3. Click the notification message.
  4. When you do not want to approve the access request, click Deny.
  5. To approve the access request, click Approve and select the permissions.
  6. Click Approve to validate your selection.

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 – please let us know!