> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/superadmin/users/account-claiming-management.md).
# Account claiming management
Marking a vendor account as claimable and following its claim status
{% hint style="info" %}
*Path: Backoffice > Users > Users*
{% endhint %}
* [Definition](#definition)
* [Marking an account as claimable](#marking-an-account-as-claimable)
* [Setting the claim contact email](#setting-the-claim-contact-email)
* [Reading the claim status](#reading-the-claim-status)
* [Sending the claim link](#sending-the-claim-link)
* [Disabling claiming](#disabling-claiming)
* [The Claimed status](#the-claimed-status)
* [Handling a deletion request](#handling-a-deletion-request)
* [Following claimable accounts from the list view](#following-claimable-accounts-from-the-list-view)
* [Special rules](#special-rules)
* [Related ressources](#related-resources)
## Definition
The "Account claiming" card of the user detailed view is where operators declare that a vendor account may be taken over by the vendor it was created for, and where they follow the progress of that takeover. See User claiming for the overall principle.
The card handles three things: whether the account is claimable, which address the claim invitation is sent to, and what state the claim is currently in.
Accounts created through a bulk import already arrive claimable (see [Importing claimable users](/v2.0/superadmin/users/importing-claimable-users.md)). This interface is used to complete them — typically to add the contact email that the import file did not provide — and to manage accounts created one by one.
The card is only displayed when account claiming is enabled in the platform configuration.
## Marking an account as claimable
By default, the card only displays the "Claimable account" checkbox, unticked (figure 1).
Figure 1
Tick it to make the account claimable. The card then expands and displays the claim status and the claim contact email field (figure 2).
Figure 2
Only accounts created by an operator can be made claimable. On accounts registered by users themselves through the front office, the option is not available.
## Setting the claim contact email
The "Claim contact email" field holds the address the claim invitation is sent to. It is the address of the real vendor the operator wants to onboard, and it is independent from the account's sign-in address: filling it in does not give anyone access to the account.
Enter a valid email address and click "Save the contact email". As long as the field is empty, the account cannot be invited: its claim status stays *Pending (no email)* and no "Send claim link" button is displayed (figure 3).
Figure 3
## Reading the claim status
The claim status is displayed as a badge, followed by the date of its last change (figure 3). It is read only — it reflects what has happened on the account and cannot be set manually.
| Status | Meaning | Available actions on the card |
| ------------------ | ------------------------------------------------------------ | -------------------------------------------------------------- |
| Pending (no email) | Claimable, no contact email. | Save the contact email, disable claiming. |
| Pending | Claimable, contact email set, no link sent yet. | Save the contact email, send the claim link, disable claiming. |
| Link sent | A claim link has been sent and is waiting to be used. | Save the contact email, send a new claim link. |
| Claimed | The vendor owns the account. | None — the card is read only. |
| Deletion requested | The vendor declined and asked for the account to be deleted. | Delete the account manually. |
## Sending the claim link
Once a contact email is saved, the "Send claim link" button appears (figure 2). It sends the claim invitation immediately, without waiting for an asker request or an RFP publication, and the claim status switches to *Link sent*.
The button remains available at the *Link sent* status (figure 4), so that a link can be re-sent to a vendor who did not act on the first one in time. The link is valid for 7 days, and sending a new one invalidates the previous one.
Figure 4
Invitations are also sent automatically when an event gives the vendor a reason to join. See [Account claiming](/v2.0/core-concepts/account-claiming.md) for the list of triggers and the rules that apply.
## Disabling claiming
The "Disable claiming" button reverts the account to a regular operator-created vendor account and clears the saved contact email.
It is only available as long as no claim link has been sent. From the *Link sent* status onwards, the button is no longer displayed and the "Claimable account" checkbox is greyed out (figure 4): an account that has already been invited cannot be made non-claimable again.
## The Claimed status
Once the vendor has taken ownership of the account, the card becomes purely informative (figure 5). The "Claimable account" checkbox stays ticked but greyed out, and the contact email is displayed as plain text instead of an editable field. No action is available, and the account can never be claimed again.
Figure 5
From that point on the account behaves as any other vendor account, and is managed through the standard cards of the detailed view.
## Handling a deletion request
When a vendor declines the claim, the claim status switches to *Deletion requested* and the operator receives a notification. The claim link is invalidated at the same time: the account can no longer be claimed, and no new link can be sent.
The deletion itself is not automatic. The operator carries it out from the same detailed view, with the "Delete this user" action (see [Viewing and managing users](/v2.0/superadmin/users/viewing-and-managing-users.md)).
## Following claimable accounts from the list view
The claim status is displayed on each account in the users list view, next to the account status, with the date of its last change (figure 6). The badge is colour-coded, so that the state of the vendor base can be read at a glance:
Figure 6
| Badge | Status |
| ------ | --------------------------- |
| Orange | Pending, Pending (no email) |
| White | Link sent |
| Green | Claimed |
| Red | Deletion requested |
Two filtering options narrow the list down:
* **Show imported users** — restricts the list to the accounts created through a bulk import.
* **Claim status** — restricts the list to a given claim status.
Each unclaimed account displays two email addresses: the address the platform generated for the account, derived from the sales team mailbox, and the claim contact email declared by the operator. Once the account is claimed, both lines show the address the vendor chose as his sign-in address.
## Special rules
* A claimable account has no password until it is claimed, and therefore cannot be logged into.
* Only one claim link is active per account at a time.
* Claiming cannot be disabled once a link has been sent.
* Platform notifications addressed to an unclaimed account (booking requests, quotes, calls for tenders) can be redirected to the sales team mailbox. See [Account claiming > Configurations](https://features.scnd.com/v2.0/superadmin/users/pages/weI6kCbWjFl1u1R9hDCG#id-1.14.x-recaptchabundle-businessrules-configurations).
## Related resources
SBO:
* [Account claiming](/v2.0/core-concepts/account-claiming.md)
* [Importing claimable users](/v2.0/superadmin/users/importing-claimable-users.md)
* [Viewing and managing users](/v2.0/superadmin/users/viewing-and-managing-users.md)
Front:
* Claim a user account
---
# 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://features.scnd.com/v2.0/superadmin/users/account-claiming-management.md?ask=&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.
