- Get Started
- DownloadsPlatformsResources & Plugins
- Features
- News
- Training & Support
- Videos
Registry Administrators are responsible for assigning roles in the registry to the members of their organization, managing users and projects, and other tasks.
Watch the webinar about Registry Administrators here, or read the written instructions below.
When editing your organization in the registry, you have access to the following tabs.
Registry Administrators are responsible for assigning roles in the registry to the members of their organization. They need to make sure that the following roles are assigned to staff who can perform them:
The Roles tab on the organization lists all of the approved users for your org and also shows users waiting to be approved.
There is an option to set an auto-approval email domain, so that requests from your org’s email address do not have to be approved.
WARNING: Not everyone in your org qualifies for a Paratext license. So even auto-approved users should be vetted to have a role in a translation project.
To assign roles in your organization:
To assign a role to someone outside your organization:
If you do not have enough people inside your organization to manage these roles, you may use the Add User to Organization button at the bottom of the roles page to assign the role to someone from a partner organization. You will only be able to see and add them if you are a supporter in the organization they belong to. (Supporters are able to see the users in the organization they support).
This tab shows where your org fits in the registry structure. You can move to sub-orgs or parent orgs quickly here.
This tab lists all the projects that are managed by your organization. These project registrations are editable by you as the administrator.
You can edit or update details about a project, such as its status, or view its members, progress, and see details about its history.
You also have the ability to manage user roles in a project. In most circumstances, the project administrators should add or remove members, but if there is a special reason, you can add or remove members of the project, or change their role in the project
Shows what Paratext text resources people in this org have access to
At a glance, you can see the number of Paratext projects that exist in each of the six following status categories:
Shows which projects have a Project Plan applied and are reporting their progress.
Shows which versions of Paratext your members are using.
Here are a number of situations you may encounter and how to solve them in your role as Administrator.
First, users should know that they can re-issue / reset their own code! Any user with an email address can generate a new code for themself after logging in to the Paratext Registry.
If the reason they cannot log in to the registry is because they no longer have access to their registration email, it is better to help them gain access to the registry:
Once they have confirmed their new email by clicking on the link in the message, they can log into the registry with their new email, and then remove the old email from their profile.
If they cannot log in to the registry, a registry admin can generate a new code for them:
Registry admins, project admins, membership approvers, and supporters can register new users who have no email address.
When you finish, the registry will generate a user code for them, which you will see, and you will also get a copy of it by email.
Note: A member who was registered by another without an email cannot log in to the registry to give themselves a new code. The person who registered them can generate a new code for them. If you look on their profile, you will see the name of the person who registered them.
It is much easier for a user to request membership of a different organization than for an admin to move them to a different organization. The best approach would be to tell them how to request membership in the different organization or if needed, impersonate them (see above on impersonating a user) to request the organizational change.
How a user can request a change of organization
If an admin removes a user from an organization, assigning that user to another organization requires administrative rights for the whole registry, (in technical terms, administrative rights over “root”).
The user will get a new registration code emailed to them and their current code will be disabled. They will not be able to send/receive until their new code is applied.
Back translations should not be included unless they are intended to be published. If not, they should be set up in Paratext as a Back Translation project, which will be linked to the parent project and will not need a registration.
After a team has setup a Project Plan and starts tracking progress, you will be able to see their progress on the Progress tab.
A project can be moved from one organization to another if needed.
Like with moving a user, you may need to coordinate this if you do not have authority within the new organization.
The option to revoke the registration a project is for those with Registration Reviewer permission. This is to be used in case of copyright infringement or other issue.
This will only delete the registration for the project. This will NOT delete the actual project files for users on the project. To delete a project entirely, see the How do I delete a project? topic in the Paratext Help.