A single Chef Server can be configured to manage the infrastructure of multiple organizations. For example, if your company has different business units that each have their own application and infrastructure servers, they can all use the same Chef server or set of Chef servers by defining unique organizations for each business unit on those Chef servers. Organizations allow the siloing of your infrastructure code, including the cookbooks, nodes, roles, environments, and so on. Said another way, cookbooks, nodes, roles, and so on, are not shared across organizations. A cookbook with the same name can exist in multiple organizations and have completely different content in each organization. This is the mechanism that allows for multitenancy on a Chef server. Each organization will have its own set of users. It is possible for a user to have access to multiple organizations, but such a user would have to be invited into each organization.