> ## Documentation Index
> Fetch the complete documentation index at: https://www.tella.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Let Auto Capture sign in to your product

> Save a login under Settings → Credentials, typed in or picked from 1Password, so Auto Capture can record pages behind a sign-in. Passwords are encrypted and never shown to the AI.

> [!NOTE]
>
> Auto Capture is in **beta**. We'd love your feedback: tell us what works, what doesn't and what you'd like it to film next by emailing [support@tella.com](mailto:support@tella.com).

Save a login under **Settings** → **Credentials** so [Auto Capture](https://www.tella.com/docs/help/integrations/auto-capture.md) can record pages behind a sign-in. You can type in an email and password, or pick a login from 1Password, which also lets Auto Capture get past two-factor authentication on its own. Passwords are encrypted before they're stored, never shown to the AI, and masked in recordings.

[https://www.tella.com/video/vid\_cmvsqdsmi000108l20p4rgj1n/embed?b=0\&title=0\&a=1\&loop=0\&t=0\&muted=0\&wt=0](https://www.tella.com/video/vid_cmvsqdsmi000108l20p4rgj1n/embed?b=0\&title=0\&a=1\&loop=0\&t=0\&muted=0\&wt=0)

## Open the Credentials settings

1. Click your **workspace name** in the top-left corner and choose **Settings**.
2. Click **Credentials**, under **Other** in the settings sidebar.

The page lists every login your captures can use under **Sign-in credentials**, with a **1Password** row below it.

> [!TIP]
>
> Use a demo or test account, not your own. The AI sees everything the account can see once it's signed in, and anything on screen can end up in the recording.

## Add a login by typing it in

1. Click **Add credential**, then choose **Enter manually** at the top of the window.
2. **Sign-in page:** the site where the email and password are typed, such as `app.example.com`. If your product signs in through Google or another provider, enter that site instead, such as `accounts.google.com`.
3. **Use on:** the sites you film with this login; a capture that starts on one of them signs in with it. It fills in from the sign-in page; add more by typing each site and pressing **Enter**. Subdomains are included, so `example.com` also covers `app.example.com`, and `www.example.com` and `example.com` count as the same site.
4. **Name:** what you and the AI call this login, such as "Demo account". It's named after the sign-in page until you type your own. When more than one login matches a page, the AI picks one by name, so make it descriptive.
5. **Email** and **Password:** the account's sign-in details.
6. If you're a workspace owner, choose **Who can use it** (see [Personal and workspace logins](#personal-and-workspace-logins)).
7. Click **Add credential**.

Tella confirms which sites now sign in with the login. Once saved, the password can't be viewed again, by you or by Tella.

## Example: a product that signs in with Google

Say your app is at `app.example.com` and its login page has a **Continue with Google** button:

* **Sign-in page:** `accounts.google.com`
* **Use on:** `app.example.com`

A capture that starts on `app.example.com` can use this login, and the password is only ever typed on `accounts.google.com`. Google accounts usually need a second step; see [Sign in with two-factor authentication](#sign-in-with-two-factor-authentication).

## Connect 1Password to Auto Capture

With 1Password connected, you pick logins from a vault instead of copying them into Tella. Tella reads the item each time a capture signs in, so a changed password works on the next capture, and it never keeps what's in the item.

Tella reads 1Password through a **service account**, which can only see the vaults you give it:

1. In **Settings** → **Credentials**, click **Connect** on the **1Password** row. (Or click **Add credential**: with no connection yet, the **1Password** tab offers to connect.)
2. Click **Create a service account** to open 1Password's developer tools, and create one.
3. Give it read access to a shared vault that holds your demo logins. 1Password doesn't let service accounts read your **Private** vault.
4. Copy the token 1Password shows you. It starts with `ops_`, and 1Password only shows it once.
5. Back in Tella, give the connection a **Name** (such as "Work 1Password") and paste the token into **Service account token**.
6. If you're a workspace owner, choose **Who can use it**.
7. Click **Connect**.

The **1Password** row then shows your connections and the vaults each can see. Click **Manage** to add another connection or disconnect one.

## Add a login from 1Password

1. Click **Add credential**. The window opens on the **1Password** tab.
2. Under **1Password login**, search by the item's title and pick it.
3. Tella checks the item and shows whether it has a **Username**, a **Password** and a **One-time password**.
4. Fill in **Name**, **Sign-in page** and **Use on** as for a typed-in login.
5. Click **Add credential**.

Only **Login** items are listed. The username and password must be in the item's own **username** and **password** fields, not in custom fields. If Tella says the item needs a username and a password, fill those fields in 1Password and pick the item again.

## Sign in with two-factor authentication

If your product asks for a code after the password, there are two ways to give Auto Capture one:

* **From 1Password, automatically.** Add a one-time password (TOTP) to the login item in 1Password, then add the login to Tella from 1Password. Tella generates each code on its own servers whenever a capture needs one, for personal and workspace logins alike. The secret never reaches the browser.
* **By you, when it asks.** For codes sent by email or text message, or a typed-in login, the capture pauses and sends you a link to a Tella page where you type the code. This only works for logins that are yours (**Only you**). See [Enter a sign-in code for Auto Capture](https://www.tella.com/docs/help/integrations/auto-capture.md#enter-a-sign-in-code-for-auto-capture).

Auto Capture can't use a security key or a passkey, including a passkey on your phone. When asked for one, the capture picks another option, such as an authenticator app code, so the account needs one of the methods above set up.

Tella never asks for sign-in codes by email. If you receive an email asking for one, don't enter it.

## Personal and workspace logins

[https://www.tella.com/video/vid\_cmw0zw77x004t07il9j009pa7/embed?b=0\&title=0\&a=1\&loop=0\&t=0\&muted=0\&wt=0](https://www.tella.com/video/vid_cmw0zw77x004t07il9j009pa7/embed?b=0\&title=0\&a=1\&loop=0\&t=0\&muted=0\&wt=0)

Every login and 1Password connection belongs either to you or to the workspace:

* **Only you:** only captures you start can use it. Anyone in the workspace can add one. It's deleted if you leave the workspace or delete your account.
* **Everyone in the workspace:** captures started by any member can use it, and it's marked **Workspace** in the list. Only workspace owners can add, change or remove one, and it stays when the person who added it leaves.

Logins you add from a 1Password connection take that connection's scope: a workspace connection gives workspace logins, and your own connection gives logins only you use. If your workspace already has a shared connection, its logins are in your list; connect your own 1Password to add logins only you use.

Workspace logins can't ask for a sign-in code by email or text message, because the code would go to a shared inbox. Use 1Password's one-time password for those.

## Edit or remove a saved login

[https://www.tella.com/video/vid\_cmvwcrg8t00fq08js35vncqkt/embed?b=0\&title=0\&a=1\&loop=0\&t=0\&muted=0\&wt=0](https://www.tella.com/video/vid_cmvwcrg8t00fq08js35vncqkt/embed?b=0\&title=0\&a=1\&loop=0\&t=0\&muted=0\&wt=0)

Each login in the list shows its sites and when it was added or last edited. Captures pick a login by site alone, so the list warns you if a login's name mentions an environment none of its sites has, such as "Sandbox" on a login used only on a staging site.

Click a login in the list, or open its **…** menu and choose **Edit**, to change its name or sites. Changing a saved login's **Sign-in page** doesn't change its **Use on** sites. For a typed-in login, the email and password show as **Unchanged**: leave both blank to keep them, or type new ones to replace them.

To delete a login, open its **…** menu and choose **Remove**. It's deleted straight away and no new capture can use it; a capture already running can finish with it. Disconnecting a 1Password connection removes every login added from it.

## How Auto Capture keeps your sign-in details safe

* Passwords and 1Password tokens are encrypted before they're stored, and no Tella employee can decrypt them.
* The AI that drives the browser never receives your password. It sees the email address and the pages it visits, including everything shown after it signs in.
* A password is only typed on the sites you listed for that login.
* Each capture runs in its own browser, which is deleted when the capture ends.
* Password fields are masked in recordings. If a recording shows the sign-in, your email address appears wherever your product displays it; trim that part in the editor.

For more, see [Is Auto Capture safe to give my sign-in details?](https://www.tella.com/docs/help/integrations/auto-capture-security.md) and [How Auto Capture protects your sign-in details](https://www.tella.com/legal/auto-capture-security).


## Related topics

- [Get started with Auto Capture](https://www.tella.com/docs/help/integrations/auto-capture-get-started.md)
- [Make videos for your help articles with Auto Capture](https://www.tella.com/docs/help/integrations/auto-capture-help-center-videos.md)
- [Record with AI agents using Auto Capture](https://www.tella.com/docs/help/integrations/auto-capture.md)
- [Let Auto Capture past your firewall or bot protection](https://www.tella.com/docs/help/integrations/auto-capture-site-access.md)
- [Is Auto Capture safe to give my sign-in details?](https://www.tella.com/docs/help/integrations/auto-capture-security.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.