not as such, no.
the way to think about a permission check is that it's a walk from a resource to a subject. if the path exists, the check succeeds, else it fails.
what that means is that you typically want to walk through an object if it's supposed to be a part of the permission logic. there isn't a way to provide multiple subjects to the permission check.
i'd add a hop from the file group to the app to the user group or something equivalent.
this is also potentially a use case for [caveats](
https://authzed.com/docs/spicedb/concepts/caveats), though i'd recommend using relations to express logic if it's possible, and then only reaching for caveats if you can't