Manage shift workers, seasonal staff, and vendor access without manual work
High staff turnover, maintenance vendors, and a factory floor on on-prem Active Directory. Adcyma automates the account work across both AD and Microsoft Entra ID.
What this looks like day to day
Manufacturing has an access pattern most software ignores: seasonal peaks, shift workers who come and go, and external vendors who need accounts for a maintenance window but keep them for years.
The factory usually runs on on-prem Active Directory while the office side moves to Microsoft Entra ID. Two directories, one small IT team, and a steady stream of account changes that all get done by hand.
- Vendor accounts outlive the contract they were created for
- Seasonal ramp-ups mean weeks of account creation, twice a year
- Factory systems on AD and office on Entra ID are managed separately
- NIS2 asks for control over exactly the accounts that are hardest to track
The short version
How Adcyma solves this
Adcyma ties accounts to employment dates and contracts, and applies the same rules to on-prem Active Directory and Microsoft Entra ID.
Date-driven accounts
Seasonal staff get access for exactly the period they work, and vendors get accounts that expire with the contract.
See lifecycle managementHybrid AD and Entra ID
One rule set for on-prem AD and Entra ID, so the factory floor and the office stop being separate manual jobs.
How hybrid support worksExternal account control
Reviews and per-account visibility show which external accounts still exist and why, with evidence to match.
See governance featuresHow you get there
Connect both directories
Connect Microsoft Entra ID and on-prem Active Directory. Factory and office in the same view.
Tie accounts to dates and contracts
Seasonal staff come from the HR data or are managed directly in the Adcyma portal, and vendors get end dates from the start.
Set rules per site and role
Define what the factory floor and the office each need. The same rules apply in both directories.
Let the seasons run
Intakes and departures happen automatically as dates pass, with a log of everything.
What changes
Common questions
Can vendor accounts expire automatically?
Yes. Set an end date when the account is created and access closes on its own. Extending is a decision, not a default.
Our production systems are on on-prem AD. Is that supported?
Yes. On-prem Active Directory is a first-class part of Adcyma, alongside Microsoft Entra ID. Hybrid is the normal case, not an add-on.
How does this relate to NIS2?
Manufacturing is in scope for NIS2, and account control is part of it. Automated offboarding, expiring external accounts, and access reviews cover the identity requirements.
Does seasonal hiring in bulk work?
Yes. Accounts are created from your HR data, so a seasonal intake of fifty people is the same amount of IT work as one.
More solutions
Public Sector
For the companies and units inside a municipality: access that follows moves, and temporary accounts that close on time.
Schools & Education
Handle the start of term without weeks of account work, on a small IT team.
Tech & SaaS
Get control of access across all the tools your teams picked, with SOC 2 evidence as a byproduct.
See it on your own directory
Start a free 14-day trial and connect your Entra ID tenant. No credit card, no consultants.