---
title: "How can I save edited approval rules so they don't revert to the default approval once a document is transitioned to the close state?"
description: "In Ketryx, item-level approval rules are reset whenever an item leaves the \"Closed\" state, reverting to the default approval configuration. This is a known limitation documented in MAN-11 Approval Rules."
category: "Frequently Asked Questions"
section: "Ketryx Lifecycle Management"
keywords: ["default approval", "approval document", "approval rules", "transitioned", "revert", "close", "level approval", "edited"]
source_url: "https://support.ketryx.com/hc/en-us/articles/38406994807437-How-can-I-save-edited-approval-rules-so-they-don-t-revert-to-the-default-approval-once-a-document-is-transitioned-to-the-close-state"
last_reviewed: 2026-06-11
---

# How can I save edited approval rules so they don't revert to the default approval once a document is transitioned to the close state?

> **In short:** In Ketryx, item-level approval rules are reset whenever an item leaves the "Closed" state, reverting to the default approval configuration. This is a known limitation documented in MAN-11 Approval Rules.

In Ketryx, item-level approval rules are reset whenever an item leaves the "Closed" state, reverting to the default approval configuration. This is a known limitation documented in [MAN-11 Approval Rules](https://docs.ketryx.com/manuals/man-11-approval-rules#id-3.-item-level-approval-rules).

An option here, for more specific approval rules that persist across state transitions, is to configure [project-level approval rules instead](https://docs.ketryx.com/reference/advanced-settings#approval-rules). These are defined in the project’s settings with KQL and apply to all items of a given type, regardless of state changes.

**To configure project-level approval rules:**

1. Go to your project in Ketryx.
2. Navigate to **Project Settings** → **Approval Rules**.
3. Define approval steps for each item type (e.g., documents, requirements), specifying the users or groups required to approve.

**Project-level rules remain consistent even if items are reopened after being closed.**

## Related articles

- [Why don't I see an approval button for my release documentation?](why-don-t-i-see-an-approval-button-for-my-release-documentation.md)
- [How can I make document templates require approval?](how-can-i-make-document-templates-require-approval.md)
- [Who is able to approve milestone documents? How do you control who is able to approve milestone documents? Why can't I approve a milestone document?](who-is-able-to-approve-milestone-documents-how-do-you-control-who-is-able-to.md)
- [I See 1/1 approvals on a ticket. However, Jira still says that I need the owner to sign.](i-see-1-1-approvals-on-a-ticket-however-jira-still-says-that-i-need-the-owner.md)
- [What is the difference between organization permissions and project permissions in Ketryx?](what-is-the-difference-between-organization-permissions-and-project-permissions.md)