Showing results for 
Show  only  | Search instead for 
Did you mean: 
Lansweeper Employee
Lansweeper Employee

Roles & Permissions

Through Lansweeper Sites, you gain control of user access across assets and locations, using roles and permissions. With Lansweeper's permissions system, you can delegate tasks to specific users without giving them full access to all of the organization’s data. Single Sign-On (SSO) enables you to configure an authentication method to reduce the number of user logins needed, while enhancing security.

Roles can be associated to job roles and tasks performed by individual staff members. Each role will have a group of permissions assigned to it. This way, each individual role an individual is assigned to will be given the permissions necessary to do their work.

You can use the built-in roles and assigned permissions or create your own. It is possible to be very granular and assign access to only a specific installation, module, etc. that fits your needs. Managing access with only roles and permissions will allow the user to access all the data. But what if you need to restrict access to a specific installation or asset type? You then want to use Asset Scopes.

Asset Scope possibilities

Lansweeper Classic enables customers to restrict controls for individual users regarding the Asset Inventory as a whole (read, write/edit, delete rights). With Lansweeper Sites Role-Based Access Control (RBAC) capabilities are even more granular in nature, enabling customers to restrict specific views using Asset Scopes.

An Asset Scope creates a subset of options for who can see what data. Some of the possibilities can be found in the examples below.

An example of granularity is restricting a Linux team to seeing only the Linux devices across multiple installations in a Lansweeper Site, without visibility into any other asset type. Simultaneously, the global IT(AM) manager can have visibility across all different asset types that live within the company’s network, with the ability to export asset reports, and create views and dashboards. The ability to make changes to assets could also be restricted.

The current variables that can be manipulated through Asset Scopes are:

  • Asset Type
  • Asset Domain
  • IP Locations
  • A combination of the variables above

Managing groups of users is easy with the Account Groups. This allows you to create a group of users and assign the specific roles, permissions, and asset scopes for quick and broad access controls.

Examples of Asset Scopes

In the first example, users can only see Linux assets from the IP Location “Contoso Building 1.”

Linux permission.png

In the second example, users can see only Windows assets from the Asset Domains “contoso” and “fabrikam.”

Asset scope Windows.png

To learn more about installation options, you can visit these pages:

  1. ☝️How to use scopes and permissions in a Lansweeper Site
  2. ☝️How to add users to a Lansweeper Site
  3. ☝️How to add owners to a Lansweeper Site
  4. ☝️How to revoke a user's access to a Lansweeper Site


Continue your training with Software Normalization ▶️


New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now
Version history
Last update:
‎06-14-2023 09:38 PM
Updated by: