Skip to main content

Closing Opportunities: Amplify Site Managers

How Amplify Site Managers, or deactivate, volunteer Opportunities

Written by Brittany Crow

❖ Heads up! This article is only intended for Amplify Site Managers.

By the end of this article, you will be able to:

  • Deactivate a volunteer Opportunity

  • Understand when to deactivate vs. expire an Opportunity

  • Review and manage inactive Opportunities

About Deactivating Opportunities

Deactivating an Opportunity removes it from active use. Once deactivated, volunteers can no longer respond to the Opportunity or log hours to it. Deactivated opportunities are not visible to volunteers but remain accessible to site managers for administrative purposes.

Opportunities that reach their end date automatically transition to the "Expired" status. Expired opportunities are hidden from volunteers but remain visible in their profiles for historical reference, including past opportunities and logged hours. If you want to manually stop new responses while still allowing existing scheduling or completion, consider marking the opportunity as "Inactive" instead.

Deactivate an Opportunity

You can deactivate an Opportunity in two ways: by changing its status to Inactive or by using the Deactivate button.

  1. Go to Volunteerism > Opportunities.

  2. Click on the Opportunity Title from the table.

  3. Change its status from Active to Inactive, or scroll to the bottom of the Update Opportunity page and click the red Deactivate button.

  4. Be sure to click Update Opportunity to save your changes!

It might be a good idea to check the box beside Notify respondents of this update, especially if volunteers have responded to the Opportunity.

Reviewing Inactive Opportunities

  1. Go to Volunteerism > Opportunities.

  2. Select Inactive from the Status column dropdown.

From here, you can select an inactive Opportunity to update it or reactivate it as necessary. You can also review any Pending Opportunities or filter the list back to your Active Opportunities.

Did this answer your question?