Dima
03/13/2023, 8:52 PMDima
03/13/2023, 8:54 PMdepartment1
(i.e. for all teams in this department)
• Article with internal team’s drafts, available for team1
My first idea was to use arrays for such visibility fields and then fullfill them with corresponding values. If visibility chosen as department1
, we will add corresponding teams too. Solution looks like this
Problems with this solution are:
• Some people can be outside teams or departments. For example CEO or other leaders.
• We need to update index every time when new teams are created, otherwise they will get empty results (e.g. newcomer team5 won’t get even publicly available documents)Jason Bosco
03/13/2023, 8:57 PMJason Bosco
03/13/2023, 8:58 PMSome people can be outside teams or departments. For example CEO or other leaders.You could add them to an internal admin “system” team of sorts, that is not exposed to your end users
Jason Bosco
03/13/2023, 8:59 PMWe need to update index every time when new teams are created, otherwise they will get empty results (e.g. newcomer team5 won’t get even publicly available documents)You could create another attribute called
is_public: true|false
in each documentDima
03/13/2023, 8:59 PMJason Bosco
03/13/2023, 8:59 PM(departments:=[`department1`] && teams:=[`team1`]) || is_public:true
Dima
03/13/2023, 8:59 PMJason Bosco
03/13/2023, 9:00 PMDima
03/13/2023, 9:01 PMJason Bosco
03/13/2023, 9:01 PMDima
03/13/2023, 9:02 PMDima
03/13/2023, 9:05 PM"available for all"
document, but expected "available for department1 (so for all nested teams)"
too, because departments
contains department1
🤔Jason Bosco
03/13/2023, 9:07 PMDima
03/13/2023, 9:08 PMDima
03/13/2023, 9:10 PMDima
03/13/2023, 9:10 PM