> 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/using-sesar-teams.md). # Using SESAR Teams SESAR users can now set up a Team to share SESAR Codes and register lab, group, and shared samples. **Note that you can no longer share personal SESAR Codes unless you have assigned or been assigned access prior to migration.** For more information, please refer to the [Shared Permissions section](/for-researchers/accounts-and-access/share-a-code-with-your-lab-group.md). You can toggle between personal and team accounts in the left side panel of MySESAR. Users may have multiple team accounts that they created or are invited to be a part of, all of which will be listed. ### **Creating a New Team** 1. On the left panel, click your name where your personal account is. This will prompt a display of all your workspaces. 2. Click ‘Add Team’ and follow the instructions to create your team. The ‘Team Name’ and ‘Contact Email’ are required. 3. Add team members as needed. All team members invited to join must have their own SESAR account. You can always navigate to ‘Settings’ on the left panel to update your team name, description, contact email, affiliation, or even delete your team as needed under ‘Team Settings’, and also add members and update their permission settings under ‘Team Members’. ### **Setting a Team SESAR Code** You can set a new SESAR Code under ‘SESAR Codes’. For more information please see ‘[Choose a SESAR Code](/for-researchers/accounts-and-access/choose-a-sesar-code.md)'. ### **Invite Team Members** If you are invited to join a team, you will receive an email from . The link on the email will redirect you to the team page where you can accept or decline the invitation. If you miss the email, the team will be listed as part of your accounts on the left panel. ### **Managing Team Members** Once members accept the invitation, you can view the samples under the team. Depending on your ‘Role Level (Team Permission)’ you will have basic access to full access to sample registration and team management as the team admin or owner. #### Available Permissions 1. **Team Owner**: owner of the team, usually original creator or co-PI who has full administrator access to the entire team. 2. **Team Admin**: can view, create, edit, and deactivate samples on all SESAR codes in the team and also manage SESAR Codes, sample groups, members, and permissions. 3. **Read, Create, Edit, Deactivate**: can view, create, edit, and deactivate samples on all SESAR codes and also add and remove samples in sample groups. 4. **Read, Create, Edit**: can view, create, and edit samples on all SESAR codes and add and remove sample groups. 5. **Read, Edit**: can view and edit samples on all SESAR codes and add and remove samples in sample groups. 6. **Read, Create**: can view and create samples on all SESAR codes and add and remove samples to sample groups. 7. **Read Only**: can view all samples, SESAR Codes, and sample groups in a team. If you need to update your permission status, please contact your team owner or administrator to update your access. Multiple users can have the same permission status.
**For more information on how to set up a Team, download our guide below.** {% file src="/files/H4axWXeiaVk5c5jdBlPY" %}

--- # 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/using-sesar-teams.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.