· updated 6 September 2026release

The case of the invisible Officers

If your org uses ranks, they now appear on every member list and on your own profile. Giving someone a rank also no longer hides the controls for managing them.

There is a particular class of bug that never crashes, never logs an error, and never does anything so vulgar as fail. It simply arranges for a piece of information to be absent, and then waits, quietly, for years. Ours involved Officers.

If your org used ranks, the only screen that reliably admitted this was Org Settings. Everywhere else, a member holding the rank of Officer appeared as a member holding no rank whatsoever, which is rather like a promotion that comes with a certificate you are not permitted to look at. On mobile it is worse still, at least until the next app update: the line under the name simply isn't there, so the entire apparatus of rank is communicated by an absence of text, which is a bold choice for a user interface.

One note on timing before the details. All of this is live on the web now. The same fixes reach iOS and Android in the next app update, so if you are reading this on a phone and your rank is still keeping its own counsel, that is why.

What changed

Every member list now shows standing. The org page, the members sheet, and the roster inside Org Settings all display where somebody actually sits: owner first, then their rank, then the old admin flag, then a custom title if you set one. The same order on all three platforms, which took some arranging.

Your own profile shows your rank. Previously it showed a custom title or, failing that, nothing at all, so most members were greeted by a tasteful blank space where their position in the organisation should have been.

The second bug, which was worse

Assigning somebody a rank quietly removed every control next to their name. Edit title, transfer, remove, ban: all gone. The label and the buttons had been sharing one slot, and the code, presented with a choice between telling you who somebody was and letting you do anything about it, confidently picked the first. So the more carefully you organised your org, the less you could administer it. They now sit side by side, as they should have from the start.

Who you can act on

The controls you are offered now depend on where you sit yourself. You will not see Remove or Ban on the org owner, or on anybody at your own rank or above. Those actions were never going to succeed anyway, and a button whose sole function is to generate an error message is not a button. It is a practical joke.

If you don't use ranks

Nothing about this touches you. Admins and titles behave exactly as before, and your org will continue in blissful ignorance of the whole affair.