Security & trust

Access you can explain, not just configure.

Most tools tell you who has access. Tola tells you why, with an ordered chain of evidence for every permission, produced by the same check the product enforces.

Admin Center · Effective access

Why can Nina Shaw see “Partner API — launch plan”?

  1. 1 The doc is filed in the launch-q1 channel
  2. 2 launch-q1 is not private
  3. 3 Nina Shaw is in the Thryiv organisation Deciding step
Access granted Checked by the same code the API enforces with.
One access rule, not a policy engine

Everything is filed in a channel. Channel access is object access.

Members always, plus anyone in your organisation for a channel that isn't private. One rule you can hold in your head, and no second path to check.

Effective-access inspector

Ask “why can this person see this?” and get the ordered chain of evidence, with the deciding step marked. It calls the same code the API enforces with, so it can't drift, and its what-if simulations change nothing.

Signing links you can account for

A signature request reaches someone with no account, so the emailed link is the whole credential. The Admin Center names every outstanding link, who holds it and when it expires.

Immutable records

Approved editions freeze. Signatures bind to exact versions. Decision outcomes lock with their evidence. History can't be quietly rewritten.

Audit everything

An append-only trail, written by the code that performed each action, filterable by person and readable in the Admin Center.

  • Emma Carter signed edition 3
  • Hannah Quinn exported launch plan · watermarked
  • Daniel Moore locked a decision

If you can't say why, you don't control it.