Sharing a roster
A group is owned by one organization and can be used by others. There are two ways that happens, and they cover different situations.
A resident proposes their own household
Section titled “A resident proposes their own household”This is the common case. Someone already belongs to a building — they live or work there. They create their household, invite people by email or phone, and propose the household to the building.
Before the manager submits the proposal, OpenApp names the receiving site and previews the roster information its authorized administrators may see if they accept the link. The manager must confirm before the proposal is sent. Household members are told when they join that managers may propose the roster to other organizations.
A building can turn this off. When it does, residents are not offered the option at all, and the API refuses it too.
An organization offers a roster
Section titled “An organization offers a roster”The other case is two organizations with no prior relationship. A school owns a class roster and wants a partner institution to use it. There is nobody to ask, so the owner creates an offer: a one-time link that expires, and that the receiving organization redeems. Redeeming creates a proposal the receiving organization still has to accept.
Accepting a roster from another organization is opt-in: without a policy allowing it, redemption is refused. A resident proposing their own household is allowed by default, because that is the normal path.
Accepting is not admitting
Section titled “Accepting is not admitting”When an organization accepts a roster, it gets a link to the group and sees the household name and member display names needed to decide admission. It does not receive member email, phone, date of birth, or globally identifying user IDs. Each member has to be admitted by the receiving organization before they can be reached there.
Admission is per member and per organization. A building never inherits a roster it has not accepted, and an admission in one organization says nothing about another. A member can be admitted at home while denied at a community centre. Manual approval is the default; automatic admission is an explicit setting on that household-to-organization link.
Either side can walk away
Section titled “Either side can walk away”Both the owner of a roster and the organization using it can end the arrangement. A household manager can revoke a site’s link, and a building can revoke its own link. Household managers cannot change a building’s member-admission decisions, and building administrators cannot edit the household roster.