> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/portfolio-management/service-portfolio/service-status-in-the-portfolio.md).

# Service Status in the Portfolio

Your Service Portfolio isn't just a list of what you offer, it also tracks where each service sits in its lifecycle. The status tells you whether a service is actively available in the marketplace, winding down, or completely out of your active portfolio.

This way you keep control over your offering without losing existing customer services or any historical data.

### Where to Change a Service's Status

You'll find the status settings directly in the Service Portfolio:

1. Open the **Service Portfolio** in equipme.
2. Select one or more services from the list.
3. Click **Actions** at the top.
4. Choose **Status**, then pick one of these:
   * **Activate**
   * **Deactivate**
   * **Archive**

Whatever you select applies to all the services you've marked.

### **The Three Status Options**

#### <mark style="color:green;">Activate</mark> – Service is Live

An activated service is a regular, working service in your portfolio.

Here's what that means:

* The service shows up in the Marketplace.
* Customers can order it.
* It appears everywhere you work with portfolio services—in categories, linked services, templates, and onboarding scenarios.

You'll use this status for everything you're currently selling.

#### <mark style="color:red;">Deactivate</mark> – No Longer Sold, But Still in the System

Deactivated services sit in the middle. They're not offered anymore, but they're still fully in the system.

You'd typically use this when you want to pull a service from sales but keep it around for existing customers, billing, or while you're restructuring your portfolio.

Here's what happens:

* The service gets hidden from the Marketplace.
* New customers can't order it anymore.
* It stays visible in the Service Portfolio so you can keep managing it.
* Any existing orders and running services based on it stay exactly as they are.

Deactivating works well when a service is ending, getting reworked, or about to be replaced—but you still need it for a while.

#### <mark style="color:purple;">Archive</mark> – Out of Your Active Portfolio

Archived services aren't part of your active portfolio anymore, but they stick around in the background for history and existing services.

What this looks like:

* The service disappears from your active Service Portfolio list.
* It's gone from the Marketplace and nobody can order it.
* You won't see it during daily portfolio work, which keeps things tidy.
* The data stays intact. Existing customer services keep running and you can still manage and bill them.

Archiving makes sense when a service is done for good, fully replaced by something new, or you're cleaning up your portfolio without wiping the history.

### Quick Summary

Status controls where a service sits in its lifecycle:

* **Activate** – Visible and orderable.
* **Deactivate** – Not sold anymore, but stays in the portfolio and all existing processes.
* **Archive** – Removed from active view, but preserved for existing services and history.

If you want to keep your portfolio clean, think of it like this: deactivate services when they're winding down, then archive them once they're completely out of your active offering.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.equipme.io/documentation/portfolio-management/service-portfolio/service-status-in-the-portfolio.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.