Puavo organisation should resemble a real life organisation. If you have a single private school, the organisation should have only one school. If you have a school district that covers a big city with a hundred schools, you should have a single organisation with those hundred schools. A single Puavo installation can manage multiple organisations, but it can well be used with only a single organisation.
An organisation has a single namespace for users and devices and all servers are registered on organisation level so there should be at least some coordination and shared administration between the schools in an organisation.
Every organisation has three types of users:
Organisation owner accounts are not meant for normal use, but all the others can be used for normal daily activities like desktop use and web services. Organisation owner accounts are handled differently from others to allow remote administration access even when some parts of the system are down.
In normal setup every organisation should have at least two schools - one fake school for administrators and one real school where actual users and devices go to. This is because school admins can modify all users belonging to their schools, the organisation owner users should be put in a separate school (e.g. "Administration") where no normal users exist.
Most of the settings in Puavo are specific to a single school, but some are always shared within the whole organisation.
Default settings on organisation page that apply to all schools if they do not have the setting set (e.g. image name, locale, timezone)
LDAP/JWT authentication for external applications is typically done for the whole organisation. This means that if external services like Moodle and want to authenticate them, the organisation user database should match the Moodle usecase.
WLAN settings - if one creates a network for a school, currently all laptops in the organisation (also in other schools) get the settings, so there can be conflicting SSID with different passwords etc.
External files - license keys, menus, Firefox settings etc. These depend on the desktop image. The same files are transferred to all devices within the organisation.
Printers - Bootservers share printer information for all schools that they serve. Access points can limit the visibility of printers.
Servers - server information