Logins
Saved sign-ins for websites, SSH, SFTP, FTP and databases that bots use without seeing the password.
Settings → Logins keeps sign-ins that bots use for you. Passwords, keys and 2FA secrets are stored encrypted on the host and never shown to any model.
| Kind | What bots can do |
|---|---|
| Website | Sign in through the built-in browser, including 6-digit 2FA codes if you add the authenticator setup key. |
| SSH | Run commands and move files on a Linux or Windows server. Password or private key (with passphrase). |
| SFTP | Browse, download and upload files over SSH. |
| FTP | Browse, download and upload files. Uses TLS (FTPS) unless you turn it off for servers that don't support it. |
| MySQL / PostgreSQL | Run queries. Read-only unless you tick Allow changes. |
Who can use a login
Tick which bots may use each login, here or in the bot editor. Bots know the other logins exist (by name, never their details) and can ask for one in a chat; you approve with a card. Test checks a login from where the bots run.
How a bot uses it
- Website sign-ins are typed as placeholders that InkBot replaces with the real values in the browser.
- SSH, SFTP, FTP and database logins are used through InkBot's tools:
ssh_run,remote_list,remote_upload,remote_downloadandsql_query.
Logins are per host: logins on a server are used by that server's bots, from that server.