While looking at the schematic consider the following items.

• RADIUSdesk uses the same principals as an application like Github for instance.
• In Github I can be the owner of a repository but I can also allow other users on Github to make changes to my repository.
• In RADIUSdesk an administrator can be the owner of zero or more clouds.
• This administrator then has the ability to assign other administrators to manage selected clouds.

• The database is structured in such a way that entities like Realms, Profiles, Permanent Users belongs to a cloud.
• This means that the database table will have a cloud_id column.
• When a request comes in to perform an action the ACL code will consult information available to determine if the owner of the request are allowed to perform the action on the specific cloud.

• Sites and Networks are tags used with MESHdesk and APs under AP Profiles.
• This is used to group items together which in turn are used for navigation in the Overviews and Maps Applets