The private mission visibility was added, but does not have any implementation yet. Setting a mission as private would only allow access to communities (or maybe even people?) that have been given explicit permission to do so.
This requires an additional MissionAccess tables (or sth. similar), keeping track of mission access. This table would also have to be queried when fetching or interacting with missions, just like the other checks currently in place.
Tasks
[x] Add model for configuring/storing mission access
[x] Add check for mission access to all currently checked mission endpoints
The
privatemission visibility was added, but does not have any implementation yet. Setting a mission asprivatewould only allow access to communities (or maybe even people?) that have been given explicit permission to do so. This requires an additionalMissionAccesstables (or sth. similar), keeping track of mission access. This table would also have to be queried when fetching or interacting with missions, just like the other checks currently in place.Tasks