Valuation

Who ELSE is on board. The owner's journey answers whether the system is configured; this one answers the question that decides the fate of the implementation. The number one cause of failure is human, not technical: the system can be 100% ready and the company keeps using the spreadsheet because finance never logged in and the field team does not know there is an app.

On board: used it in the last seven days. Cooling off: seven days or more without using it, and this is when a nudge works. Abandoned: thirty days or more, when a reminder no longer helps and a conversation is worthwhile. Never logged in: the invitation was sent and not used. Cooling off is a state, not an event — the warning goes out BEFORE it turns into abandonment, on purpose.

Profile says what the person CAN do; role says what they came to do in the implementation. They are different things: whoever checks the mirror month may have the same profile as whoever posts invoices. That is why the role is chosen here, in each row's dropdown, and not deduced from the profile — deducing it would put the external accountant in the same bucket as the financial analyst.

When nobody has been invited, the percentage appears as a dash, not as zero. Zero would say the team does not use the system; the truth is that there is no team — and the two situations call for opposite actions.

The invite button opens Users and permissions in a new tab. In the queue of those who need a nudge, the "Tenkai gives a nudge" button notifies the person through the platform itself — internal notification and e-mail, with the number of idle days in the message, because "so-and-so stopped" does not move anyone —, and the sending is recorded in the journey log.

It ties which Academy track is the mini-track for that role. Leaving it on "use the official track", the platform searches by the name of the standard curriculum ("Academy: Financeiro", for example). The explicit link exists because searching by name breaks the day someone renames the track — and it would break silently, with the panel going back to saying that nobody has a track.

The panel does not count who has a login created — that measures HR, not adoption, and it is exactly the number that makes an implementation look successful while nobody uses the system. Here a person is on board when they have OPENED some screen of this company. That is why someone with access for months can show up as never logged in.

The owner goes through the entire track. The field person needs two minutes to learn how to log hours on the phone — and asking them to do the full track is a guarantee they will do none of it. It is this proportion that separates adoption from ignored training.

Without them the mirror month does not close, and charging a seat for someone who only checks would be the wrong incentive: the company would stop inviting precisely the person who validates the implementation.

And the one that most disguises itself as success, because the system is configured and the owner's panel is green. When the team has more than one person and only one used it during the week, this warning appears highlighted — it is the most important signal on this screen.

Each role points to a Tenka Academy track (the same LMS as /pages/rh/trilhas.xhtml). The percentage shown here is what the Academy calculated from the items the person accepted; nothing is typed on this screen and nothing is recalculated. Having a second calculation of the same number would mean having two truths about it.

Zero is a statement: it says the person did not study. When the track does not exist, was not created in this account, has no items, or the person has no employee record, there is no way to measure — and the panel says exactly which of the four cases it is, with the path to resolve it. Showing zero in these situations would make you chase people who had nothing to do.

The button creates an internal notification for the person and queues an e-mail with the same message — the e-mail is a complement, not decoration: whoever has cooled off is precisely who is not logging into the system, and an in-app-only warning would be a note slipped under a locked door. Each nudge is recorded in the journey log.

The platform warns the owner on its own when someone cools off, at most once a week per person. If nobody is marked as Owner, there is no recipient and the warning does not go out — the strip at the top of the screen shows whether it is on or off, precisely so that silence is not mistaken for "everything is fine".

The warning to the owner goes out at cooling off, never at abandonment. After thirty days idle, the person does not come back because of a reminder: that has become a re-implementation, and sending "we missed you" at that point is the noise that teaches the owner to ignore the next warning.

The list shows the ACTIVE users linked to this company. If the person is not here, either the user is inactive or the link to this company does not exist — both are resolved in Users and permissions.

Activity is counted by COMPANY. Someone who works in another company of the same account and never opened a screen in this one appears as never having logged in here — and that is correct: the adoption this panel measures is that of this implementation.

Because the Academy has no track written for the external accountant, and inventing four links just to fill the panel would have you send someone to take a course nobody wrote. If you want one, write it in the Academy and tie it here in the dropdown.

The Academy enrolls employees, not users — the enrollment hangs on the HR record. Partners, external accountants and any login without a record have nowhere to be enrolled, and that is why the panel says so instead of showing a percentage.