> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Megaport Marketplace Notifications

> This help topic describes Megaport Marketplace notifications during the service provider connection process.

export const Image = ({src, alt = '', caption, width, height, shadow}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Image -';
  if (typeof src !== 'string') {
    src = String(src);
  }
  if (!src || src === 'undefined') {
    console.error(`${errorPrefix} \`src\` is required — rendering an empty string instead`);
    return <></>;
  }
  const img = <img className={['mega-image-style', shadow ? 'shadow' : ''].join(' ')} src={src} alt={alt} width={width} height={height} style={{
    display: 'block'
  }} />;
  return caption ? <figure>
      {img}
      <figcaption style={{
    textAlign: 'center',
    width
  }}>{caption}</figcaption>
    </figure> : img;
};

With a [profile](/marketplace/profile), service providers can receive connection requests.
When a customer starts the connection request, the service provider is notified of the request by email and the service provider can accept or deny the request.

This topic describes:

* The notifications emailed by Megaport to the service provider and the customer requesting the connection.

* How the service provider can accept or deny the request.

* How to configure email notification groups so Megaport Portal users receive only email updates relevant to their position.

## Requirements for customers of service providers

For an end user to connect to a service provider, they need:

* Access to the Megaport Portal
* A Port or Megaport Cloud Router (MCR) on the Megaport network
* Support for Layer 2/Layer 3

## Service provider and customer notifications

After the customer makes the connection request, Megaport sends email notifications to both the service provider and the customer.

<Note>
  When the service provider is approving a connection, they have the option to make configuration changes for their end of the VXC before granting approval.
</Note>

**Notification to Service Provider**

<Image src="/images/marketplace/sp-service-approval-required.png" alt="Notification to Service Provider" shadow={true} width={400} />

<Note>
  If you have configured a form to collect additional information from customers, the submitted form data is included in this notification. For more information, see [Megaport Marketplace Forms](/marketplace/forms).
</Note>

**Notification to Customer**

<Image src="/images/marketplace/customer-service-approval-required.png" alt="Notification to Customer" shadow={true} width={400} />

## Service provider approval

After receiving the email notification about the connection request, the service provider must log in to the Megaport Portal, navigate to the Approvals section on the right side of the screen, and select either **Accept Request** or **Deny Request**.

If you have configured a form to collect additional information from customers, a **Service Request Form** step appears in the approval workflow where you can view the submitted data before making your decision. For more information, see [Megaport Marketplace Forms](/marketplace/forms).

After the service provider accepts or denies the request, Megaport sends a second notification to the customer with the outcome details.

<Image src="/images/marketplace/vxc-service-approved.png" alt="Service provider response" shadow={true} width={400} />

Megaport sends another email to the customer when the VXC is available.

<Image src="/images/marketplace/vxc-service-up.png" alt="VXC is available" shadow={true} width={400} />

This establishes the Layer 2 connection from the customer to the service provider.

For connectivity to multiple destination ports, repeat the creation and approval process for each new connection.

<Note>
  Service providers can also use service keys to control customer access to their ports. For more information, see [Setting up Service Keys](/marketplace/service-keys).
</Note>

If a customer requests a speed change to a higher bandwidth after deployment, Megaport notifies the service provider and they can accept or reject the change.

<Image src="/images/marketplace/vxc-speed-change.png" alt="Speed change" shadow={true} width={400} />

## Configuring Portal users for email notifications

Each Megaport Portal user is assigned a user role that includes privilege levels. Users configured for Company Admin, Technical Contact, and Technical Admin can subscribe to notifications.

For more information, see [Managing User Roles](/portal-admin/user-management/roles).

Users can choose to receive email notifications from each of these groups:

* Financial
* Company
* Ordering
* Services
* Service Status

Notifications can be selected individually or at the group level. For VXC approvals, enable notifications for the Ordering group.

For more information, see [Configuring Email Notifications](/portal-admin/email-notifications).

## Helpful references

* [Creating a Megaport Marketplace Profile](/marketplace/profile)
* [Megaport Marketplace FAQs](/marketplace/marketplace-faqs)
* [Megaport Marketplace Forms](/marketplace/forms)
* [Megaport Marketplace Overview](/marketplace/overview)
* [Requesting a Connection to a Service Provider](/marketplace/connections)