Registry Supporter’s Guide

The role of Supporter in the Paratext Registry gives access to useful information that will help troubleshoot problems with projects and user accounts.  Supporters are unable to modify information directly, but can use this information to help users identify problems and resolve them.

Page Contents

Registry Supporter Webinar

Watch the webinar about Registry Supporters here, or read the written instructions below.

What can a supporter do?

  • Discover which users are using outdated versions of Paratext and need to upgrade for the safety of their data.
  • In the case of a forgotten password, look up the email address that a user has registered with.
  • In the case of a lost registration code, help find the exact registration name and email address in order to help the user log in and regenerate the code.
  • Learn who registered a given user when they were registered without an email address. (That person can regenerate the registration code.)
  • Learn who the administrator or consultant is for a given project.
  • Find out a user’s registration approval status. Which organization have they applied to?
  • By viewing the history of organizations, users, or projects, it is easy to troubleshoot problems related to registration or migration.
  • Find out if a given project has been migrated to Paratext yet.
  • Discover when a team has incorrectly registered a back translation or auxiliary project as a standard project.
  • Find out who the registration approvers for the organization are, in order to contact them and expedite a registration approval.
  • Check to see what resources are available for a particular organization, since not all organizations have access to the same resources.

Where to look for this information

The registry displays tabs for ProjectsUsers, and Organizations.

Projects

A supporter in an organization will be able to see the following additional tabs and information about it or its children that a registered user can’t see:

  • Members: All the members who are part of the project, and their roles.
  • History: The list of changes and additions made to users and their roles in the project, and any changes to the metadata of the project.

Users

A supporter in an organization will be able to see the following additional tabs and information about it or its children that a registered user can’t see:

  • Basic: The user’s registration name and the email address they registered with.  If they were not registered with an email address, you can see the person who registered them.
  • Projects: A list of all the projects the user belongs to that are in an organization you support. (Projects will be hidden if confidential or if belonging to an organization in which you do not have a support role.)
  • Roles: The registry management roles, if any, that the user performs for their organization.
  • Activity: The user’s footprint in the registry, all the actions they have performed for themselves or on behalf of others, beginning with their initial registration.
  • History: All the actions performed to or for the user, like changing their role, or generating a new registration code.

Organizations

A supporter in an organization will be able to see the following additional tabs about it or its children that a registered user can’t see.

  • Roles: View all registered members of the organization and learn who is responsible for the various roles in the registry, such as approving membership.
  • Projects: A list of all the non-confidential projects in the organization.
  • Resources: A list of all the text resources that members of this organization have access to.
  • Status: The total number of projects according to their current status.
  • Statistics: Paratext usage statistics, showing the software versions in use in the organization.
  • History: The list of events, such as membership approvals, which pertain to the organization.

Was this helpful?