Hi all,
I was recently a part of a group discussion where there was confusion around what exactly triggered the re-verification of trusting projects with hidden coordinates. Looking through the help documents and previous forum posts, there’s not a clear answer that I could find.
Essentially, the group runs several projects that is mostly based on tracking taxa that have coordinates hidden by default. One is an umbrella project, and it collates several collections. The collections and umbrella project both require the individual to join, and on joining, they are prompted to set their level of trust with hidden coordinates.
However, in the past, it seems like adding people to the projects required the re-establishment of trust settings, so they’ve been sending out manual messages asking people to opt-in again to the trust settings whenever they make changes to the projects. There was also a lot of concern over whether adding admins to the umbrella project would cause trust settings to need to be re-established for collection projects below it. Likewise, would changing settings in a collection subproject cause people to need to re-trust the umbrella project?
What I’m curious about and looking for is a logic flowchart of what causes the trust of hidden coordinates to be triggered for reverification or opting in again. Or, at least, clear documentation of what causes this so I can make my own flowchart to help figure out the changes that will and won’t trigger this.
As far as I am aware, the only reason this should happen is if the requirements of the project are changed (i.e, taxa included), or if the admins of a project change (i.e., someone new is added… does it still happen if someone is removed?).
Secondarily – are users notified and required to opt back in explicitly? It seemed unclear, and it seems like there have been significant changes to the way trusted coordinates are handled in iNat recently. I’ve seen in some of the help articles that no hidden coordinates will be visible for one week if changes are made, but I can’t find much/any information on when a user might need to explicitly opt back in. But, it sounds like this has been an issue with this umbrella project in the past where it had been clearly un-checked as trusted in the user’s project settings, so I’m just trying to dig into this a little bit to determine the project guardrails.