Location ACL (potential bug and hopefully able to convert to a feature request one day)

[grapemix]

First of all, great work! Thanks.

Current behavior:
I create a location as User A, but the location is not visible from User B's account.

Expected behavior:
I create a location as User A, the location is visible for User A and B.

Ideal behavior (if this ticket turns to feature):
When users actually start using this app, we create lots of locations. It is kind of annoying to see lots of unrelated locations and have to transverse multiple level to select a location.

Ideally, each location have its ACL list, so users can filter most of unrelated location naturally. Users lived in house A should only see locations in house A, not house B. For house A's common areas like kitchen, everyone lived in house A should see and access it (CRUD). For area like bedroom, only its owner can see and access it. Of course, admin have to assign all common areas permission for users.

For nested location:
If users only live in house A, users will see only location under house A, users should not even see location house A. However, if users only live in house A and B, users will have to select either house A or B first before navigating to its children location. It is like the chroot concept in bash.

So I think we need a M2M table with additional permission field.

env:
homebox:0.21
k8s + pgsql

[tonyaellie]

I believe this would resolve some of your issues
#760

[tankerkiller125]

I create a location as User A, but the location is not visible from User B's account.

This is most likely not a bug, but a UI/UX failure in the sense that every user that simply registers is getting their own tenant/group (as designed). If you want to share a tenant with someone you must send them the invite link from the profile screen.

As it stands right this second users can only be part of one tenant, so if a user needed to be multiple tenants on a single Homebox install they would need to use plus addressing emails ([email protected], [email protected], etc.) we plan to eventually fix this, but it's later down the road as it stands currently.