Manage package administrators and editors

What's the difference between a package editor and a package administrator?

A package administrator is the default role for the person who creates the package. They have the right to add, remove, or modify the role of a package collaborator, whether an administrator or an editor. They also have the right to close or reopen a package.

A package editor has the right to add or remove other package editors.

The table below shows the different actions each role can perform.

Add/edit administrators and editors

1. From the main menu, double-click Packages to open your Package Register.
2. Click on the package you want to modify.
3. Click Collaborators in the left-hand column.
   In the main part of the screen, you’ll see a list of editors and administrators for the package. Here you can modify their access level (editor or administrator) or remove their ability to modify the package. You can also add another editor or administrator.

• To add a new package administrator or editor, enter their name in the Add Person field.
• Anyone you add will be an editor by default. Select an option from the drop-down menu to change their access level.
• To remove a collaborator, click the X.

Are you adding editors from multiple organizations?

If you want multiple organizations to edit a package, you’ll need to keep package versioning in mind. Each time a package is edited, a new version of that package is created.

If your project requires multiple organizations to edit packages, make sure you have a clear process on how and when each organization will update them. Otherwise if you update a package at the same time as another organization, the updates you made to the package could be superseded by the other organization.

After updating a package make sure you transmit the latest version to the other organizations. This ensures all organizations have the latest version of the package as early as possible and should reduce the likelihood that the version of the package you created is superseded by another organization.

Edit administrators and editors in bulk

1. Select the packages you want to update (1000 limit).
2. Click Package Management, then select Edit Administrators/Editors in Bulk.

3. From the bulk edit panel:

• Click Add users to add administrators or editors.
• Click the pencil icon to edit the access level of a collaborator.
• Click the remove icon to remove collaborators from the package if required.

4. Click Update when you have finished making your changes.

Access levels, status and permissions

When adding users as collaborators, they will automatically be added to the distribution list as well, which is the same behavior as within the package. 

Access levels

There are three types of access levels: Administrator, Editor and Mixed. 

The access level Mixed means, that you might not be a collaborator on all of the selected packages, or that your access level is different. For example, on one of the packages you might be an administrator, on others you might only be an editor. If you have enough permission to change the access level, you could change it from Mixed to Editor for example. This would add you to all of those packages where you are not an editor yet. However, this would downgrade your access level on all of those packages where you are an Administrator. 

Status

There are two statuses for the distribution: On the list and Mixed. 

On the list means that you are on the distribution list of all of the selected packages. Mixed means that on some of the packages selected you are on the distribution list, but on others you are not. If you change from Mixed to On the list you will be added to the missing ones. 

Permissions

For permission to edit the access level, the same rules you’d have to edit collaborators within a package would apply. This means that if you are an Editor on one of the packages selected, you won’t be able to add Administrators or to upgrade an existing Editor to Administrator. If you don't have permission to edit the collaborators on all of the selected packages, you’ll see a message telling you.

What happens if a Package Administrator leaves the project or organization?

If a package no longer has an administrator (because they left the project) you can add a new one if you have permission.

You'll need the Package Administrator permission assigned to your user role. This permission allows you to:

• Add a new Administrator for packages administered by your organization.
• Assume the Administrator role on packages administered by another organization on a package-by-package basis if the following conditions are met:
  
  • You are from the project-owning organization.
  • The organization(s) that previously administered the package is set to Archive status on the project.

Assume Administrator for packages administered by another organization

1. Click on the package you want to modify.
2. Click Collaborators in the left-hand column.
3. If the above conditions are met, you'll see an Assume Administrator button.
4. Click Assume Administrator. You will be added as an Administrator. You will have full Administrator rights on the package.  A new event will be added to the package Event Log of all organizations affected by this change to indicate that the project-owning organization has assumed administration of the package.

Note: The action to assume the package Administrator role by the project-owning organization can only be completed on a package-by-package basis.