Admins and team shares
Inherited policies in sub-organisations
2 min read
When you create a sub-organisation, it inherits certain policies from its parent organisation. Inherited policies can only be managed by the administrators of the parent organisation. This lets parent administrators manage their organisation and its sub-organisations properly, while sub-organisation administrators can still look after the organisation assigned to them.
For newly created sub-organisations
- If an inherited policy is on in the parent organisation, the new sub-organisation can keep it on or turn it off.
- If an inherited policy is off in the parent organisation, it cannot be changed in the new sub-organisation. To change it, turn it on in the parent organisation first.
For existing sub-organisations
- If you turn an inherited policy off in the parent organisation, it turns off in all existing sub-organisations. Only you, or an organisation higher up, can turn it back on in a sub-organisation.
- If you turn an inherited policy on in the parent organisation, existing sub-organisations are not affected. The policy stays off in each sub-organisation until it is turned on there.
Note · Policies marked as inherited can only be managed by parent organisations. An administrator you assign to a sub-organisation does not see inherited policies under Policies in the settings, whether they are on or off.
The tables below show which policies are inherited. See also organisation structure and multitenancy.
Organisation policies
| Policy | Inherited |
| Storage quota | No |
| Maximum file size | No |
| Excluded extensions | No |
| Maximum number of users | Cannot exceed the number of the parent organisation |
| Allow creating sub-organisations | Yes |
| Maximum number of sub-organisations | Yes |
| Enable service plans | Yes |
| Enable branding | Yes |
| WebDAV support | Yes |
| Backup creation | Yes |
| File server enablement | Yes |
| Show authentication tab | Yes |
User settings
| Policy | Inherited |
| Allow organisation admins to browse remote files | Yes |
| Allow organisation admins to create users | Yes |
| Allow users to create their own backups | Yes |
| Allow users to share files | Yes |
| Require login for new share links | Yes |
| Enable web preview | Yes |
| Enable web editing | Yes |
| Allow users to override collisions | Yes |
| Allow users to resolve several warnings at once | Yes |
| Allow users to lock files | Shown in every organisation when turned on at the master organisation |
| Use file system permissions to enforce locks | No |
| Force password change after | No |
| Require two-step authentication | No |
Revision settings
| Policy | Inherited |
| Allow users to roll back revisions | No |
| Allow users to delete revisions | No |
| Remove revisions automatically | No |
| Remove revisions of files unchanged for (x days) | No |
Deletion settings
| Policy | Inherited |
| Allow users to purge deleted files | No |
| Remove deleted files automatically | No |
| Remove deleted files after (x days) | No |
Backup settings
| Policy | Inherited |
| Remove revisions automatically | No |
| Remove revisions of files unchanged for (x days) | No |
| Remove deleted files automatically | No |
| Remove deleted files after (x days) | No |
API settings
| Policy | Inherited |
| Deactivate API tokens after (x days) | No |
Bandwidth settings
| Policy | Inherited |
| Throttle bandwidth | Yes |
| Enable throttling exceptions | Yes |
Related articles
Still stuck?
Our support team in the Netherlands answers by email and phone.
