---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/employee-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Opportunity publishing approval

# Opportunity publishing approval {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Opportunity publishing approval

The Opportunity Marketplace's publishing approval framework streamlines the approval process for gig, volunteer, and project opportunities.
Opportunity Owners can submit draft opportunities for approval directly from the creation form and track the status.
Notifications are sent to both owners and approvers regarding approval or rejection decisions, enabling efficient communication and management of opportunity publishing.
Show full answer Show less  

## Approval Workflow

The framework includes out-of-the-box subflows tailored to each opportunity type (gig, volunteer, project) that automate the approval process based on configurable conditions:

* **Gig opportunities:** Require approval if the time commitment is 20+ hours per week. The owner's manager is also assigned as an approver in addition to those listed.
* **Volunteer opportunities:** Require approval if there are 20 or more participants.
* **Project opportunities:** Require approval if there are 5 or more participants.

Once conditions are met, approval requests are sent to designated approvers listed in a dedicated table. Approvers receive email notifications and approval tasks, allowing them to approve or reject drafts with comments. Approved opportunities are published and owners notified; rejected opportunities revert to draft status for revision and resubmission.

## Configuration and Flexibility

Administrators can configure:

* Which users or groups act as approvers, including adding users to the default **OPM Opportunity Approvers** group or assigning approvers per opportunity type.
* Approval rules such as requiring multiple approvals or multiple rejections before publishing or blocking an opportunity.
* Assignment of approval subflows especially for volunteer and gig opportunity types, which require manual assignment.

Custom opportunity types can reuse existing approval subflows designed for project or volunteer opportunities.

## Benefits for ServiceNow Customers

* Automates and standardizes the approval process for opportunities, reducing manual oversight and delays.
* Enhances transparency and communication through notifications and approval tracking.
* Offers flexible configuration to meet organizational policies on approvals and publishing criteria.
* Supports governance and quality control by enabling approvers to review drafts before publishing.  
The Opportunity Marketplace's publishing approval framework streamlines the approval process, allowing Opportunity Owners to submit drafts for approval and receive notifications upon approval or rejection.
In versions 2.3 and later, Opportunity Marketplace includes an out-of-the-box framework to automate the publishing approval workflow for the gig, volunteer, and project opportunity types.

* The Opportunity Owner can submit a draft opportunity for approval from the Create an opportunity form and monitor the status of the approval request. They receive an email notification when the Opportunity Approver approves or rejects the draft.
* The Opportunity Approver is notified of the approval request via email and an assigned approval task. They can review the opportunity draft and either approve or reject with comments from the notification interface.
* Admins can configure approver users and additional approval rules.
{#egd-oppt-pubs-approval__ul_zgy_nlk_y2c}

## Approval workflow {#egd-oppt-pubs-approval__section_qb1_rlk_y2c}

Each out-of-the-box opportunity type (gig, volunteer, and project) has a respective subflow to facilitate the approval workflow. Each subflow has default configurations, which determine the conditions under which the opportunity is
sent for approval.

1. If the conditions are met, the subflow requests approval from the users listed in the Opportunity Type Auxiliary \[sn_opp_market_opportunity_type_aux\] table for that respective opportunity type.
2. If an approver approves the opportunity, the system notifies the Opportunity owner and publishes the opportunity.
3. If the approver rejects the opportunity, the system reverts it to draft state and notifies the owner. The owner can then implement the feedback and resubmit for approval.

{#egd-oppt-pubs-approval__ol_mwp_slk_y2c}  
Note:  
By default, only one approval is necessary for the system to publish an opportunity, and only one rejection is necessary to prevent an opportunity from being published, however the admin can configure alternative approval scenarios, such as requiring a greater number of required approvals or at minimum two rejections. For more information, see the Approvers section below.

The following diagram provides a visual of the approval workflow:  
The following describes the default configurations for the subflows, which can be modified in the Workflow studio. {#egd-oppt-pubs-approval__table_a2d_4qk_y2c__entry__2}

| Subflow | Settings description |
|-|-|
| Gig opportunity posting \& editing approval | This subflow sends the opportunity for approval if it requires a time commitment of 20 or more hours per week (line 2). Unlike the other two subflows, this one assigns the opportunity owner's manager as the approver (line 7-10) in addition to the listed approvers. |
| Volunteer opportunity posting \& editing approval | This subflow requires approval for the opportunity if the total number of participants is twenty or more (line 1). |
| Project opportunity posting \& editing approval | This subflow requires approval for the opportunity if the total number of participants is five or more (line 1). |
[Table 1. Default settings for out-of-the-box subflows]

{#egd-oppt-pubs-approval__table_a2d_4qk_y2c}  
Note:  
Only the `Project opportunity posting & editing approval` flow is assigned to the project opportunity type out-of-the-box; for volunteer and gig opportunity types, the admin must manually assign the flow. For the steps on assigning the approval flows, see [Creating custom opportunity types in Opportunity Marketplace](https://servicenow-prod.fluidtopics.net/buZOdnTzDIlHZzYOUi0~Lg "Opportunity Marketplace comes with 3 base system Opportunity types. If you need a different opportunity type, you can create custom opportunity types to meet the needs of your organization. You can also create custom user criteria, opportunity details, and roles and requirements.").
For custom opportunity types, the admin can reuse either the `Project opportunity posting & editing approval` or `Volunteer opportunity posting &
editing approval` flows, as they support opportunities with multiple roles.

## Approvers {#egd-oppt-pubs-approval__section_wmm_2rk_y2c}

If your instance has demo data loaded, the group `OPM Opportunity Approvers` is assigned to the gig, volunteer, and project opportunity types. An admin can add users to the `OPM Opportunity Approvers`
group to review all opportunity drafts. Alternatively, the admin can define approvers for a specific opportunity type. For the steps on assigning approvers to an opportunity type, see [View and manage the opportunities created in Opportunity Marketplace](https://servicenow-prod.fluidtopics.net/wCn3jBF_4bpEol6xuWEE1g "Opportunities are created to solicit individuals to apply for roles within the opportunity. As an Opportunity Marketplace admin [sn_opp_market.admin], you can view and manage opportunity records from the ServiceNow platform.").

By default, the subflow requires one approval or rejection. Admins can configure alternatives, such as requiring multiple approvals or two rejections to block publication.