Security

Roles and access

The five roles, the one permission check behind every request, who can read a person’s record, and what keeps a lead’s questions apart from shared knowledge.

RolesMember, Team, Org, Admin, Owner
CheckedOn every request
Ranking of peopleNone
On this page

The roles#

  • Member: every active person. A member uses their own assistant and reads the organization’s knowledge.
  • Team: a lead of one team. A lead reads the personal intelligence of that team’s people and can ask their assistant about them.
  • Org: a leader across the organization. A leader can do the same for everyone.
  • Admin: administration. An admin manages settings, keys, sign-in, members, desktops, teams and the audit log.
  • Owner: an admin who can also manage owners and delete the organization.

One check#

  • Every request passes one permission check: who asks, which permission, which target. A page shows only what the server allows.
  • Admin is administration. An admin reaches nobody’s personal insight unless they also hold Team or Org.
  • An admin gives Team and Org to others, never to themself. An owner gives them to anyone.

Who reads what#

  • Nothing in the product ranks, scores or compares people. The assistant reads one person’s record per request.
  • The person and the organization’s owners and admins read a person’s meetings. A lead’s assistant reads a recap or a transcript to answer a question. It never plays a recording.

Private conversations#

When a lead’s assistant reads another person’s records, that conversation is private. Its content never enters shared knowledge, a journal or a recap.

Shared knowledge#

The assistant builds team and organization knowledge from work records only, such as notes, facts and action items. It never uses activity or screen text for them.

Esc
↑ ↓ to moveEnter to open