Skip to main content

Platform The request is the record.

Tenriva coordinates the requests, approvals and records behind joiner, mover and leaver changes, for organisations using Microsoft Entra ID and Microsoft 365.

Everything on this page is available today.

Tenriva's dashboard in a browser window: requests waiting on approval, the weekly request trend, and Microsoft 365 service health.

Lifecycle requests

Every employee change starts as one structured request.

A joiner, a promotion and a resignation are three different conversations and one shape of work. Tenriva gives each of them a request that records what IT needs, in fields rather than in an email.

Access should be there on day one.

A joiner request gives IT the start date, department, manager and role profile.

A joiner request records

  • Start date
  • Department
  • Manager
  • Role profile
Joiner requests
The New Joiner request in Tenriva: five steps down the left, from the employee’s details to review and confirm, with the identity form open.
A new joiner request: five steps, starting with who the person is.

Role profiles

Describe a role once. Every request for it starts from the same baseline.

Without a baseline, every request is assembled from memory and the answer drifts between one starter and the next. A role profile makes the expected shape of a role explicit, so a request begins from it rather than from whoever happens to be on shift.

Licences
What the role should be assigned.
Groups
The security and distribution groups it belongs to.
Teams
The Teams the role works in.
Policies
The policies that should apply to it.

A request always shows what the profile would apply, and the manager and IT approve it before anything changes.

The five parts of a new joiner request in Tenriva: employee, position, role profile, devices, and review and confirm.

Approvals

Nothing moves until the right people have said so.

The route is the same for every request, so a reader of the audit history six months later can see exactly which gates a change passed through.

  1. HR or the manager

    Request raised

    The change is recorded with the dates, the role and the people involved.

  2. The manager

    Manager approval

    The employee’s manager confirms the change is right before IT sees it.

  3. IT

    IT review

    IT checks what the request would do and what the role profile would apply.

  4. IT, optionally

    Second sign-off

    A second IT approval, for teams that want one on higher-risk changes.

    Optional. Teams that need a second pair of eyes turn it on.

  5. The work queue

    Ready to carry out

    The request reaches IT’s queue with every decision attached to it.

Work queue

One queue for every lifecycle request.

Requests sit in lanes by stage, so IT can see what is waiting on a manager, what is theirs to action and what has slipped past its service level, without asking anyone.

  • Which stage every request is at
  • What is over its service level
  • Which requests have no owner set
Tenriva’s work queue: requests set out in lanes by stage: one waiting on a manager and two in IT review, two of them over their service level and none with an owner set.
Every request by stage, and what is over its service level.

Records and visibility

The decisions are kept, not reconstructed.

The same request that carried the change carries its history, and what is in front of you is what exports.

Tenriva’s audit log, each entry giving the time it happened and the person or system that acted.

  • Audit history

    Keep a record of requests, approvals and actions, and export the entries you are viewing as CSV or PDF.

  • Licence insights

    See licensed accounts that have not been used in the last 30, 60 or 90 days.

  • Device inventory

    View devices managed in Microsoft Intune.

  • Analytics

    Review sign-in activity, provisioning runs, application adoption and Microsoft 365 seat allocation across your organisation, over a chosen period.

Microsoft 365

A governance layer, not a replacement identity provider.

Tenriva is designed to work with Microsoft Entra ID and Microsoft 365 through Microsoft Graph. People sign in with their existing Microsoft work account.

Microsoft Entra ID

Your existing identity. Tenriva does not replace it.

Tenriva

Requests, approvals and the record of every decision.

  • Users

    Accounts for joiners and movers

  • Licences

    What the role is assigned

  • Groups

    Security and distribution

  • Teams

    Where the role works

  • Sign-in with Microsoft Entra ID

    People in your organisation sign in to Tenriva with their Microsoft work account.

  • Microsoft 365 changes for joiners and movers

    Create accounts and apply licences, groups and Teams from the role profile when IT runs an approved request.

  • Microsoft 365 leaver actions

    Block sign-in, revoke sessions and remove licences and group access when IT runs an approved leaver request.

  • Retry and roll back

    Retry steps that fail while a request is carried out, and skip steps or roll back changes for joiners and movers.

  • Microsoft 365 service health

    See the status of Microsoft 365 services from inside Tenriva.

Ask us for the Microsoft Graph permissions Tenriva requests, and we will go through them with you.

How Tenriva approaches governance

Capabilities

What Tenriva does, family by family.

Tenriva sits between the change and the systems it touches. Choose a family to see what sits under it.

Tenriva

One place where a change is requested, approved and recorded.

Select a capability family

Requests

Every employee change enters as a structured request rather than an email, raised by hand or from a change recorded in the HR system.

HR system connections
Create joiner, mover and leaver requests from changes recorded in BambooHR, HiBob or Workday.
Joiner requests
Create a structured request for a new starter, with their start date, department, manager and role profile.
Mover requests
Record a change of role, department or manager, with the date it takes effect.
Leaver requests
Record a departure with the last working day, the reason and how the person’s mailbox and devices should be handled.
Role profiles
Describe the licences, groups, Teams and policies a role should have, so requests start from a consistent baseline.
A Tenriva summary strip showing counts of requests by stage.
Requests by stage.

Next step

Show us where the hand-off breaks.

Start the trial and run one joiner, mover or leaver process yourself. Or book a walkthrough, bring that process, and we’ll look at who is involved and where it slows down.