> For the complete documentation index, see [llms.txt](https://docs.iotify.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotify.io/concepts/understanding-a-test/locking-unlocking-a-test.md).

# Locking/Unlocking a test

With workspaces, it becomes really easy to collaborate with your teammates. Everyone in the workspace can access the same tests and work on them (granted they have proper permissions). However, while you are working on any test in the workspace, you would not want another person to be able to open and modify the test at the same time. 

To avoid this situation, when a workspace has multiple users, once any user starts working on a test and saves it, the test is locked for everyone else. When a test is locked, a small lock icon is shown beside its name in the test list.

<figure><img src="/files/wfhSnUdYR3SrqsgGDD7f" alt=""><figcaption></figcaption></figure>

Everyone else will still be able to open the test and view the contents and even start simulations for the test, but they can't modify the test until it is unlocked.

<figure><img src="/files/MqKgvmkJPIDL6oYXAyKM" alt=""><figcaption></figcaption></figure>

The user who has locked the test has an Unlock button, which they can use to unlock the test. The test will automatically get unlocked if the user has closed the tab or if there was no activity for over 30 minutes. Additionally, any user with an Admin role in the workspace will also have the Unlock button in the test editor.

<figure><img src="/files/LCdSAAfhx2De5VlFGGvK" alt=""><figcaption></figcaption></figure>


---

# 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.iotify.io/concepts/understanding-a-test/locking-unlocking-a-test.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.