Employee Onboarding with Manager-Selected Access

Employee Onboarding with Manager-Selected Access

Employee Onboarding with Manager-Selected Access

This automation prepares and tracks employee onboarding by combining employee and manager information, applying the appropriate standard access profile, and asking the manager which business applications are required. It provisions the selected accounts, records each result in the onboarding ticket, and highlights any remaining manual actions.

Onboarding

Provisioning

Identity Management

Ticket Management

Trigger

An onboarding webhook carrying the employee identity and any requested business applications triggers the flow.

Outcome

The flow produces a GLPI onboarding ticket containing employee and access results, then either closes it as onboarded or leaves it pending with manual actions when access remains incomplete.

Trigger

An onboarding webhook carrying the employee identity and any requested business applications triggers the flow.

Outcome

The flow produces a GLPI onboarding ticket containing employee and access results, then either closes it as onboarded or leaves it pending with manual actions when access remains incomplete.

Before

IT support likely had to collect employee details, identify the manager, prepare an onboarding ticket, apply standard access, and request application choices separately. After waiting for the manager, support had to create each application account individually and update the ticket with the results.

How it works

  1. Read and combine the employee, department, manager, and identity details, select the department profile, and open the onboarding ticket.
  2. Apply standard access, ask the manager to choose business applications, and assign department-based roles to the selected applications.
  3. Provision each requested account sequentially, summarize the results in GLPI, and either solve the ticket or leave the remaining actions pending.

Workflow details

  • Employee preparation: An onboarding request is enriched with the employee record, department, job title, start date, legal entity, manager, and identity details. The workflow selects the appropriate standard profile group for the employee’s department and creates an onboarding ticket.
  • Standard access: The selected profile group is applied to grant the employee the standard single sign-on applications associated with the department.
  • Manager decision: The manager receives a Teams message showing the employee’s details and can choose Artis and Crystal together, either application individually, or none. The workflow waits up to 24 hours, using the manager’s answer when available and falling back to the applications in the original request when there is no response.
  • Application provisioning: Each selected application is sent to the account-creation sub-flow one at a time, with the application role selected from the employee’s department and the resulting status captured.
  • Ticket completion: The workflow adds a consolidated access summary to the GLPI ticket. If all selected access is granted, the ticket is solved; otherwise, it remains pending with the incomplete access or unanswered manager decision clearly listed for IT follow-up.

What changed

Employee data, profile selection, manager approval, role assignment, sequential provisioning, and ticket updates now happen in one controlled workflow. The manager makes the application choice through Teams, while IT only needs to follow up when an application fails or the manager does not respond within 24 hours.

Work removed

Collecting and rekeying employee details, preparing the onboarding ticket, applying the department profile, sending the manager application request, converting the response into separate application requests, checking each provisioning result, and manually updating the ticket summary.

Expected outcome

A complete and auditable onboarding record showing granted access and clearly separated pending actions, without requiring IT to coordinate each application request manually.

Related flows

Related flows

Explore more workflows with similar topics or tools.

Automated Employee Offboarding

Automates employee offboarding by identifying recently changed employee records, checking whether offboarding is due today, removing qualifying users from Slack, suspending their Google Workspace and Okta access, and sending a detailed status email. This replaces a multi-system manual checklist with a consistent automated sequence.

Automates employee offboarding by identifying recently changed employee records, checking whether offboarding is due today, removing qualifying users from Slack, suspending their Google Workspace and Okta access, and sending a detailed status email. This replaces a multi-system manual checklist with a consistent automated sequence.

Explore use case

Explore use case

Interactive Identity Incident Remediation

This automation turns Teams security event messages into actionable remediation workflows, allowing authorized users to reset passwords, lock accounts, revoke sessions, investigate session identifiers, or route supported requests to specialized subflows. It updates the original incident message with the selected action, actor, and timestamp so the response remains visible in the incident conversation.

This automation turns Teams security event messages into actionable remediation workflows, allowing authorized users to reset passwords, lock accounts, revoke sessions, investigate session identifiers, or route supported requests to specialized subflows. It updates the original incident message with the selected action, actor, and timestamp so the response remains visible in the incident conversation.

Explore use case

Explore use case

Automated Service Desk Ticket Enrichment

When a user opens a service desk incident, the workflow retrieves the ticket, searches related incidents, and determines whether the caller can likely resolve the issue. It then either sends concise guidance to a team channel or enriches the incident with ticket history, similar-resolution context, and device details.

When a user opens a service desk incident, the workflow retrieves the ticket, searches related incidents, and determines whether the caller can likely resolve the issue. It then either sends concise guidance to a team channel or enriches the incident with ticket history, similar-resolution context, and device details.

Explore use case

Explore use case

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.

© 2026 Mindflow — All rights reserved.

SOC 2 Type II
ISO 27001
GDPR
France 2030
Bpifrance
Île-de-France

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.

© 2026 Mindflow — All rights reserved.

SOC 2 Type II
ISO 27001
GDPR
France 2030
Bpifrance
Île-de-France

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.

© 2026 Mindflow — All rights reserved.

SOC 2 Type II
ISO 27001
GDPR
France 2030
Bpifrance
Île-de-France
To embed a website or widget, add it to the properties panel.