Overview: Access identities and permissions
Storage permissions evaluate the process identity, pathname and operation under the applicable filesystem or sharing rules.
Reading a film, listing its directory and saving a sidecar can require different rights. Ownership, ACLs and numeric IDs supply parts of that decision, while a service has its own running context. The topics here connect those rules to specific operations instead of treating desktop access as a complete server test.
Read-only media access
Read-only media access lets a server consume source files while directing required application and temporary writes to other locations.File ownership and permissions
File access depends on the process identity, rights along the directory path and the requested operation, rather than the file owner's name alone.Access control lists (ACLs)
Access control lists assign rights to named identities, but masks, entry order and inheritance determine how visible grants become effective access.Linux user and group IDs
Linux storage access uses process and file user/group IDs, so matching account names do not guarantee matching permissions across hosts or namespaces.Storage access from background services
A background service opens storage through its own credentials and pathname environment, which can differ from an interactive desktop session.