Skip to main content
New Participant
April 15, 2024
5. Not Enough Info to Make Decision

Request "On behalf of"

  • April 15, 2024
  • 2 replies
  • 57 views

We can introduce a new process that allows supervisors to raise access requests on behalf of their team members. This will enable employees to gain timely access to the resources they need to perform their job duties, while ensuring that all access is properly authorized and tracked.

 Under this process, supervisors will be able to submit access requests through the BOT, providing necessary details such as the employee Name, email ID, and the specific access required. The request will then be reviewed and approved by the appropriate IT personnel/enabled for auto approval to ensure access is in accordance with organization's security policies.

 This new process aims to reduce the administrative burden on employees and IT staff, while also improving the overall efficiency and security of our access management practices. By allowing supervisors to raise access requests on behalf of their team members, we can ensure that all employees have the necessary access to perform their job duties, while maintaining a robust and auditable record of all access requests and approvals.

This feature can be extended to IT Support teams to make software changes in the system by providing details such as the employee Name, email ID, Hostname, Software, and action needed.

 

 

    2 replies

    dluckadoo
    Employee
    April 19, 2024

    @jambu.j I think there may be a way to achieve this with our current functionality. There are two routes that come immediately to mind:

    1. In-chat fillable forms:
      • By building an in-chat fillable form (details here), you could offer your users the ability to request software/resources on behalf of other users directly in-chat. Once submitted, our native approvals integration (here) would be able to pick up the requests and get approval from the necessary approvers. Finally, once the ticket is approved, the software gets provisioned through one of several different methods and the requested end users software/resource is provisioned.
    2. Creator Studio Path’s Use Case:
      • Build a Paths use case asking for the software/resource to be provisioned, the user to provision, etc. File this request to some table in ServiceNow (possible just the sc_request table or similar). The rest is the same as option 1: approvals kick off, provisioning takes place, and end user is notified. There’s room here to configure notifications using something like Flow designer + Moveworks Events workspace.

    Let me know if either of these options sound like they are in line with what you are thinking and I’ll be happy to provide more details or answer any questions you might have!

    Dray

    Dray
    kyril.remillard
    Community Manager
    May 3, 2024
    1. New5. Not Enough Info to Make Decision