> 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.

The state transition diagram of a category.

### State description

State	Definition
New	This is the initial status for a newly created category. This state is not visible on the interface.
Published	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.
Unpublished	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.
Deleted	The category has been deleted. When a category is deleted, all configurations for that category across all accounts are also removed.

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.platform.softwareone.com/developer-resources/rest-api/notifications-api/categories/state-diagram.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.