> 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/accounts-and-access/choose-a-sesar-code.md).
# Choose a SESAR Code
To register samples, all users must have a SESAR Code.
## Selecting a SESAR Code (IGSN namespace)
SESAR Codes are a tool that uniquely identifies the person or institution that registers the sample, and can be used by researchers to aid in the management of their samples. MySESAR supports multiple SESAR Codes for each user and team. **SESAR Codes begin with 'IE' and are followed by 3 letters and/or numbers of your choosing (IEXXX)**. Common SESAR Codes are initials or abbreviations of a large project.
When you create a SESAR Code, it is important to keep in mind what samples will be registered with that SESAR Code. For example, unique SESAR Codes can be used to represent:
* Personal vs Team samples
* Different projects or grants
* Different field sessions
SESAR Codes belong to the user account or the team that created the code. Permissions can be granted to team members to share sample management (see section below).
## Creating a SESAR Code
1. To create a SESAR Code, navigate to the left hand panel and click 'SESAR Codes'.
2. Click 'Create New Code' on the upper right hand menu.
3. Under the 'Create New SESAR Code' popup, add three alphanumeric digits and click 'Create'.
If the code is already in use, the system will not allow you to create the code and flag it. Please try again until your code is successfully added. Your personal or team code will be displayed in 'SESAR Code' of your personal or team account.
\
**For more information on how to create a new SESAR Code, please see the guide below.**
{% file src="/files/rrZ8oyXwAGPjhkF31wIl" %}
---
# 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/accounts-and-access/choose-a-sesar-code.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.