> For the complete documentation index, see [llms.txt](https://docs.geosamples.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geosamples.org/for-researchers/manage-samples/transfer-ownership.md).
# Transfer Ownership
Users can transfer the ownership of their samples, SESAR Codes, and group samples to individual users or a Team under 'Settings'. Once the transfer request is sent, the recipient or Team Admin/Owner must accept or deny the request. All pending and past requests will be displayed on 'Transfers Ownership' in the left hand panel.
## Transferring Ownership
1. Click '+ New Transfer' to begin a new transfer.
2. Select from the drop down menu under 'What are you transferring' for select samples, all samples, all samples in a group, and SESAR Code.
3. If you are transferring select samples, please choose 'Specific List of IGSNs' and enter the IGSNs that you want to transfer under 'IGSN List'.
4. Select 'Another User' (personal profile) or 'A Team'.
5. Add a user by searching their name or ORCID or for a Team, search the name of the Team.
6. Click 'Initiate Transfer'.
7. The recipient or team admin/owner will receive an email.
## Accepting Transfers
1. An email will be sent from with notice that there a 'Transfer Request was Initiated'.
2. Click the 'View Transfer' to access the direct link to the 'Transfer Ownership' section or navigate to the page in MySESAR.
3. 'Accept' or 'Deny' the transfer request. If you deny the request, the sample will be listed as 'Rejected' under your 'Past History'. If the sample is accepted, the sample will show up as 'Completed'.
4. Email confirmations for both rejected and accepted transfers will be sent to the original owner and to the new recipient.
**For more information on transferring ownership of samples or SESAR Code, please download our guide below.**
{% file src="/files/9WJWhWyfo7XBmFzdywrd" %}
---
# 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://docs.geosamples.org/for-researchers/manage-samples/transfer-ownership.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.