← All docs

Klyr for Teams: your team admin and the directors.

Klyr for Teams groups the people of one company. Every member keeps their own clone, on their own account: nothing about memory changes. What the team adds is an admin who decides, for each member, which of Klyr's directors their clone works with.

What a team is

• A team has a name, members and admins. Each member is one Klyr account; an account belongs to at most one team.
• The person who creates the team is its first super admin. A super admin has full rights, including making other people super admins or admins.
• An admin manages the members and their directors, and can name or remove other admins. An admin cannot remove a super admin or change their role.
• A team always keeps at least one super admin. The last super admin cannot step down or leave until someone else holds that role, so a team can never lock itself out.

The directors

Your clone works like a chief of staff with four directors it can hand work to: Finance/Admin, Operations, Marketing and Sales. On your own account you have all four.

In a team, which directors a member's clone has is the admin's decision, behind three gates:

1. Directors are off by default for a team. A new team starts with none.
2. Klyr turns directors on for the team when the team asks (write to [email protected]).
3. Once they are on, the admin assigns them per member, admin or not, or not at all. Most companies give their members no director at all; that is the admin's call.

An admin can already assign directors before Klyr turns them on for the team: the lists are kept, and they apply the moment the gate opens.

What an admin can do

• See every member of the team, with their directors and whether they are an admin.
• Add a member by their email address. The address must already have a Klyr sign-in; the team never creates accounts.
• Remove a member. Their clone goes back to the solo set of directors.
• Set a member's directors: a list of the four, none, or "every director Klyr ships".
• Name admins, and (as a super admin) name other super admins or revoke them.

Every one of these decisions is recorded on Klyr's side, with who decided what for whom, so a change is always traceable.

What a member sees

The admin's decision is recorded on Klyr's side today; a coming update of the Klyr helper makes your clone follow it. From then on, a director the admin did not give you is not on your machine; one they gave you works exactly as on a solo account. Your clone asks Klyr for the current decision regularly, so a change reaches you without any action on your part, and it tells you plainly when a director is not available to you and why.

What stays yours

• Your memory. A team admin never sees your conversations, your notes or what your clone learned about you. The team record holds names and decisions, nothing from any member's memory.
• The agents you hire yourself. Only Klyr's four directors are governed by the team. An agent you created is yours and the admin never touches it.
• Your own version of a director. If you customised a director and the admin later switches it off, your version is kept. When it comes back, it comes back as you left it.

Good to know

• Klyr creates the team and names its first super admin when a company asks; write to [email protected] with the address of the person who will administer it.
• An admin does not need a clone of their own: an assistant who signs in with Klyr but has no subscription can administer the team.
• A team's admin tools reach the admin's clone in a coming update; until then, tell us what you decided and we apply it the same day.