Every account closed the day someone leaves.
Tenure runs onboarding and offboarding across the systems a credit union actually uses, from the core to bill pay, and writes a log you can hand to an examiner.
- 16:02:11Active Directory disable, move OU, clear groupscleared
- 16:02:14Exchange Online convert to shared, forward to managercleared
- 16:02:15Duo delete user, revoke tokenscleared
- 16:02:19Core system disable teller IDcleared
- 16:02:22Loan origination deactivate usercleared
- 16:02:24Bill pay admin remove operatorcleared
- 16:02:27Phone system release extension, reroutecleared
- 16:02:29E-signature close seatcleared
- 16:02:31Emergency alerts remove contactcleared
- 16:02:33Training platform archive learner, vendor API downheld
Built for the systems credit unions run
Mainstream identity products stop at Active Directory and Microsoft 365. Tenure was built inside a credit union, so it reaches the platforms where terminated users are usually found still active.
- Active Directory
- Entra ID / Microsoft 365
- Exchange on-prem and Online
- Duo
- Mitel
- RingCentral
- DocuSign
- Adobe
- Bill pay administration
- Loan origination
- Emergency alerting
- Learning platforms
- ServiceDesk Plus
- Core system (per install)
Product names belong to their owners. New connectors are built per engagement; see Pricing.
Why a five-person IT team needs this
An offboarding touches a dozen or more consoles. Done by hand, it takes an afternoon, and one skipped step leaves a teller ID or a bill-pay operator active for months. That is the finding examiners write up most often in access reviews.
Tenure takes the ticket from your help desk, does every step in order, retries what it can, and flags what it cannot. The run log is the evidence: who was removed, from where, at what time, by which service account.
Onboarding runs the same way in reverse: accounts, groups, mailbox, MFA, extension, and platform seats created from one ticket, matched to the position you hired for.
Runs inside your walls
Tenure is installed on a server you control and runs under service accounts you create. No credentials leave your network and no vendor holds standing access to your systems. That keeps it in the vendor-risk tier your board can approve without a special review. Read the security and deployment model.