> For the complete documentation index, see [llms.txt](https://starbeam-one.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://starbeam-one.gitbook.io/home/common-tasks/attach-another-login-identity-to-your-account.md).

# Attach Another Login Identity to Your Account

So you signed in with your Twitter account, but you also want to log in with Google.  How do you do this?

1. **Do Not Sign Out**.  Whatever you do, *do not sign out of your account*.  This is done by pressing a button labeled `Sign Out` somewhere (usually on the navigation menu).  When you sign out and sign back in with another identity, it creates a brand new user account in our system and a bit of an administrative headache for us to resolve.  We are actively addressing this process and hope to improve this for a future version.
2. Visit your account security: [https://starbeam.one/profile/security](https://alpha.starbeam.one/profile/security)\
    ![](/files/tucmuseVVrZILKb7qy2z)
3. Select the type of Authenticator you'd like\
   ![](/files/pHzcCBWUCGPs1jWo2oo6)
   1. **Public**: Preferred for artists who want to publish under a publicly-verifiable identity
   2. **Personal**: Preferred for collectors or those who want to add security to their account
4. Select the authenticator.  This starts the process of signing in with the authenticator, and on successful login will attach it to your current user account.\
   ![](/files/ecRsgWmpfHwzDyv4hwtL)

### But Why?

Adding an additional authenticator helps secure your account, especially for artists.  For example, if you are an artist using your Twitter identity to publish your works, and your Twitter account gets banned for whatever reason, what happens to your starbeam.one account?  Well, you can no longer log into it.  This is a bit of a problem.  So, having another method to sign in is very much preferred and recommended.

### Recommended Configuration

It might seem you want to connect all your known identities to your account.  This is not recommended.  Why?  The more identities you attach, the more surface area a malicious actor has to compromise your account.  Keep in mind that a malicious actor has to gain access to only one of your identities to access your entire account.  If you attach 8 different identities, they have 8 different paths to get there.  If there are only two identities, then they have less surface area to utilize for their approach.

That stated the recommended configuration is:

1. One public authenticator
2. One personal authenticator
3. Enable Two-factor authentication: \
   [https://starbeam.one/profile/security/multifactor](https://alpha.starbeam.one/profile/security/multifactor)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://starbeam-one.gitbook.io/home/common-tasks/attach-another-login-identity-to-your-account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.