Places
A place is a part of your organization: a region, a branch, a team, a store. Places are how Canopy knows that a manager in one branch administers that branch and not the one next door.
Overview
Every organization is already shaped: offices inside regions, stores inside districts, teams inside departments. Canopy holds that shape, and authority is granted against it. This is the one idea that makes the difference between an administrator who runs a branch and one who runs a country.
The Workspace calls these places, and calls them locations on some screens. Developers meet the same idea under a third name: a hierarchy node.
What a place is
A place is one point in that shape, with a name you would recognise: Northern Region, Store 114, Cardiology. Places sit inside other places, which is what gives the organization its levels. What the levels are called is decided per environment, so one account might have regions and stores while another has departments and teams.
A place includes everything beneath it
Being assigned to a place gives you that place and everything inside it, all the way down. Nothing above it, and nothing in a place beside it.
Or the whole environment
Some authority is not attached to any place. An environment-wide assignment covers the environment as a whole, including places created after you were granted it. It is the right shape for someone whose responsibility genuinely is the whole environment, and the wrong shape for everyone else, because it cannot be narrowed later without replacing it.
Why it decides what you see
Places are not a filter on a screen. They are the answer Canopy gives when it is asked whether you may do something, so they decide what you can see, who you can invite, whose roles you can change, and which activity you can read. Two administrators holding an identical role in different places have entirely different working days, and neither can reach the other's people.
Next Step
Tell us how we can improve this guide.