#Entity Permissions

The Orchad has come up with a model to describe what we refer to as Public and Private data, and the inteface between
them. 

##Global
The concept of Global was introduced to bring together Public and Private data.  A Global entity is the canonical source 
of a particular entity, whether it be a SoundRecording, Participant or other. 
Top level elements of a Global are considered Public.
Some Global entities have both Private and Public elements.  Public elements are those which are entirely composed of 
Public data. Private elements are composed entirely of Private data and are subject to permission checks. 


##Private
At its heart, Private data is data which either originated within The Orchard (such as release metadata), or that data 
related to it (such as the release's streaming numbers). Our modelling has grown with several different synonyms for 
Private. If you encounter entities prefixed with these, they are Private: 
* Catalog
* Label
* Orchard

##Profile
Every user of our systems needs to have a Profile.  Profiles are the gatekeepers of access to entities.  If your 
Profile 'has_access' to a specific entity (e.g. to a Label) then you have access to that Label's Private data. 
Not only do Profiles grant or deny access to entities, they also describe the kind of access granted, such as 
Administrator or Analytics. Although it is possible for a user to have more than one Profile this is very much the 
exception, and is only found for Workstation - aka Label Profiles.  Normally, one user has one Profile per app (i.e. 
an InsightsProfile to access Insights)

##Public
Public data is data which is freely available. There are no restrictions on who can see it. Charts are examples of 
Public data, as are social media stats. At the moment, we get most of our Public data from Chartmetric. Any 
SoundRecordings that are created from Chartmetric data which we can't recognise are Public.  They will still have a 
Global representation however.