3. Roles, people and access

A role is a set of instructions, always an agent's, tied to what it knows how to do, the systems it reaches, the channels it serves, and the work that runs on its own. It has a name, a description, and, optionally, the artificial intelligence model it uses.

A name that does not change

Each role is identified by a fixed internal name. Its title can change («Sales» can be renamed «Commercial»), but that internal name cannot, and an archived role keeps it forever without any other role being able to take it.

It looks like a detail, but it is not. If a role's name could be reused, what was given to one role (its permissions, its connections, its history) could pass to another by accident. An identifier that is never recycled prevents that kind of error by design.

Role is not access

Two words that are often confused are worth telling apart.

  • Role is what an agent does: «Sales» answers inquiries and puts together quotes.
  • Access is what a person can do in the business. There are usually three levels: whoever can configure everything (admin), whoever can change what belongs to the roles within their reach (manager), and whoever works with their role and handles their own things (collaborator).

A person having access to a role (seeing it in their copy and asking it for things) does not make them the agent. The role is always filled by an agent, and the person directs it.

Each person, their own copy

In this model, each person has their own copy of the business factory. They always come in through the same place, their own conversation with the coordinating role (the owner of their copy), and from there reach only the roles they were granted access to. A person can have access to one role or to several; a role can be in the copies of several people.

The alternative (a single shared business factory, which every person enters through the same door) looks simpler, and in a first version it is usually what gets built. The problem shows up with use: conversations from different people get mixed in the same roles, what one person asked for is visible to another, and it is hard to separate what each role is doing for whom. With one copy per person, each person has a door of their own that they know, sees only what concerns them, and the coordinating role in their copy takes care of distributing what they ask for among the roles they have access to.

Those who administer the business usually have access to every role; everyone else, to the roles of their area.

When there is only one person

For an independent professional, the model becomes simpler without changing shape:

  • there is a single copy, theirs, and they always come in through their owner conversation;
  • the person has admin access: they are the one who defines the roles, their rules, and what gets approved;
  • the roles are their own areas of work, not departments of a company;
  • approvals, the five message forms, and the record of the work serve just the same: the record tells them what they decided and when, and the owner asks them only what needs them.

Example. The independent accountant comes in through her owner and asks it to prepare the month's payroll and tax calculations. The owner passes it to Payroll and Taxes, which works with the data that Clients gathered during the week. When Deadlines detects that a client has a payment due on Friday, it sends that to the owner, and the owner tells her along with everything else that needs her that day.

Access is the ceiling

The access of each conversation works as a ceiling that nothing goes above. What the person cannot do, an agent in their conversation cannot do either; no instruction, skill, or memory raises it.

Conversations that belong to no person (the ones the next chapter covers) carry the narrowest access of all, that of a collaborator. The reason is simple: what runs without a person in front of it should not be able to do more than the most limited of those who work in the role. What only an admin can do is done by an admin, or by an admin's conversation when the admin asks for it.

Example. The salesperson at Ópticas Horizonte is a collaborator. They ask their role to change the general instruction on discounts. The agent cannot: that change belongs to an admin, and the person's ceiling is the agent's ceiling. What it can do is pass the request on to the proprietor.

Who talks to whom between roles

Roles hand work to one another, but in an order:

  • the coordinating role can write to any leader;
  • a leader can always write to the coordinating role;
  • two leaders can write to each other directly, but only for a question or its answer;
  • a new request for another area always goes through the coordinating role, which decides whose it is.

The distinction between a question and a request is deliberate. A quick question needs no intermediaries; a new request is work that someone has to prioritize, and prioritizing belongs to whoever coordinates.

In short, a role belongs to an agent and each person works in their own copy, with the roles they have access to; access is the ceiling and is never negotiated; and roles pass questions to each other directly, but requests through whoever coordinates. The next chapter looks at how work is divided within each role.