Skip to content

Roles & participation taxonomy

The word “role” means several different things in Athenty depending on what is being related to what. To keep them straight — and to stop the loan, estate, accounting, and permission engines from cross-wiring — Athenty uses five distinct axes. This page is the single canonical reference for all of them; the surfaces that consume each axis are cross-linked from the table.

AxisWhat it isFixed / editable
InvolvementA participant’s relationship to a matter — Client / Counterparty / Third-party (Assigned staff is the fourth involvement)Fixed
Matter RoleThe role within that involvement — Buyer, Seller, Lender, Borrower, Guarantor, Executor, Estate Trustee… Loan and estate parties both live here.Managed list — org-editable; a role locks on use once your firm uses the loan/estate module that relies on its exact name (see below)
Staff FunctionHow an assigned staff member relates to a matter — Matter Introducing / Matter Responsible / Matter AssignedFixed (accounting permissions)
Authorized-rep roleHow a person ties to an entity (matter-independent) — Director, Officer, Shareholder, Trustee…Fixed system list — orgs can’t edit
Access LevelA staff member’s org permissions — Owner / Admin / Manager / General (+ HR / Compliance / Bookkeeping add-ons). This is not a “role”.Fixed (Access Levels)

Involvement → Matter Role (the participant hierarchy)

Section titled “Involvement → Matter Role (the participant hierarchy)”

Every non-staff participant on a matter is grouped first by Involvement (a fixed top-level set), then carries a Matter Role drawn from the org’s managed list:

Participant
├─ Client ─┐
├─ Counterparty ├─ carry a Matter Role → [ Buyer · Seller · Lender · Borrower · Guarantor · Executor · … ]
├─ Third-party ─┘
└─ Assigned staff → carry a Staff Function → [ Matter Introducing · Matter Responsible · Matter Assigned ]

The Matter Role managed list is edited at Settings ▸ Managed Lists ▸ Participants ▸ Roles and is consumed by the Matter detail ▸ Participants tab.

Every Matter Role is firm-editable — legal practice is jurisdiction-specific, so each org can add, rename, archive, and reorder the roles it needs. There is no role that is locked by name: until your firm actually uses the module that reads a role by name, that role is as editable as any other.

A role locks the moment your firm starts relying on it. When your org opens its first Loan matter, the three roles the loan engine matches — Borrower, Guarantor, Lender — lock. When your org opens its first Estate matter, the estate roles the module relies on lock. From that point a locked role is:

  • Non-renamable — its name is fixed (the engine matches it by name),
  • Non-deletable — it can’t be archived.

The lock is per-org and stored (the row’s is_system flag), set the first time the module runs for your org — not a global name list. An org that never opens a loan or estate matter keeps every one of these roles fully editable. Orgs may always add their own custom roles and edit or delete the roles they added themselves. Locked roles show a System badge in the managed-list UI, with rename/delete affordances disabled (the API rejects the change too, with a MANAGED_LIST_ITEM_LOCKED error).

When the module first runs it adopts any same-named role you already have (case-insensitively — no duplicate row is created) and creates any essential role that’s missing; re-running is a no-op.

Triggering moduleRoles that lockWhy
First Loan matter (Loan management)Borrower, Guarantor, LenderA participant’s loan capacity is derived from their Matter Role name, so renaming or deleting one would prevent that person from being added to a loan.
First Estate matter (Estate interview)Executor, Beneficiary, Witness, Estate Trustee, Administrator, Trustee, Successor Trustee, Attorney for Property, Attorney for Personal Care, Guardian, SettlorThe estate roles the module seeds and the questionnaire engine attaches participants by — renaming/deleting one would break those references.

Roles such as Buyer, Seller, Spouse / Partner, the litigation set (Plaintiff, Defendant, Applicant, Respondent, …), and Other never lock — they’re conveniences/jurisdiction roles you fully control.

The separation is deliberate and load-bearing:

  • Staff Function is not a Matter Role. Putting “Matter Responsible” into the participant role picker would cross-wire staff into role notifications, Critical-Date recipients, and fee attribution. Staff Function is a fixed set under Assigned staff — see Accounting permissions.
  • Access Level is not a Matter Role either. It governs what a staff member can do in the org (Owner / Admin / Manager / General), not how they relate to a single matter — see Access Levels.
  • Authorized-rep role describes a person’s tie to an entity (a company’s Director/Officer/Shareholder), independent of any matter, and is a fixed system list orgs can’t edit.