> For the complete documentation index, see [llms.txt](https://documentation.rcore.cz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.rcore.cz/paid-resources/rcore_doorlock/troubleshoot/item-give.md).

# Key/card give

`door_key` or `door_card` contains metadata regarding access to specific doors. Therefore, **these items cannot be given using /giveitem** command from your inventory, because the metadata about which doors they belong to will not be there. It is therefore necessary to use one of two ways:

## Command /doorsgive

If you are not using the business module or the door were not created by a business, you can obtain a key or card using the `/doorsgive` command. A menu will appear where you can select which group of doors you want the key for and whether you want a universal key for the entire group or a specific one.

## Business Crafting Table

You can obtain a key or card for doors created by a business using the business crafting table. You can find it on the map under the blip if you are part of a business and have crafting permissions in your business role.

{% hint style="danger" %}
In a business, you can only create keys/cards for doors that you have created in the business you are currently in (have a job in).
{% endhint %}


---

# 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://documentation.rcore.cz/paid-resources/rcore_doorlock/troubleshoot/item-give.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.