> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/social-registry/features/lock-and-unlock.md).

# Lock and Unlock

In Social Registry (SR) huge volumes of data are recorded. There is a need to set a limit to prevent the data from being edited multiple times. If the limit is set, it improves the accuracy of the data. The Social Registry has the Lock and Unlock feature which plays a pivotal role in maintaining the integrity of the recorded data.

## Lock

The Lock feature prevents data from being edited inadvertently or without appropriate permissions. When the records are loaded on SR and SPP, the limit is set to edit the data only once. If the records are edited once, the Lock feature disables the record from being edited again.

## Unlock

Records may be unlocked to be edited following the below process:

* The user must send a request with a valid reason to the Admin (with permissions to allow lock/unlock)
* The Admin validates the reason and approves the request.
* The user can then edit/update the records.
* If the request is rejected, the record remains locked.

## Notification

If there are updates to the records, Admin will send a push and an email notification to the user. The email contains the information on the record that needs to be edited/updated.

## Log

The Log feature captures the status of the records such as the information on the

* records the user has requested for unlock.
* edited record details.
* notifications sent for a record.
* approved/rejected record requests.


---

# 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.openg2p.org/1.3/social-registry/features/lock-and-unlock.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.