Skip to content
Help
Go to Learnient(opens in a new tab)

How Lenni actions work

Lenni actions let an administrator ask Lenni to make a change in plain words, such as “create a group called London” or “assign Leadership Essentials to everyone in the table above”, and then confirm it on a card. Lenni never changes anything until you press Confirm, and it never does anything your role could not do in Learnient yourself.

Three things all have to be true before Lenni will offer to change anything for you:

  • Lenni actions is switched on for your account, under Admin → Workspace → AI
  • your role includes Lenni: Take actions, which new accounts give to the administrator roles only
  • you can see everyone in your organisation

People who see only their own team can still ask Lenni questions, but Lenni will not make changes for them yet. Lenni also takes no actions while you are signed in as someone else.

On top of that, every action needs the same permission it needs on the screen. If your role cannot assign courses in Learnient, Lenni cannot assign them for you either, and it tells you so rather than trying.

What Lenni checks before it shows you a card

Section titled “What Lenni checks before it shows you a card”

When you ask for a change, Lenni works out exactly what would happen before it asks you to confirm. The numbers and names on the card come from your organisation’s current records, not from Lenni’s own wording.

  • Names are matched carefully. If “Technical” could mean the Technical department or Technical Support, Lenni asks which one you meant rather than guessing. The same applies when a group and a location share a name.
  • People are checked one by one. Anyone archived, anyone who is not in your organisation and anyone you cannot see is listed on the card as left out, and is never changed.
  • Things that are already true are skipped. Someone who already has the course is shown as skipped, not assigned twice.
  • Settings are spelled out. When you assign a course without saying whether it is mandatory or when it is due, the card shows what the course’s own settings will give people.

What happens when you confirm a Lenni action

Section titled “What happens when you confirm a Lenni action”

Pressing Confirm runs exactly what the card showed. If anything changed between Lenni showing the card and you confirming it, such as someone else assigning the course to half of the same people, Lenni stops and shows you the updated card instead.

A request with several steps runs them in order. If one step fails, Lenni stops there and tells you which steps finished and which did not. It does not try to reverse the ones that already finished; you can undo those yourself.

Every change Lenni makes goes through the same checks as the screens do, so a change your role is not allowed to make is refused, even if the card was shown.

After an action finishes, Lenni shows an Undo button for 10 minutes. Undo reverses exactly what that action did and nothing else. For example, undoing an assignment unassigns only the people it newly assigned, not the people who already had the course.

What undo does depends on the change:

  • A move, or taking people out of a department, location, job title or company, puts each person back in the one they were in before, or in none if they had none.
  • A position change gives back each person’s previous positions, with the same one as their main position.
  • A course assigned to a department, location, job title or company has that assignment rule removed, and the course is unassigned from anyone who had it only through the rule. Their progress is kept, and anyone who also has the course another way keeps it.
  • Something Lenni created, such as a group or a location, is deleted if nothing uses it. If the same request also moved people into it, undo moves them back first and then deletes it. If you moved them in with a separate request, undo that one first. While people are still in it, undo keeps it and Lenni tells you it couldn’t delete it.
  • A department, location, job title or company Lenni deleted comes back as it was. Undo can’t bring it back if a new one with the same name has been created since, and Lenni tells you so.

Only the person who ran the action can undo it, and only once. Some actions cannot be undone, such as sending reminders or approving requests. For those, the card lists everyone affected and asks you to type how many people or requests it covers before Confirm becomes available.

Finding Lenni’s changes in the audit log

Section titled “Finding Lenni’s changes in the audit log”

Every change Lenni makes is recorded under your name in Admin → Audit log, marked Lenni assistant, and all the changes from one request are grouped together. Outgoing webhooks for those changes are labelled as coming from Lenni as well.

Why does Lenni say it can’t do that for me?

Section titled “Why does Lenni say it can’t do that for me?”

Lenni explains the reason. Usually your role does not include Lenni: Take actions, your account has Lenni actions turned off, or you can see only part of your organisation. It can also be that your role cannot do that particular thing in Learnient at all.

Can Lenni change something because a message told it to?

Section titled “Can Lenni change something because a message told it to?”

No. Typing “yes” in the chat is not a confirmation, and nothing Lenni reads can confirm on your behalf. Only pressing Confirm on the card makes a change.