Skip to content

25 founding places

What founding customers get

A clearer path to access.

Manage onboarding, role changes and offboarding across HR, managers and IT—with clear approvals, visible ownership and recorded outcomes.

A Tenriva offboarding plan, listing the identity, device and licence steps for a leaver
A Tenriva analytics card showing the status of every request in the period

We started Tenriva in Manchester to bring that work together: one request, the right approvals and a record of the Microsoft 365 changes.

What Tenriva does.

From the initial request to the recorded outcome, Tenriva connects the people responsible for each employee access change.

  1. Request

    HR records the joiner, role change or leaver request, with the employee details and access requirements for review.

  2. Approve

    The request follows the configured approval process. Managers and IT review the change before execution.

  3. Execute

    Internal IT or the assigned MSP technician controls delivery. Tenriva carries out the approved Microsoft 365 access changes.

  4. Verify

    Review execution outcomes, identify steps that still need attention and keep the results with the request and its approvals.

Microsoft 365 and Microsoft Entra ID are what Tenriva changes today. BambooHR, HiBob and Workday can raise the request.

Why we started Tenriva.

Employee access changes cross HR, management and IT, but the work often remains fragmented across emails, tickets and manual updates. That fragmentation makes it harder to establish ownership, enforce approvals and verify that the right changes have been completed.

We founded Tenriva to bring those responsibilities into one controlled workflow.

Operational experience

Ugochukwu Ibeawuchi

Experience in MSP operations informs how requests move between teams and where hand-offs break down. That operational perspective shapes clear ownership, practical approvals and the information teams need to deliver each change.

Software engineering

Chiemeka Madufor

Software engineering experience informs how those workflows are implemented reliably—with permission checks, explicit execution steps and recorded outcomes. That engineering perspective connects the approved request with what actually runs.

A shared purpose

Together, we are building a platform that connects business decisions with technical execution. HR initiates the change, managers approve it and IT or an assigned MSP technician controls delivery. The request, approval and execution record remain connected throughout.

Starting with Microsoft 365, our focus is to reduce manual coordination while preserving accountability. Organisations should be able to see what was requested, who authorised it, what changed and what still requires attention.

What guides us.

  • Make ownership visible

    Show who requested the work, who approved it and who needs to act next.

  • Keep people in control

    Use software for repeated administrative steps while keeping people responsible for the decisions.

  • Leave a record behind

    Keep the request, its approvals and the outcome together, so the history is ready to review.

  • Be transparent about capabilities

    Make clear what is available today, what is still in development and which assurances have been established.

Next step

Bring us your process.

Book a walkthrough with the team building Tenriva. We will review your current hand-offs and show how the request, approvals and Microsoft 365 work fit together. You can also start a trial to test it yourself.