In the past, you could define installation-based scopes in Lansweeper Sites within specific roles. However, we've since transitioned to asset scopes.
Asset scopes offer improved asset management capabilities compared to installation-based scopes, as they provide more granular control of asset visibility. This transition to asset scopes also offers the flexibility to customize asset management processes based on installations and roles.
While installation-based scopes remain functional, we highly recommend migrating to asset scopes instead to take advantage of their benefits.
Migrate installations to asset scopes
Since installation-based scopes will continue to work despite being deprecated, you'll need to complete a manual migration process to transition them to asset scopes.
The sequence of steps in the migration process is crucial. Installations must first be added to a scope before removing them from a role. Reversing the steps could result in users briefly having access to assets they shouldn't have permissions for.
Roles that have installations attached to them will have a warning sign next to their name.
Add installations to the scope
- Go to Configuration > Account Management > Roles & Permissions.
a. If the role already has an asset scope, select the linked asset scope to go to the Edit scope view.
b. If the role does not have a linked asset scope, hover over the warning sign and select Go to asset scopes.
In the Asset scopes view, select Add new asset scope. - In the Conditions tab, select the Installation field, the Equal to expression, and select an installation that is already assigned to the role.
Tip: You need to add an additional condition for every installation you want to add to the asset scope.
- Link the asset scope to a role if necessary.
- Select Save and exit.
Remove installations from the role
- Go to Configuration > Account Management > Roles & Permissions.
- Select the role that has installations attached to it.
- In the Scopes tab, select Deselect installations.
- Select Save role.