> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/settings/team-access.md).

# Team access

Blotato supports one user per account. Native multi-user and team-member access is not live yet, and there is no firm release date. Today you share access by sharing your login email and the emailed authentication code (steps below). Whoever you share the code with signs in as you, so there are no separate teammate logins, roles, or audit trail.

## Give a teammate access to your account

If you have an assistant or teammate who needs access to Blotato on your behalf:

1. Have them enter your email address when logging in
2. Give them the authentication code sent to your email
3. They complete the login process

This keeps them signed in for awhile.

## Invite an admin to your account

If you want to give someone admin-level access to manage your Blotato account:

1. Have them enter your email address when logging in
2. Give them the authentication code sent to your email
3. They complete the login process

The admin will have full access to your account, including social accounts, posts, and settings.


---

# 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://help.blotato.com/settings/team-access.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.