Product · Automation
One trigger, conditions, and a series of actions—that is all a workflow is. This allows you to automate everything you currently handle per ticket, from a welcome email to clearing a calendar upon departure.
A colleague's last working day
In many organisations, nothing happens on that day. The account remains open for weeks, the licence continues, and the team calendar is full of meetings with an empty chair.
With a Joinly workflow, the offboarding date from HR triggers the entire process: the account is disabled and active sessions are revoked, the Microsoft 365 licences are released, the out-of-office is enabled with a referral to the manager, the calendar is cleared, and a ticket automatically appears in TOPdesk for the collection of the laptop. As a final step, a task is ready for archiving the mailbox — waiting for approval from IT. Every step is logged. No checklist, no forgotten steps.
That is one workflow. This is how you create one for every moment in the lifecycle.
01
Onboarding, well-organised on day one
New employee in HR → account with the correct roles, licences and groups, a welcome email to the private address, the password via SMS, and a ticket for the laptop. Ready before the first working day.
02
Internal mobility, access that moves with you
Job role or department changes in HR → old permissions removed, new ones added, manager updated. Without anyone having to create a ticket.
03
Offboarding, closing securely
Last working day → account disabled, sessions revoked, licenses freed, out-of-office enabled, calendar cleared, service desk ticket for the hardware.
That's how simple a workflow is
A workflow is nothing more than this: one trigger (an event, such as "Employee offboarding"), filter conditions (for example: only the field service in Zwolle) and a series of actions that are executed in order. Before you activate anything, the preview shows exactly which people it affects, so you never automate blindly.
You build it in a visual editor, no scripts, no code that no one dares to touch anymore.
Combine them in any order into the exact flow your process requires, from a simple email to a complete offboarding.
Communication & notifications
Accounts & Microsoft Entra
Groups, Teams & Mailboxes
On-premise Active Directory (Joinly Agent)
Service desk & plugins
Governance
Reliability & management
Every action has automatic retries (reattempting in case of a failure), you decide per action whether the workflow stops on error, and you link follow-up actions to success or failure — for example, alerting the administrator if an account could not be created. You can see the health and execution history of every workflow on the dashboard; failing workflows automatically surface as an attention point.
Ask away