Members of a confidential project can see it in the registry, but it is not visible to other registry users, even in the same organization. It can be seen, however, by people in the project’s managing or contributing organizations that have a role of Administrator or Registration Reviewer in the registry. Supporters in those organizations do not have access to confidential projects unless the project is directly shared with them.
In addition, there are two more roles that can see confidential projects:
- Root level administrators
Those who administrate the registry can necessarily view these projects to resolve problems and make requested changes. - Confidential project reviewers
In order to prevent users from using confidential projects to circumvent the Paratext Terms of Use, a reviewer from SIL and one from UBS each perform the role of Confidential Project Reviewer. Their task is to ensure that confidential projects are not abusing copyright, or bypassing restrictions to use publishing tier tools.
Lastly, progress.bible has access to confidential projects in order to report on progress, without revealing specifics at a project level. Individual members of projects are not listed in the data progress.Bible can access. The reporting that progress.Bible enables is set up so that only the organization(s) involved in a project can see detail, and the kinds of detail reported on also depend on the role the organization has in relation to a project. There is NO use of Paratext Registry data through progress.Bible that involves a public audience.
