> For the complete documentation index, see [llms.txt](https://docs.datacake.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datacake.de/device/claiming.md).

# Claiming

## What is Claiming?

You can share your Datacake devices with others using a pin code and serial number without having to invite those persons.These persons only need to register for use on the Datacake Cloud.

If you give the pin code and serial number to these persons, they can "claim" the device by entering both into their workspace.

{% hint style="warning" %}
Pincode claiming is only available for paid devices!
{% endhint %}

### What is this for?

With the help of pin code and serial numbers, devices can be delivered anonymously. The end user can insert the devices you have purchased into his workspace by entering the pin code and serial number. You do not need to know in advance who the person actually is. This is ideal for:

* Selling or renting products without knowing who the end user will be.
* Providing the functions of a device.
* Sharing devices.
* Involving dealers.

Claiming gives another workspace access to a device that stays yours. If the device should stop being yours altogether, move it instead.

{% content-ref url="/pages/PGGViWfIhOLcpRltmYPM" %}
[Moving Devices](/device/moving-devices.md)
{% endcontent-ref %}

## Set Pincode

Open the configuration of your device that you want to share via the claiming. Inside of the General section, under "Device Claiming", select "Device can be claimed into other workspace".

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

{% hint style="success" %}
As long as the pincode is not set, the device cannot be claimed by another user, even if he knows the serial number.
{% endhint %}

### Claim Code

In this text field you can enter any pin code. It can consist of numbers, letters or both.

## Claim a Device

To understand how claiming works, we will also show you how to insert a device into a workspace using the combination of pin code and serial number.

First of all navigate to your fleet view (Fleet / All Devices) via the sidebar (marked red in the following screenshot).

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

Now add a new device. To do so, please click on the button "Add Device". Now the following modal will appear:

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

Select "Pincode claiming" from the collection of available device types. You can also recognise this by the QR Code symbol.

Please enter the serial number and the pin code in the corresponding text fields. To add the device, confirm your entry with either "Add Device" or "Add Device and configure" (the latter will take you directly to the configuration of the device).

If the pin code and serial number have been entered correctly, the claiming was successful. The device is now available in your workspace.

## Managing Claims

As the owner of a device you can see which workspaces have claimed it, and take those claims back.

Open the configuration of the device. In the General section, under "Device Claiming", you will find a list called "Claimed by". Each entry shows the workspace that claimed the device and the organization that workspace belongs to.

{% hint style="info" %}
The list is only shown in the workspace that owns the device. If you are looking at a device that you claimed from somebody else, you will see a short note pointing you to the owning workspace instead.
{% endhint %}

{% hint style="warning" %}
A claim gives a workspace access to the device, so make sure at all times that you make the claim code and serial number available only to selected persons.
{% endhint %}

### Revoking a Claim

Select "Revoke" next to a workspace and confirm. The workspace loses access to the device immediately.

{% hint style="warning" %}
The workspace you revoke is not notified. The device simply disappears from it.
{% endhint %}

### Making the Device Claimable Again

Revoking a claim does not make the device claimable again on its own. As described under [Auto-Deactivation](#auto-deactivation), claiming switches itself off once a device has been claimed, and stays off until you switch it back on.

To hand the device to somebody else, select "Device can be claimed into other workspace" again and save. The configuration tells you when a device has a claim code but is not open for claiming, so you can see when this step is still needed.

{% hint style="warning" %}
The workspace you revoked probably still knows the claim code. If you make the device claimable again without changing the claim code, that workspace can simply claim the device back. Change the claim code first.
{% endhint %}

## Security

### Auto-Deactivation

Once a device has been claimed by a user into another workspace using the claiming function, that function is automatically deactivated.

{% hint style="info" %}
If the device is then to be claimed again, the function must be reactivated as described above.
{% endhint %}

### Pin code override

The pin code option is also available to your end customers. This means that the person who added one of your devices to his workspace via claiming can also reactivate the claiming and assign a different pin code.

{% hint style="info" %}
This pin code is bound to the device itself. This means that you can also see the changed pin code of the end user.
{% endhint %}

### Selling Products

If you use the claiming in your sales activities and you sell the products anonymously, you usually do not know who the end customer will be.

If you still want to provide proactive support, then have your customers invite you to their workspace. In this way, your customers will have explicitly agreed to the access and are on the safe side as far as data protection is concerned.


---

# 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.datacake.de/device/claiming.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.