Terramaster Photos

[AGiLiT]

This still leaves no way of viewing photos separate from videos.

[CursaYang]

This still leaves no way of viewing photos separate from videos.

Currently, only separate access to videos is supported. We are internally discussing how to efficiently filter photos so they can be accessed separately. We will update you as soon as there is any progress.

[AGiLiT]

The desktop app does it, which is why I originated my request. Hopefully, you'll find a way...

[CursaYang]

We have forwarded this request to our product team. Thank you for your understanding and support. We will keep you informed as soon as there is any progress.

[Tolian]

[Feature Request] Photos – Granular User and Group Access Permissions

I would like to suggest an important improvement to the TerraMaster Photos application: a comprehensive system for managing access permissions to photos, folders, and albums for individual users and user groups.

This functionality would be extremely useful not only in business environments but also for ordinary families using a single TerraMaster NAS.

1. Why is this necessary?

Imagine a family of four using the same NAS to store and organize their photographs.

Each family member has their own TerraMaster account and personal photo collection. However, they also want to maintain shared family albums.

For example:

• Parents should have access to their own private photographs and shared family albums.
• Children should have access to their own photographs and selected family albums, but not necessarily their parents' private collections.
• Certain albums, such as family vacations or celebrations, should be accessible to everyone.
• Some photographs should be shared with only one specific family member.
• Users should not be able to discover restricted photographs through search results, thumbnails, facial recognition, or other AI-powered features.

These are completely normal requirements even within a single household.

The same principle applies to small businesses and companies, where multiple employees may need to access a shared photo library while maintaining separate permissions for different departments, projects, or confidential materials.

2. Proposed functionality

I suggest implementing the following features directly within the Photos application:

• Private photo libraries: Each user has a personal photo library that other users cannot access without explicit permission.
• Shared albums and folders: Users can share selected albums or folders with specific NAS users or groups.
• Granular access permissions: Support separate permission levels such as View Only, Upload/Add Photos, Edit/Manage, and Full Access.
• Group-based permissions: Allow administrators to create or use existing TOS user groups and assign permissions to entire groups.
• Permission inheritance: Subfolders and albums should optionally inherit access permissions from their parent folders.
• Simple permission management: Users with appropriate privileges should be able to manage sharing and permissions directly through the Photos interface without navigating through multiple TOS administration menus.
• Complete privacy enforcement: Access restrictions must apply not only when opening photographs but also to thumbnails, search results, facial recognition, People, Places, Scenes, AI-generated collections, and other indexing features.
• Clear separation of personal and shared content: The Photos interface should make it easy to distinguish between My Photos, Shared with Me, and Shared/Family/Team Libraries.

3. Important: Permissions must work throughout the entire Photos application

Simply restricting access to folders at the file-system level is not enough if photographs remain discoverable through the Photos application's search, indexing, or AI features.

Users must only be able to see photographs and associated metadata for which they have permission.

For example, if a user does not have access to a particular album, photographs from that album must not appear in their search results, face recognition collections, location-based browsing, or automatically generated categories.

4. Why this would improve TerraMaster Photos

A NAS is naturally a multi-user device. Families and businesses purchase NAS systems specifically to centralize data while retaining control over who can access it.

A modern photo management application should support this concept natively.

With proper user and group permissions, TerraMaster Photos could become a much more practical alternative to cloud photo services, combining centralized storage, collaborative albums, and genuine privacy.

Such functionality would make Photos significantly more useful for families, small businesses, photographers, and teams.

5. Expected result

Ideally, an administrator should be able to configure a shared photo library once, assign appropriate permissions to users and groups, and let everyone use Photos normally within their assigned access rights.

Users should not need complicated workarounds or manual file-system administration for everyday photo sharing.

I believe granular user and group access management should be considered a fundamental feature of TerraMaster Photos, rather than an optional advanced capability.

I hope the TerraMaster development team will consider including this functionality in the future Photos development roadmap.

[TMzethar]

Hi Tolian,
It seems you’d like to build upon the existing permission management features to establish more granular permission levels and extend those permissions to all indexing capabilities, including search, thumbnails, and facial recognition.
We’ll compile these requirements and submit them to the project team for evaluation. We’ll keep you updated here as progress is made.

[Tolian]

Hi Tolian,
It seems you’d like to build upon the existing permission management features to establish more granular permission levels and extend those permissions to all indexing capabilities, including search, thumbnails, and facial recognition.
We’ll compile these requirements and submit them to the project team for evaluation. We’ll keep you updated here as progress is made.

Hello,

Thank you very much for considering my proposal.

I have a large family with different ages and interests. Adults are interested in their own photo collections and albums, teenagers are interested in their own, children are interested in their own, and elderly parents don't need to see everything.

Dividing permissions by user or group for viewing, adding, and sharing photos with friends via links—that's the kind of functionality I'd really like to have.

My family previously used Qnap's app, QPhoto. Although it didn't have AI facial recognition, it allowed us to create albums and assign access rights. Our old Qnap NAS wasn't fast enough, so we upgraded to the more powerful Teramaster. We'll wait and see how the Photos app will perform better.

Thanks again.

[TMzethar]

Photos currently offers personal spaces, shared spaces, and internal and external sharing, and follows the user group and shared folder permissions outlined in the Terms of Service (TOS). To ensure system security and consistency in permissions, we will not establish a separate permission system within Photos to avoid conflicts with access permissions in other sections.

[Tolian]

Photos currently offers personal spaces, shared spaces, and internal and external sharing, and follows the user group and shared folder permissions outlined in the Terms of Service (TOS). To ensure system security and consistency in permissions, we will not establish a separate permission system within Photos to avoid conflicts with access permissions in other sections.

Hello,

I found several other similar discussions on the forum:
viewtopic.php?p=51850
viewtopic.php?t=9673

I would like to clarify how shared folder permissions (ACLs) interact with the album-sharing functionality in Photos on TOS 7.

**Can a user access photos through a shared album in Photos if they are explicitly denied access to the original shared folder at the file system (ACL) level?**

For example:
- Users A and B have access to a shared folder.
- User C does not have permission to access that folder.
- User A creates a photo album using pictures stored in that folder and shares the album with User C.

**Will User C be able to view those photos through the shared album despite not having access to the original folder?**

In this scenario, which permissions take precedence: the original folder's ACL restrictions or the album-sharing permissions in Photos?

Thank you for clarifying!

[EriChan]

Yes, User C will be able to view those photos through the shared album.

Here is how the two permission layers interact in this scenario:

1. Shared Space vs. Folder ACLs: By default, general access to the Shared Space in Photos is governed by the underlying shared folder's file-system (ACL) permissions. Because User C has no ACL permission for that folder, they cannot browse it directly in File Manager or SMB.

2. Internal Sharing Takes Precedence: However, when User A (who does have access to the folder) creates an internal share in Photos and explicitly shares it with User C, the sharing permission within Photos takes precedence for those specific items.

As a result, User C can view the photos shared with them via the internal sharing feature in Photos, while remaining completely restricted from accessing the rest of the original shared folder.

Hope this clarifies how permissions work in TOS 7! Please let us know if you have any other questions.