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

Organization Hierarchy & Design 29
Provide Access to Services
If some users need access to different services, enable or disable the service for
those users’ organization. Such services include:
• Message Center and Notifications: If users should be able to manage their
own quarantined spam and viruses, enable their Message Center. Also
enable Notifications, which sends them an email summary of recently
quarantined messages. If not, disable these features for their org.
Customize Spam Filtering
Some users might need different spam filter levels, filtering turned off, or to
manage their own filter settings.
• Spam filtering on/off Most users want their spam filters on. But they might
want to forward spam that gets through the filters to Customer Support for
further analysis. So the forwarded spam can get through, you might place
Customer Support in an org with spam filters turned off.
• Spam filter levels Most users probably want all categories of spam filtered
aggressively. Your Sales team, however, might want lenient filtering of
Commercial Offers, so potential leads aren’t wrongly identified as spam. You
might place them in their own org with the Commercial Offers filter turned off.
• Permission to modify filters You might want to allow some users the ability
to modify the strength of their own spam filters, or turn filtering on and off.
What Settings Are Made Where
Settings that affect users and their service can be made for a user organization, a
Default User, or a specific user—depending on the setting and its intended scope.
• Org-level settings apply general policies or administration for all users in the
org, such as a support address or policy against receiving mp3 files.
• Default User settings apply for new users in an org, and are how you
enforce spam and virus filter settings across an org.
• User-specific settings apply to individual users.
• User-controlled settings A few settings, such as filter levels and sender
lists, can also be customized by users themselves at the Message Center,
depending on the user’s User Access permissions.
Some settings are available in more than one location—for example, you can
define org-level sender lists, which users can augment with their own personal
lists. You can also override some org-level settings for a user, such as User
Access permissions to the Message Center. Once you do this, however, the user
is disconnected from the org-level setting—that is, further changes to the org
won’t affect this user. If you have a lot of users, it’s best to manage these settings
at the org-level. It’s a lot easier to apply a new policy once, across an entire org,
rather than individually to tens or hundreds of users