> 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/readme.md).

# Create a SESAR Account

Here is the workflow for creating an individual researcher and Team account.

## Setting up a SESAR User Account

### Individual Researcher

1. Create an [ORCiD](https://orcid.org/) Account. 
2. Login to [MySESAR](https://app.geosamples.org/index.php) with your ORCiD.
3. Follow the instructions to complete your MySESAR Account. Users must set up their SESAR account before proceeding to registrations. 
4. Create a [SESAR Code](/api/sesar-codes.md).

### Using SESAR with a Team

If you are the lead of a research team and want to share sample registration, metadata editing, and other tasks with your staff or colleagues, you can do so through the following steps to set up a Team. See also [**Using SESAR Teams.**](#using-sesar-with-a-team)

#### Team Lead or PI

1. Create an [ORCiD](https://orcid.org/) account if they do not have one already.
2. Login to [MySESAR](https://app.geosamples.org/index.php) with their ORCiD and create a personal account. Users must set up their SESAR account before proceeding to registrations. 
3. Create a new Team under Workspace.
4. Create a [SESAR Code](/for-researchers/accounts-and-access/choose-a-sesar-code.md) for the Team under 'SESAR Codes'.
5. Invite members to your Team under Settings: Team Members using their ORCID or searching by name.
6. Set permission levels for team members after invitation is accepted.

#### All Other Team Members

1. Create an [ORCiD](https://orcid.org/) account if they do not have one already.
2. Login to [MySESAR](https://app.geosamples.org/index.php) with their ORCiD and create personal accounts. Users must set up their SESAR account before proceeding to registrations. 
3. Accept the Team Invitation.
4. Create a personal SESAR code only if they plan on registering personal samples.

Once team members have access to the Team group SESAR code, samples can be registered for the lab group from each individual’s MySESAR account. If the PI of the Team changes, the owner of the SESAR code can be updated. See more information under [Using SESAR Teams](/for-researchers/accounts-and-access/using-sesar-teams.md). 


---

# 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/readme.md?ask=<question>&goal=<user_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.