Grant permissions to specific assets to a user

Security Requirements and Controls

  1. Click on the profile menu icon and select Organization Settings → Users.

  2. Click the name of the user to view or edit from the list.

  3. Click the Permissions tab and select Asset permissions. The list shows all assets to which the user has permissions. Use the filter buttons to narrow the list of assets.

    Screenshot of the LogScale Asset permissions interface showing a filterable list of all assets to which a selected user has access. The screen displays asset names, their types, associated repositories or views, and the specific permissions granted for each asset. Filter buttons at the top allow administrators to narrow the displayed assets by various criteria, while a prominent '+Assign asset' button provides the entry point for granting additional permissions. This interface allows administrators to comprehensively view and manage granular asset-level permissions for individual users.

    Figure 66. Asset permissions list for user


  4. Click +Assign asset.

  5. Select the asset to give the user access to and click Next. Use the filter buttons to limit the list of assets.

    When granting permission to an asset in a repository or view the user does not have permissions to, you are required to acknowledge that by granting permission, the user is automatically given read access.

    Screenshot of the LogScale 'Select asset to assign' dialog showing a filterable list of available assets that can be assigned to a selected user. The interface includes filter buttons at the top to narrow down assets by type or location, a scrollable list of assets organized by repository or view in the main area, and a 'Next' button at the bottom to proceed with the permission assignment workflow. This dialog appears after clicking '+Assign asset' and allows administrators to precisely select which specific asset will receive custom permission settings for the user.

    Figure 67. Select asset to assign


  6. If the asset is in a repository to which the user does not have read access, you see a dialog when setting the additional asset permissions that the user will be granted read permissions automatically to ALL assets in the view.

    If the user already has read access to the view where the asset is located, you will not see this dialog.

    Screenshot of a warning dialog that appears during the asset permission assignment process when the selected asset is in a repository or view to which the user does not currently have read access. The dialog alerts administrators that proceeding will automatically grant the user read access to ALL assets in that view, not just the selected asset. This critical notification requires administrator acknowledgment and understanding of the broader permission implications before the specific asset permissions can be assigned, helping prevent unintended access grants.

    Figure 68. Select asset to assign when user has no read access to view


  7. Select the permission(s) to assign to the user for this asset. Click Next and then Confirm.

    If assigning permissions to an asset in a view for which the user does not have read access, you must check the box that you understand that the user will be granted read permission to the view before you can click Confirm.

To see how a user has access to a certain asset, click on the asset in the list.

Screenshot of the permission details dialog showing how a user has obtained access to a specific asset. The dialog displays the connected repository information at the top, followed by a detailed breakdown of permission sources, including whether permissions were granted directly, inherited through roles, or obtained via group memberships. This interface helps administrators understand the complete permission path and identify all sources contributing to a user's access rights for the selected asset.

Figure 69. How user obtained asset permission


This dialog shows the repository to which this asset is connected. And then shows the source of the permissions to the asset.

Direct asset permission assignments are automatically removed from a user if that user loses all access to the view.