Adding a person to a unit: one form

The choice between "add without an invitation" and "invite" is gone. You pick the unit, you say what the person is to it, and the invitation becomes the last question instead of the first.

Before typing a single character, the administrator had to choose between two buttons: "Add a co-owner (without an invitation)" or invite them. That choice was about our internal mechanics, not about their task. Their task fits in one sentence: this person owns unit 302.

One door

There is now a single form. It asks who the person is and which unit is involved. The invitation became its last field, defaulted from whether an email address was typed. Answering no produces exactly what the old "without an invitation" button produced: a record with no portal access, which you can invite later.

The access role is no longer asked here. "Access management" owns that question; this screen only puts someone on the unit's roster.

The unit first, the role after

The old grid listed every unit in the syndicate with a checkbox and a row of roles. At six units that was heavy; at a hundred, a wall to scroll, and on a phone the save button fell below the fold. You now pick the unit, then say what the person is to it. The access question stays on screen instead of hiding further down.

"Primary owner" becomes "unit contact"

The old label suggested a rank between co-owners of the same fraction, which does not exist. Undivided holders may hold unequal shares, but none of them is thereby the "primary" owner over the others: what the syndicate designates is the person it addresses. The label now says what the thing is: the unit contact.

Contact details follow the relationship

A person's contact details are shown only to someone with a defined reason to see them. A real link to the unit or a role on the board opens the record; mere membership in the syndicate does not.

The roster finally renders properly on a phone, with no clipped rows and no horizontal scrolling.