Automatically enabled when you configure ELMO permissions in your agent workflow. ELMO is connected per client, so the agent calls the ELMO of the ticket’s company.
What it does
- Find a user by work email or name, and read their manager, department, position, location, legal entity, start, service start and end dates, role and custom fields
- Create a user and update one, through ELMO’s user events, and read each event’s result
- Activate and deactivate a user
- Find, create and update onboarding users, and convert one to a user
- Read, create and update departments, locations and positions, and read legal entities
- Read and update a user’s personal contact details
- Read employment details (employment type, pay rate, pay cycle, termination details, emergency contacts) and payroll cycles
- Read leave types and leave requests
- Read recruitment candidates
How the agent changes a department, location or position
The agent sends only the fields that change. Before the update, Neo reads the stored record and fills in each field the agent left out, so an update never clears a field by accident.Writes that always ask a technician
Three updates wait for a technician’s approval under every access profile, Full Automation included, whatever the group’s own approval setting:- Updating a user
- Updating an onboarding user
- Updating a user’s personal contact details
Permission groups
Access profiles
Read Only, Helpdesk and IT Admin keep Personal Contact Details, Employment & Payroll, Leave and Recruitment off. Turn one on by hand for an agent that needs it.
