Skip to main content
Skip table of contents

Responsible Party Bulk Update

This feature gives admins and super admins the ability to update the Primary Responsible Party for a large number of contracts.

To perform a bulk update of a Primary Responsible Party:

If the user navigates away from the bulk update wizard, any information entered will be cleared.

  • Go to Explore > Reporting > Contracts.

  • Filter the table by Primary Responsible Party, Status=Active, and any other desired criteria so the table shows only the contracts on which you want to replace the Primary Responsible Party.

  • Select Bulk Update.

  • Step 1: Select contracts.

    • Review the contracts carefully to ensure the list is correct. Uncheck any contracts you want to exclude from the bulk update.

    • OPTIONAL: Manage columns and/or export the table.

    • Select Next.

  • Step 2: Select operation.

    • Select the Primary Responsible Party you want to replace.

    • Select the new Primary Responsible Party, then click Next.

  • Steps 3 and 4: Define rules.

    • Define Rule 1, i.e., what should happen on selected contracts if the user lacks sufficient permissions to them:

      • Apply an Editor-level permission override

      • Apply a Contract Moderator-level permission override

      • Don’t change the Primary Responsible Party

    • Define Rule 2, i.e., what should happen on selected contracts if the user is already a Secondary or Tertiary Responsible Party:

      • Leave the Secondary or Tertiary field blank

      • Don’t change the Primary Responsible Party on these contracts

  • Admins and super admins can report on changes made via bulk update so they can validate and review those changes in Explore > Reporting > Bulk Update. Only admins and super admins can see this tab.

  • On the contract summary page, users can see responsible party changes under Field Change History, in the Responsible Party tab.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.