Google Message Security for Google Apps Administration Guide - Manual (Page 24)

24 Message Security for Google Apps Administration Guide
As new users, user aliases, and domain aliases are created in your Google Apps
account, they are added to your initial User organization. If you have several
organizations in your hierarchy, you can move your new users to a sub-
organization.
Each user org can be configured to provide its users with specific services, filter
settings, administrators, and other policies. Placing users in an org applies its
settings to those users. Changing a setting applies the change to the entire org.
By grouping users in organizations, it’s easy to manage users based on their
geographical location, role in the company, service level, filtering needs, and so
on.
Sub-Organization
A sub-organization, or sub-org, is simply an org created below another org in the
hierarchy. When it’s created, a sub-org gets a copy of settings from its parent, and
you can then modify these settings to apply only to users in the sub-org. Creating
sub-orgs allows finer levels of control among a larger group of users.
Sub-orgs Jumbo configures its top-level user org with settings common to all
users. It then creates sub-orgs that get a copy of standard Jumbo settings from
the parent, and that are then customized for the sub-org’s users.
• A sub-org receives a copy of org-level settings from its parent, making it easy
to retain common settings throughout a leg of the hierarchy.
• A sub-org can be managed by any administrators you assign to it, and also by
the parent org’s administrators. This is because an administrator has
privileges to manage the org he or she is assigned to, and all of its sub-orgs.
• Once created, a sub-org remains otherwise independent of its parent.
Changes made later to the parent’s settings are not copied to its sub-orgs,
unless you specifically choose for them to be.