not a subexpression
# spicedb
j
not a subexpression
s
Thanks for the quick reply Joey! Two followup questions: 1. Is there any plan to support arrow over an subexpression (e.g. if the expression resolves to a single type)? 2. Is there a different way to model the permission I described?
j
1. unlikely, as it seems to break the Zanzibar model
2.
department->member & company->member_of_can_read_document_role_department
or somesuch
or if it needs to be on the department itself
department->some_combined_permissions
s
To clarify, the user doesn't need to be in the department to have the permission. As long as the department matches the user should have access. That's why I think some sort of department intersection is needed. Sorry I wasn't clear on this.
j
the department matches... what though?
remember: the goal is to reach the user