User Asset View

@Keats this is a great capability for asset audits and identifying missing or unused assets that can be tracked down and redistributed.

I agree this would be a very useful functionality to offer users/requesters the ability to review what hardware/software assets are registered under their name in the assets module in Freshservice - great for asset audits. 

Hope this will be considered  int next roadmap.  it will be beneficial for both users and agents.

But right now, if they really need to view all asset assigned to them, I suggest to go to the submit ticket page then click the ‘associate asset’, then all asset assigned to them will appear.

This could be very useful. Especially if you think of an additional field where they can confirm that they have the device or not and this confirmation gets written into the asset (separate field or an existing field like assigned on). If they are missing an asset a ticket for research gets created. 

We currently have created a service item that allows users to make this request. We do it on the backend and then send the results via a reply to the service request ticket. I have not looked to see if this could be automated, but it would be nice for the user to view this information inside the support portal at their convenience. +1 vote from me!!!

We will try something like this with the automation tool appian. We plan to get the users assets via API, list them in a view in appian with alle the options I mentioned. This will work for sure but it could be easier tbh. 

Hey @zachary.king do you mind sharing the web request you used to list assets of a given user or requester? I’m trying to figure out how to list all assigned assets of a user in an offboarding ticket but for the life of me can’t figure it out. Any help would be greatly appreciated!

@mmardini13 Have you tried a query like:

api/v2/assets?filter="user_id: USER_ID"

The assets endpoint supports filtering by a ‘requesters’ user_id. This should give a list of all assets assigned to the person. https://api.freshservice.com/#filter_assets

You do however first need know the persons user_id. I usually do that by first querying the requesters endpoint by primary_email like so:

api/v2/requesters?query="primary_email: 'example.user@example.com' "

Consider that ‘agents’ can also be assigned assets and that your API credentials will not be able to query for any information on an agent unless the user attached to those credentials has the correct permissions to do so. (From memory you need to be able to manage agents in order to make queries for them). 

Thank you @mbft!

@mmardini13 This is exactly how I would do it. Give that a shot and I think you should see what you need.

Thank you @zachary.king & @mbft for the solution, that totally worked! I am able to query for the user id using this: 

/api/v2/requesters?query="primary_email: '{{ticket.actual_requester.email}}' "

but how do I use the User ID from that query in here? 

api/v2/assets?filter="user_id: USER_ID"

I’ve tried this with no luck:

https://brilliantearth.freshservice.com/api/v2/assets?filter="user_id:{{W1.id}}"

Thanks in advance for your help!

That query looks correct to me, assuming W1.id corresponds to a valid user_id that exists within your freshservice environment. What response are you getting?

Here is the WF that I’m using: 

The last part adds a private note in the ticket:

and this is the result:

{"description":"Validation failed","errors":[{"field":"filter","message":"Given query is invalid, expected format \"keyword:value OPERATOR keyword:'string' OPERATOR keyword:>'yyyy-mm-dd' OPERATOR keyword:

Thanks in advance for your help!

This would be a great help as mentioned above, for auditing and letting the users know what they have.

2 years ago.. Zzzz Fresh :D

Great idea!

This could potentially be taken further as well and provide an option to show the user other information about assigned access, for example: 

• Applications assigned in SSO platforms
• Membership of email distribution lists / mailboxes
• The same details but for their direct reports - and allow them to manage the access from within the view (tying back to workflows, ticketing to trigger the outputs). 

I have placed my upvote for this much wanted feature.

To add weight to this, this was also suggested at a roundtable held by Freshservice in the Freshworks London office last year. All 10 other participants from a range of large public sector organisations agreed this would be a beneficial feature.