Service Automation

I would like the ability to modify the text and layout of the confirmation screen, and/or disable the confirmation screen entirely for a self‑service product.

Currently, in HelloID Service Automation, we have the option “Requesting User Should Approve” in an approval workflow. When enabled, the requester must approve their own request, even if they submitted it themselves. In most real-life scenarios, we disable this option to avoid an unnecessary extra approval step when the approver is also the requester. Current Behavior When “Requesting User Should Approve” is disabled: No approval email is sent (this works correctly) However, the approval request still appears inside HelloID: As a notification under the bell icon In the user Inbox This makes it look like an approval is still pending, even though no action is required. Why this is confusing From a workflow perspective, the approval step is skipped. But from a user interface perspective, users still see an approval request, which causes: Confusion for end users Extra questions and support requests Doubt about whether the workflow is configured correctly Reduced trust in notifications If something appears in the Inbox or notification bell, users expect it to require action. Suggested Improvement When “Requesting User Should Approve” is disabled, the approval request should not: Generate an email Appear in the dashboard notifications Appear in the Inbox In short: if no approval is required, no approval item should be visible anywhere in the UI.

I don't want anyone to add all groups to a user. I would like this button to turn off. Or give the person a popup when he selects more lets say 5 at the time.

Hello, we're fairly new customers and making use of a dual list in one of our delegated forms. The ">>" and "<<" buttons that move the entire list over leave the opportunity open for our internal users to do some damage. I would like to request the capability of either disabling these buttons, or the preferred option is the option to remove them entirely for a cleaner look to the form. I see this was requested in 2020 and didn't gain much traction as far as upvotes, but we'd greatly appreciate this capability at our company! I anticipate several uses for these dual lists down the road. Thank you for considering

When we request a product in Service Automation, we have the option to add a comment. However, when returning a product, it is not possible to leave a comment. In our environment, the IT department manages the products, so it would be useful to include a comment explaining why a product is being returned.

Since Windows Powershell 5.1 doens't get any feature updates anymore, and Powershell 7 has some notable performance improvements it would be nice to specify the powershell version with which we want to run datasource and delegated form scripts with. Also the helloid cloud agent only supports powershell 7, so it makes sense to also support this on a locally installed system.

When using Maximum amount, it would be useful if HelloID could store an internal "seat number" from 1 up to the maximum amount. When approved, the first available seat is allocated. And when returned, that seat is marked as available. Seat number could be used by tasks as a variable and optionally made visible to the product owner / requester. This would allow us to more effectively assign software licenses that are purchased in bulk but come with individual keys for each user/computer. This is probably possible today, using the metadata API endpoint or an external system to track allocations but it would be much less complex to implement if HelloID had this one variable in Service Automation.

In Managed Products (but in general in all HelloID GUI) it should be possible to adjust the column size to see the complete text.

We would like to import certificates into Cloud agent powershell session. This directly from HelloID environment. The solution to store certificates in azure blob, storage or key vault require credentials in the powershell script to be executed. This is undesirable.

When you assign a product to a user in Managed Products you can assign active and inactive users. The same should be possible in the Admin Portal when you assign a user via Self Servic=> Administration