Browser sign-ins
AI signs in to each store's account in turn and runs the same task
One admin console, one account per store or department. Store each login under a name, and AI switches between "Shibuya" and "Shinjuku" while it downloads sales or checks stock, one account after another. Nobody has to re-enter accounts one by one.
Open Samurai AppRequest materials
- How the work was done
Accounts split by store causing headaches like these?#
Signing in again for every store
Even on the same service, each store or department has its own account and there is no combined view. Every day you sign out and type the next ID.
Passing around a list of IDs and passwords
People type from a spreadsheet of IDs and passwords. The more people can see the list, the harder it is to tell where a leak came from.
Automation stops at the first account
Typical automation assumes one login per site. Switching to the second account sends the work back to a person.
Store any number of named logins for the same site#
On the browser sign-ins screen, register a sign-in URL, ID, and password under a name such as "Shibuya". That name is how chat and skills refer to the account. With many stores, paste from a spreadsheet or upload a CSV to register them in bulk.
- Bulk registration takes up to 200 rows at a time. Rows whose name already exists are skipped, not overwritten
- Logins for the same site are grouped, and you can pick the one you use most as the default
- Choose who can use each login: only you, a group, or the whole tenant
Name the account in chat and AI switches and carries on#
Ask "download yesterday's sales for every store" and AI switches accounts by name, repeating the same steps once per store. Each time it signs out of the current account, clears that site's cookies, and signs in again with the next one.
- Accounts switch inside the same browser, without opening a new one
- Save the steps as a skill and they run in the same order every time
- Store a signed-in cookie and an ID and password under the same name, and AI signs in with the ID and password when the cookie expires
AI sees only the account name#
Stored IDs and passwords are used only to fill the sign-in page. AI sees the account name, never the password or cookie values. If an account was renamed and someone asks for the old name, AI stops and lists the names that exist. It never quietly runs as a different account.
- When a site asks for a two-step code, a card appears in the chat, and a person's click fills the code from the password vault
- Storing a login takes one approval. Write actions still need approval per site, as before
- The same logins work in the cloud browser and in your own Chrome
Frequently asked questions#
Can AI use several accounts at the same time?
No. Accounts on the same site are used one at a time, switching in turn. Working through them in order, the same steps repeat for dozens of stores.
Can AI sign in automatically on any site?
On a typical sign-in page with an ID and password, AI fills them in and signs in. Pages whose fields are hard to identify, or sites with unusual sign-in flows, may not work. For those, you can store a signed-in cookie instead.
Does it work with sites that use two-step verification?
Yes. When a code is requested, a card appears in the chat, and a person's click fills the code stored in the password vault. Because a person has to click, unattended scheduled runs cannot pass two-step verification.
Can AI use passwords from the password vault directly?
Copy a vault item to browser sign-ins and it becomes a login AI can use. Passwords left in the vault can be opened only by people, so AI does not use them. Two-step keys are not copied.
Everyday work comes together, connects, and becomes the company's strength.