Is there a way to hide the "requestor" field for service catalogue requests?

Hi helpdesk_survivor , 

While it's not possible to hide the requester in service catalog or incidents, you can disable the "Request on Behalf Of" functionality if users are creating requests for others. This prevents users from submitting requests.

Here's how to disable it:

1. Go to Setup.
2. Navigate to Global Settings.
3. Select Service Portal.
4. Locate the option for "incident on behalf of other users" and disable it. Refer below image.
   
   
   

Hi Chazz, 

Thanks for your response! Unfortunately I'd like to keep that option open as we have office admins and managers submitting service requests on behalf of new hires.. 

Here is an example of one of our forms:

Besides turning off the option to allow users to submit on behalf of others do you know of any workaround to have the generated ticket update approvals for the "Who will this software be assigned to" user?

Let me know,

Thanks!

Hi Chazz, 

Thanks for your response! Unfortunately I'd like to keep that option open as we have office admins and managers submitting service requests on behalf of new hires.. 

Here is an example of one of our forms:

Besides turning off the option to allow users to submit on behalf of others do you know of any workaround to have the generated ticket update approvals for the "Who will this software be assigned to" user?

Let me know,

Thanks!

The only work around I can think of is creating a service catolog form/item that is department specific and then create a user group that is specific to each department (includes managers/approvers from that department). Then for each separate catolog form, make it department specific for the title, something like "HR New Hire Equipment Request" or whatever your ticket is for. Then make the required approver the department group that you created. Then whoever is in that group can approve it. Honestly, that sounds like a lot of work as I don't know how many departments your business has, but that is the only work around I can see. If I am understanding you correctly, the individual submitting the ticket changed the Requester to the person they are submitting it on behalf of? It is strange that it wouldn't default to that person listed as the requester and defaults to the person who actually submitted it.