Nembl
Services
Publishing & Visibility

Publishing & Visibility

Publishing controls when your services and offerings appear in the service catalog and who can see them. Until you publish, your service remains in draft mode and is only visible to administrators.

Draft vs. Published

Every new service starts as a Draft. While in draft mode:

  • The service does not appear in the service catalog.
  • Only administrators can see and edit it.
  • You can take your time adding offerings, forms, and workflows without anyone else seeing incomplete work.

When you are ready, publishing the service makes it visible in the catalog based on the visibility level you choose.

How to Publish a Service

  1. Go to Admin > Services and open the service you want to publish.
  2. Make sure it has at least one offering with a form attached.
  3. Click the Publish button.
  4. Choose a visibility level (see below).
  5. Confirm and your service is live.

You can unpublish a service at any time to remove it from the catalog. Existing in-progress requests will continue to completion, but no new requests can be submitted.

Visibility Levels

When publishing, you choose who can see and request your service. Nembl offers three visibility levels:

Internal

The service is visible only to people within your company. This is the most common setting for internal processes like IT support, HR requests, or team-specific workflows.

  • Only users who belong to your company can see the service in the catalog.
  • Use this for any process that should stay within your organization.

Partner

The service is visible to your company and to specific partner companies you have connected with. This is useful for B2B workflows where you provide services to known business partners.

  • Only your company and approved partners can see the service.
  • Partners must be connected through the B2B registry before they can access partner-level services.
  • Use this for supplier portals, vendor intake processes, or partner collaboration workflows.

Public

The service is visible to all Nembl users through the B2B service registry. Any company on the platform can discover and submit requests to your service.

  • Your service appears in the public B2B registry.
  • Any Nembl user can browse, find, and submit a request.
  • Use this for services you want to offer broadly, such as order intake, customer support, or public-facing request processes.

The B2B Service Registry

The B2B registry is a shared catalog where companies publish services for other companies to discover. Think of it as a marketplace for business services.

When you set a service to Public or Partner visibility, it appears in the registry. Other companies can:

  • Browse available services by category.
  • View service descriptions and offerings.
  • Submit requests directly through the catalog.
  • Track their requests just like internal ones.

This is how Nembl enables cross-company workflow orchestration. A request submitted by Company A to Company B's public service flows into Company B's inbox and follows their workflow, while Company A can track progress from their own dashboard.

Publishing Individual Offerings

You can also control visibility at the offering level. This is useful when a service has a mix of internal and external offerings. For example, your "IT Support" service might have:

  • "Password Reset" — Internal only
  • "Guest Wi-Fi Access" — Available to partners

To set offering-level visibility, open the offering and adjust its visibility setting independently of the parent service.

Changing Visibility After Publishing

You can change a service's visibility at any time:

  1. Open the service in Admin > Services.
  2. Click Settings or the visibility indicator.
  3. Select the new visibility level.
  4. Save your changes.

The change takes effect immediately. If you reduce visibility (for example, from Public to Internal), external users will no longer see the service in their catalog, but any existing requests from them will continue to completion.

Checklist Before Publishing

Before you publish, make sure:

  • The service has a clear name and description.
  • At least one offering is configured with a form.
  • The form collects all the information you need to process requests.
  • A workflow is linked if you want automated processing.
  • You have chosen the right visibility level for your audience.