Summary and recommendation
Lansweeper user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Lansweeper Cloud user management is handled entirely through the site-scoped admin console at app.lansweeper.com → [Site name] → Settings → Users.
There is no native SCIM provisioning, so every app access change - onboarding, role updates, and offboarding - requires a manual action by a site Admin.
Roles are fixed at three built-in levels (Admin, Member, Viewer) and cannot be customized or made more granular.
Quick facts
| Admin console path | app.lansweeper.com → [Site name] → Settings → Users |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | N/A |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full access to all site settings, user management, scanning configuration, integrations, and all asset data within the site. | Admin rights are scoped per site; a user can be Admin on one site and Member on another. | |||
| Member | Can view and interact with asset data, run reports, and use most read/write features within the site. Cannot manage users or change site-level settings. | Cannot invite or remove users, cannot modify site settings or scanning credentials. | |||
| Viewer | Read-only access to asset data and reports within the site. | Cannot create or edit reports, cannot modify any settings, cannot manage users. | Viewer seats may be available at no additional cost on certain plans; verify current pricing with Lansweeper sales. |
Permission model
- Model type: role-based
- Description: Lansweeper Cloud uses a fixed set of built-in roles (Admin, Member, Viewer) assigned per site. Roles are not customizable. Each user's role can differ across multiple sites within the same organization.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Role-level per site; no field-level or object-level permission granularity documented.
How to add users
- Sign in to app.lansweeper.com and navigate to the target site.
- Go to Settings → Users.
- Click 'Invite User'.
- Enter the invitee's email address.
- Select the role to assign (Admin, Member, or Viewer).
- Click 'Send Invite'. The invitee receives an email invitation to join the site.
Required fields: Email address, Role selection
Watch out for:
- Invitees must accept the email invitation before they appear as active users.
- Users must have or create a Lansweeper account (or use SSO) to accept the invite.
- Invitations are site-scoped; a separate invite is required for each site the user needs access to.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Admins can remove a user from a site via Settings → Users by selecting the user and choosing the remove/delete option. This revokes the user's access to that site. Removal is site-scoped; the user's Lansweeper account itself is not deleted.
- Sign in to app.lansweeper.com and navigate to the target site.
- Go to Settings → Users.
- Locate the user to remove.
- Select the option to remove the user from the site.
- Confirm the removal.
| Data impact | Behavior |
|---|---|
| Owned records | Asset data and scan results are retained in the site after a user is removed; data is not deleted with the user. |
| Shared content | Reports and saved views created by the removed user remain in the site. |
| Integrations | Not documented |
| License freed | Removing a user from a site frees the consumed seat for that site, making it available for reassignment. |
Watch out for:
- Removal is per-site; if the user has access to multiple sites, they must be removed from each site individually.
- The last Admin of a site cannot be removed without first assigning another Admin.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named user seat | Access for one invited user at the assigned role level (Admin, Member, or Viewer) within a site. |
- Where to check usage: app.lansweeper.com → [Site name] → Settings → Users (shows current user list and roles per site)
- How to identify unused seats: Review the Users list for users who have not accepted their invitation (pending status) or who have not logged in recently; no built-in last-login report is documented.
- Billing notes: Lansweeper Cloud pricing is primarily asset-based (number of managed assets), not strictly per-user-seat. User seat limits and costs vary by plan tier. Confirm current seat allowances with Lansweeper sales or the official pricing page.
The cost of manual management
Because access is site-scoped, a user who needs access to multiple Lansweeper sites must receive a separate invitation for each one. There is no org-wide or bulk assignment mechanism. For organizations running several sites, this means every app access review multiplies the number of individual actions required - one per user, per site.
Lansweeper's pricing is primarily asset-based rather than per-seat, but seat allowances vary by plan tier; confirm current limits directly with Lansweeper sales.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Lansweeper Cloud is a practical fit for IT and security teams that primarily need asset visibility and are comfortable managing a small, stable user roster manually. The fixed role model (Admin, Member, Viewer) covers most read/write/admin splits without configuration overhead.
Teams with large or frequently changing user populations, or those requiring fine-grained permissions, will find the per-site manual workflow difficult to sustain without an external identity management layer. No SSO prerequisite is required to use the platform, but SSO adoption is recommended to reduce credential sprawl across sites.
Bottom line
Lansweeper Cloud's user management is straightforward for small teams but does not scale gracefully. Every app that needs access must be handled site by site, with no bulk tooling, no custom roles, and no automated provisioning path.
Organizations managing more than a handful of sites or running frequent access reviews should plan for the operational overhead that the current manual model requires.
Automate Lansweeper workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
