When you create a suborganization, certain policies will be inherited from its parent. These inherited policies can only be managed by higher-level organization administrators. If you assign an organization administrator to a suborganization, he or she will not see inherited policies in the Policies page, regardless of whether this policy is turned on or off. The purpose of inherited policies is to allow higher-level organization administrators to appropriately manage organizations while still enabling lower-level organization administrators to support their assigned suborganizations.
For example, when you create a new suborganization under a parent organization:
- If an inherited policy is turned on in the parent organization, you will be given the option of turning on or off this inherited policy when creating a new suborganization.
- If an inherited policy is turned off in the parent organization, you will not be given the option of configuring this policy when creating a new suborganization. This policy must first be turned on in the parent organization.
For existing suborganizations:
- If you turn off an inherited policy in a parent organization, this policy will also be turned off in any existing suborganizations. Only you or another higher-level organization administrator can turn on this policy in the suborganization.
- If you turn on an inherited policy in a parent organization, any existing suborganizations will not be affected. The policy will remain turned off in any of these suborganizations, unless specifically changed within the suborganization.
Use the tables below to identify inherited policies.
IMPORTANT: Policies that are marked as inherited can only be managed by higher-level organization administrators. If you assign an organization administrator to a specific suborganization, he or she will not see inherited policies in the Policies page, regardless of whether these policies are turned on or off.
For more information on managing organizations and policies, please reference the How to Create and Configure Organizations and Policies Knowledge Base article.
*Cannot exceed parent organization.
|Max File Size||
|Max Number of Users||*Cannot exceed parent organization.|
|Allow Creation of Suborganizations|
|Max Number of Organizations|
|Enable Service Plans|
|File Server Enablement|
|Show PSA Tab|
|Show Authentication Tab|
|Let Organization Admins Browse User Files|
|Let Organization Admins Browse Remote Files|
|Let Organization Admins Create Users|
|Allow Users to Create Their Own Backups|
|Allow Users to Share Files|
|Force New Share Links to Require Login|
|Enable Web Editing|
|Enable Web Preview|
|Allow Users to Lock Files||*If this policy is enabled at the master organization level, the policy will appear for each organization.|
|Use Filesystem Permissions to Enforce Locks On|
|Force Password Change After|
|Require Two-Step Authentication|
|Allow users to roll back revisions|
|Allow Users to Erase Revisions|
|Erase Revisions for Files Unchanged In|
|Allow Users to Erase Deleted Files|
|Auto-Erase Deleted Files|
|Erase Deleted Files After|
API Token Settings
|Deactivate API Tokens After|
|Enable Throttle Exception|