Granting access permissions
Convert access requests in TOPdesk into accounts in healthcare applications and update the ticket.
Overview
New employees require accounts in healthcare applications, requested via TOPdesk. This automation reads every ticket, checks if the data is complete and the start date is approaching, supplements it with data from ONS, creates the account in Ysis or FarMedRx, and assigns the permissions. The ticket is then updated with the result.
What has changed
- Accounts are created faster
- Accounts are created consistently every time
- Service desk staff have less repetitive work, and everything is auditable
At a glance
In één oogopslag
Overzicht
New employees require accounts in healthcare applications, requested via TOPdesk. This automation reads every ticket, checks if the data is complete and the start date is approaching, supplements it with data from ONS, creates the account in Ysis or FarMedRx, and assigns the permissions. The ticket is then updated with the result.
Wat er verandert
- Accounts are created faster
- Accounts are created consistently every time
- Service desk staff have less repetitive work, and everything is auditable
How it works.
What it does per ticket
- Reads open requests from TOPdesk
- Extracts employee details and checks if they are complete
- Only proceeds if the start date is today, tomorrow, or in the past
- Supplements the request with location and employee ID from ONS
- Creates the account in Ysis or FarMedRx and assigns the permissions
- Updates the ticket with a comment and status
Rules
An account is only created if the data is complete and the start date is today, tomorrow, or in the past; requests made too early are postponed, with a 14-day limit for re-checking. Certain roles or departments are skipped, duplicates are checked first, and incomplete requests receive a comment on the ticket. Because the logic is fixed, the same input always yields the same result, and every run is logged.
Check out other automations.
Frequently asked questions.
No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.
Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.
Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.
Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.
Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.