Skip to main content

Understanding File Settings and Permission Inheritance

Learn how Sydnee’s "restrictive waterfall" permission system keeps your files secure and your firm-wide policies enforced.

Connor Bearse avatar
Written by Connor Bearse
Updated over a week ago

Sydnee uses a hierarchical permission system to manage features like Comments, Versioning, and Client Access. To ensure security and consistency, settings "flow down" from the top level to individual files.

The Permission Waterfall (Inheritance)

Settings in Sydnee follow this specific order:

  1. Tenant (Firm-wide defaults set by admins)

  2. Account (Settings applied to a specific client relationship)

  3. Files (The individual document level)

By default, any file will look "up the chain" to see what its parent has decided. This is called Inheritance.

The "Restrictive Only" Rule

This is the most important concept in Sydnee permissions: A child can only turn a feature OFF; it can never turn a feature ON if the parent has already disabled it.

Example: If commenting is disabled for an entire Account, you cannot re-enable it for a single File within that account. This ensures that firm polices (like "No commenting on this high-risk client's files") cannot be accidentally bypassed.

Managing Settings at Different Levels

File Settings

From the File Info panel, team members can click File Settings to apply an override to that specific file.

  • If you see a Lock Icon, it means the feature has been disabled at a higher level (Account or Folder) and cannot be changed here.

  • If you see "Inherited from [Source Name]", it means the file is currently following the rules of its parent.

Client Access Levels

Client access is set at the Folder level and applies to all files inside it:

  • Full Access: Clients can view, download, upload new files, and manage versions.

  • View Only: Clients can only view and download. They cannot upload or delete.

  • Hidden: The folder and its contents are completely invisible to the client. This is perfect for internal work papers or drafts in progress.

Did this answer your question?