We looking for the same functionality and are confused on how this could be complex to implement.
Lansweeper already has a method built with relational mapping. The 'Used By' mapping allows that user to attach the that asset to a ticket but not see any other assets not related to them. See image...
Expanding on that functionality, we created an additional relationship type named 'Managed By' and link users to assets under this tag. The intent is to correlate non-IT staff with systems that affect their department and documents on our end who to contact. Unlike the 'Contact' field, you're able to assign multiple people, if needed, to an asset. Staff can then create tickets and attach that any assets that we've designated are 'managed by' them.
Being that this method is already built in, ideally you would only need to add an additional tab (for designated users) to see a list of assets they managed. We already have reports built on this criteria (user relation mapping) and are able to pull info out of any table. Of course this all in a report format but the the functionality is there.
Lansweeper is an amazingly built product especially with the full access and documentation of the tables, so that is were we are confused on complexity of creating a read-only view of a particular asset page?
Biased off of what is already built with 'Access Management', ideally users could be allowed to..
- View assigned assets
Add Comments
Add Asset Documents
See open tickets on that asset and past tickets.
Be notified when a new ticket is create for that asset (possibly with a filter based on ticket type)
Uptime
Additional functionality would ideally include
- Fine grain control of editing certain asset fields.
Fine grain control of what info they can view on the asset