People: leading the hybrid team|INEMA.CLUB-PRO

Lesson 7 · 18 min

HR for people and agents

When someone joins Horizonte, they get a file, a badge, system access and a person responsible for them. When they leave, access is cut the same day. Hora joined with none of that: in the inventory, the owner is IT. And the automatic summary was suspended, but nobody said who reads the conversations now. In this lesson you handle agents joining and leaving the way you handle people.

Start the lesson
An HR professional and an IT technician check a list on a clipboard next to a laptop; a badge with a lanyard sits on the desk.

In this lesson you will

  1. 1What an agent's onboarding needs to include
  2. 2The agent register, like the list of who works at the company
  3. 3Train the people who supervise, not just the agent
  4. 4Offboard an agent without leaving orphaned work or open access

Goal: organize an agent's onboarding, follow-up and offboarding the way you do for people: owner, access, record and who takes over the work.

01An agent's life cycle

The same stages as a person, with what changes for the agent. Tap each stage.

Click each block in the diagram to see what it does.

Cycle recommended by INEMA, based on the Gestoria method (levels, register, change with rollback). It does not replace the company's information security policy.

02HR for people and agents in practice

Four steps, with Hora and Horizonte's automatic summary.

1. An agent is onboarded too

Deloitte (Tech Trends 2026) treats agents as a workforce that needs onboarding in the data and the operation, graduated autonomy with human-oversight triggers, and notes that the human supervisors also need training.

In practice, onboarding comes down to three questions: who owns the result, what it can access and with which identity, and who supervises it. Without a business owner, the agent stays with IT, which is not accountable for the business result.

At Horizonte (fictional study company)In the lab inventory, the person responsible for Hora is Rafael, from IT. In the retroactive onboarding, the owner becomes Patrícia; Rafael keeps looking after the technical access.

03Templates to copy

Onboarding with the register line, offboarding, and a prompt that looks for gaps. The next tab shows Horizonte's.

Agent onboarding + register line
AGENT ONBOARDING · <name> · <date>

[ ] Job sheet written (mission, deliverable, prohibited) · version <...>
[ ] Business owner: <name> (not IT) · technical lead: <name>
[ ] Supervisor: <name> · trained in <review, package, off switch> on <date>
    · backup: <name>
[ ] Access: <tool · read/write · limit> (only what is needed)
[ ] The agent's own identity (it does not use anyone's password)
[ ] Test cases run before starting: <n> · result <...>
[ ] Trial period: starts at yellow until <date> · sample of <n> per <day/week>
[ ] Off switch: who <names> · tested on <date>
[ ] Team told what changes (meeting on <date>)

AGENT REGISTER LINE
| Agent | Role | Owner | Supervisor | Version | Access | Start date | Next review | Status |
| <name> | <...> | <name> | <name> | <v> | <...> | <date> | <date> | <active / on trial / suspended / offboarded> |
Agent offboarding
AGENT OFFBOARDING · <name> · reason <...> · <date> · decided by <name>

[ ] Access and credentials revoked today: <list> · by <name> · checked by <name>
[ ] Automations and integrations stopped: <list>
[ ] WHO TAKES OVER THE WORK: <person or agent> · starting <date>
    · what changes for that person: <...> · agreed with them on <date>
[ ] Data with the vendor: <what was left there> · deletion request: <done / not possible, why>
[ ] Record and history kept in <where> for <period> by <name>
[ ] Agent register updated: status = offboarded (or suspended)
[ ] Told: team <date> · customers, if something changes for them <...>
[ ] Review on <date>: is the work getting done? did anyone go back to using it in secret?
Prompt · look for gaps
You are reviewing the onboarding or offboarding of an AI agent at a
company. Do not decide anything: point out gaps.

1. Is there a business owner with a name (not just IT)?
2. Is any access bigger than needed, or does it use a person's
   credentials?
3. Has the supervisor been trained, and do they have a backup?
4. In offboarding: who takes over the work, starting when, and was
   that person consulted?
5. What happens to the data left with the vendor?

Document:
"""<paste here>"""
Simulation: illustrative example

Retroactive onboarding · Hora · 11/05 · Horizonte, fictional study company

  • Owner: Patrícia (before: Rafael, in the inventory) · technical lead: Rafael.
  • Supervisor: Juliana, trained in the review checklist, the exception package and the off switch · backup: Sandra.
  • Access: catalog (read) · customer record from the conversation (read) · orders app (write up to R$ 5,000 and 5%) · its own identity.
  • Trial period: sample of 20 conversations per week until 12/04.

Offboarding (suspension) · daily customer service summary · F10

  • Reason: conversations with tax ID and address in a free service outside Brazil, with no contract.
  • Stopped: the 6 p.m. automation, by Rafael, checked by Patrícia.
  • Who takes over: Juliana reads the exception queue and 20 conversations a day, agreed with her; anything that doesn't fit goes up to Patrícia.
  • Data with the vendor: Rafael requests deletion and records the answer.
  • Register: status = suspended until the vendor is replaced.

04Practice

Onboard Hora and turn off the automatic summary; then build the agent register for your area.

1 · Onboard Hora, turn off the summary

30 min

Do the retroactive onboarding of Hora using the template. Then do the offboarding (suspension) of the daily customer service summary, which sends conversations to a free service with no contract. Build Horizonte's agent register from what the inventory and the survey show. Run the prompt on both documents.

Done when: the onboarding has a business owner, a trained supervisor with a backup, and access with limits; the offboarding says who takes over reading the conversations, starting when, and what happens to the data with the vendor; and the register has at least 3 agents or automations, each with an owner and a status.

2 · The register for your area

40 min

List the AI agents and automations in your area, including the ones your team uses on their own. Build the register. Pick one of them and do the full onboarding (or the offboarding, if that applies).

Done when: the register has every agent you know of, each with an owner and a status, there is at least one complete checklist, and every named supervisor has a backup.

Lab materials: IT inventory and customer service summary (F10).

05Quick test

4 questions. The explanation appears after your attempt.

Question 1 of 4

In the inventory, the person responsible for Hora is Rafael, from IT. What does onboarding change?

06Summary

OnboardingBusiness owner, minimum access, own identity, trial period at yellow.
Agent registerThe list of who works here, now including the agents, each with an owner and a status.
Trained supervisorWhoever supervises learns, has time, and has a backup.
OffboardingAccess cut the same day, work has an owner, vendor data handled.

Going further

Horizonte Lab: IT inventory (fictional study company)G4 · Resources: shadow AI and minimum accessG3 · Agents: the digital role
Previous lessonNext lesson