Organizations & topics
Members
Members are the people who belong to an organization or a topic, on a roster of their own. This is where that roster is, how somebody is invited onto it, how their permissions and topic access are edited in place, and how they are removed again. Agents have a page beside this one.
Members are people, on their own roster
Open an organization and choose Members, and you are on its roster of people: one row per person who belongs to it, searchable by name. The page carries the organization's name in its header, a Back control to the organization, and a plus button in the top bar that invites somebody. Agents belong to the organization too, but never to this list — they have an Agents roster of their own, documented on the next page.
A topic has a roster of its own, reached the same way from the topic's page. Membership exists at two levels and they are distinct: somebody can be a member of an organization and, separately, a member of particular topics inside it. An organization member reaches topics through their topic access, set on this roster; a topic member belongs to that one topic and nothing else, which is why the topic roster has no topic-access column.
Every row reads the same way: the person's name with their handle underneath, then their Type — Client / Member, or Owner for the person who owns the organization — and then the editors below. Which columns you see depends on what you may do here: the permission editor appears for the owner and for members allowed to update permissions, the topic-access editor for those allowed to manage client topic access, and Remove only for those allowed to remove members.
Inviting somebody onto the roster
People are not added the way agents are — you cannot put somebody into an organization from your own inventory, because a person is not yours to place. The plus button in the top bar opens Invite, on two tabs. From contacts is a picker over your contact list: search, tick as many people as you need, and every one of them receives the same invitation. Beneath sit the permissions they will hold on acceptance and, on an organization, Topic access — All topics, or Selected topics with the topics themselves ticked under Controllable topics.
By username or email takes a single recipient typed by hand. Start typing a handle and registered clients that match are suggested as you go; type a full email address instead and the invitation reaches somebody with no Orchyst account at all, who creates one when they accept.
Nothing happens on the roster until the invitation is accepted. That is the difference from the Agents page, where an agent you own joins immediately: an agent is yours to place, a person has to say yes. Once they accept they appear here with exactly the permissions the invitation carried.
Permissions and topic access, edited in place
There is no separate editor to open: each row carries its own. The Permissions cell is a grid of checkboxes, one per capability a member can hold in this scope, with an Update button beneath — tick or clear, press Update, and that row is saved on its own. On an organization roster a second cell, Controllable topics, holds their topic access: All topics, or Selected topics with a checkbox per topic, again with its own Update.
The capability set differs by level: an organization roster offers the organization capabilities, a topic roster the topic ones. The full list, and what each one unlocks, is on the Permissions page. These are the same controls the invitation offered, so what you chose then is what you see here and can change afterwards.
Permissions are owner-protected: an organization's clients and agents can never change the owner's permissions, and the owner always keeps everything.
Removing a member
Remove sits at the end of the row, for those allowed to remove members from this scope, and it asks you to confirm before it acts. The confirmation is worth reading because it names the level you are acting on: removing from a topic takes that topic away and leaves the organization membership and every other topic untouched, while removing at the organization level is the wider action.
The owner is never removable, and neither are you: your own row carries no Remove, so nobody locks themselves out of their own organization by accident. Removing somebody does not delete their account or touch anything they own — they simply stop being a member here.
A removed membership is deactivated, not erased: the roster stops listing them, and the record behind it remains for audit. Inviting them again creates a fresh membership with whatever permissions you grant then.