> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/developer-resources/rest-api/notifications-api/categories/state-diagram.md).

# State diagram

The following diagram shows the state (status) transition process of a notification category in the platform.

<figure><img src="/files/HJhKpDqxyg5nNxy4b6ZW" alt=""><figcaption><p>The state transition diagram of a category.</p></figcaption></figure>

### State description

<table><thead><tr><th width="135">State</th><th>Definition</th></tr></thead><tbody><tr><td><strong>New</strong></td><td>This is the initial status for a newly created category. This state is not visible on the interface.</td></tr><tr><td><strong>Published</strong></td><td>The category has been published and is visible on the platform. When a category is created, it is automatically set to the published state. By default, it is enabled for everyone. Users can disable the category in their notification settings if they choose to do so.</td></tr><tr><td><strong>Unpublished</strong></td><td>The category has been published and is visible on the platform. However, a Notification Category in this state cannot be used and is therefore not visible on the platform. An unpublished category can be revived and changed back to a published state.</td></tr><tr><td><strong>Deleted</strong></td><td>The category has been deleted. When a category is deleted, all configurations for that category across all accounts are also removed.</td></tr></tbody></table>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.platform.softwareone.com/developer-resources/rest-api/notifications-api/categories/state-diagram.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.