> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/utilities/checkin-checkout.md).
# CheckIn/CheckOut
\
appRules includes a selection that allows you to check-in and check-out project databases.\
Technical users can check-out subsets or the entire project database to enable them to work remotely or to perform testing or other development activity.
The projects are locked after checkouts, not after checkin (see below)
Project databases can also be checked out for installation on departmental computers or for updating any computers in the Development-Test-Production chain.
## Check-Out Project Database
To check-out a project database, select CheckOut All Metadata from the CheckIn/CheckOut menu of the application.
Follow the on-screen instructions and click the OK button to create the new project database.
## Check-In Project Database
To check-in a project database, select CheckIn All Metadata from the CheckIn/CheckOut menu of the Configurator application:
Follow the on-screen instructions and click the OK button to check-in the project database.
## Locking and Unlocking Projects
appRules includes features to lock and unlock projects to minimize contention when using the system for team development.
When using appRules in a multi-user mode, projects are automatically locked when they are loaded into the Studio environment, and unlocked when they are closed or unloaded. To view the lock status of a project, select the project and go to the project detail window the LockStatus property:
At design time, if a project is being held by another user, a warning window will be displayed.
---
# 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.appstrategy.com/apprules-r-documentation/platform/platform-features/utilities/checkin-checkout.md?ask=&goal=
```
`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.