Podcast · Roles & permissions · Deep dive

The Industry's Names for the Job

The live code reads one role word in eight different places — and ten role names turn out to be only five actual behaviours, plus a dead invite screen and twelve blank memberships that need cleaning up before real customers start creating their own admins.

Companion to Roles — a simple model before customers arrive, the source brief this episode is generated from. The role audit is what the live code does on September 10, 2026; the five-seat model and the cleanup are a proposal awaiting three of Fede’s decisions.

The Industry’s Names for the Job

Deep dive · two hosts · short episode · 6 min

Read the page →

What it covers

The mechanism first: a role is one word stored on a person's membership in a company, and an audit of the live code on September 10 found that single word read in eight separate places — not just which menu items appear, but which page addresses load, which saves and deletes go through, who can invite whom, which buildings show up, whether Clara treats a caller as staff or as a prospect, which of Clara's own tools a person's conversation can trigger, who gets paged, and who alone is walked through the first-sign-in wizard.

Then the gap between what the product defines and what the code actually does: ten named roles, but only five distinct sets of permissions, because four of them were added on August 19 purely to show a real job title and were pointed, by reference, straight at an existing role's permission table — a title stapled onto a permission level, and the entire reason the list grew.

Then the three screens that each hand-typed their own version of that list, a fourth screen that isn't linked from anywhere and still posts to a dead invite path, and the twenty-one-row production user table read that same day: twelve users with no role stored at all, and not one customer admin anywhere yet.

Then the fix already sitting in how every real customer the team has talked to is actually staffed — one or two people who pay and decide, managers, leasing people, maintenance people, and people who only watch — which maps one-to-one onto the five behaviours the code already has, plus reach (which buildings) as a second, independent axis. And the three decisions that are Fede's alone: how many seats to offer, where a regional manager sits on the invite ladder, and how an owner gets to watch without touching anything.

Before you quote anything from this

The role audit — the eight read sites, the ten-names-five-behaviours finding, the three screens, and the production user counts — describes the live code and the live database as read on September 10, 2026. The five-seat model, the cleanup list, and the three decisions are a proposal awaiting Fede's go; nothing in this design ships to a real customer without it. The only names used are people already named on the source page or already public to the team (Fede, Gera, Sean, Kenya) and customer names already public there (Western Slope, Situs Group, ConAm, JP&Co, Yale). No prospect, tenant, or applicant appears anywhere. The audio is a machine-generated overview of the brief below, and the transcript is machine-made from that recording; proper nouns are fixed by hand before anything is quoted.

Chapters

  1. Open on the assumption, then break itA role looks like it just decides which menu items appear. It is read in eight places — lingering on the three that reach into Clara — plus the two things it deliberately never controls.
  2. Count the names, then count the behavioursTen role names, five actual behaviours: the four title roles honour a real ruling literally, three screens hand-type their own lists, and a dead fourth still posts to an old path.
  3. The production tableTwenty-one users, read September 10: more than half have no role stored, and not one customer admin exists yet.
  4. How six became ten, in three datesMarch, seven roles. May, the company design collapses them to six, already the simple one. August, four titles added because a title problem was solved with roles.
  5. The founder’s ruleFede rejected generic seats like Manager and Leasing: a role should be the job a person holds, in the industry’s own words — plus no accounting role, and start minimal.
  6. What the market calls themAppFolio’s thirteen roles, the institutional vocabulary and its credentials, the smaller-operator names, and why owners get a portal, never a staff role.
  7. What our own customers sayJason, Jay, Kat and Beverly at Western Slope; Dara and Jaise at ConAm; Kenya at JP&Co — and why which buildings has to stay separate from the role name.
  8. Six rolesOrganization Admin, Regional Manager, Property Manager, Leasing Agent, Maintenance Technician and Owner — a small change against today’s code, with Regional Manager the one real one.
  9. One place, no copiesA single role catalog and a guard test that fails the build if any other file writes its own list of roles — built dark tonight, no visible difference.
  10. Close on the decisionsThe three decisions and their recommendations, the three things already ruled, and why deciding this week is the cheapest it will ever be.

One chapter per major turn in the source brief. The list is hand-written — nothing derives it from audio — and the titles are also what goes in the recording tool's focus prompt. Each one already points at a transcript heading (#ch01…#ch10); the links go live the moment the transcript is pasted in, and until then a click is a deliberate no-op.

PropFlow Docs