> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/semantic-model-editor/delete-a-semantic-model.md).

# Delete a semantic model

Delete a semantic model that you no longer need for analysis or reporting. 

Complete the following steps to delete a semantic model: 

1. Log into the **Pentaho User Console** (PUC).  
2. Open the Semantic Model Editor by taking one of the following actions:

   * If you are using the Modern Design of PUC, in the menu on the left side of the page, click **Semantic Model Editor**.
   * If you are using the Classic Design of PUC, click **File** > **Semantic Model Editor**. 

   The **Semantic Model Editor** opens. 
3. In the **Semantic Models** list, navigate to the model you want to delete by searching or scrolling through the list. 
4. In the row that contains the semantic model you want to delete, click the **More Actions** icon, and select **Delete**. The **Delete Model** confirmation window opens. 
5. Click **Delete**. The semantic model is deleted. 


---

# 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.pentaho.com/pba/semantic-model-editor/delete-a-semantic-model.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.