> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/example-gallery/example-applications/starter-with-record-locking-example-project.md).

# Starter with Record Locking Example Project

Download the attached project and import it into your Designer account. Follow the customization steps to associate your Assessment Framework (or other) application with this project.

To activate the record locking, take the following action:

* Turn on *Security Authentication* to activate the admin and user roles (Modify Project Settings).
* Publish the project to expose the roles to the *User Management* module.
* Create any additional user accounts and associate them with a project role.

Once you have completed these steps, launch the Starter, sign in, start then save a session, and resume it. From this point, any other user with access will see the session in use. If they select this session, the system presents the user with the following choices:

* Return to the session list.
* Continue with the session, including any edits made by the first user.
* Continue with the session, overwriting any edits made by the first user.

## Attachments

* [Locked Records Demo.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/36rs00-Locked-Records-Demo.zip)


---

# 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://community-test.logicnets.com/release-9/example-gallery/example-applications/starter-with-record-locking-example-project.md?ask=<question>&goal=<user_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.