Website connections
Sign in to a website once, and the chat's browser starts signed in every time it uses the site.
Some tools have no API, or the work only happens in a browser. A website connection keeps a signed-in session for a site so the model can work inside it without asking you to log in each time. Pad holds the session, and any saved login, encrypted; the browser provider never does.
Connecting a website
From Connections choose Add connection, then Connect a website. Enter the site's address and, if it differs, its sign-in page. Website connections use personal accounts by default, so each person signs in as themselves; choose a shared account for a team login a whole group should use.
Signing in
Open the connection's Browser tab and choose Sign in. A real browser opens on the site's sign-in page. Sign in as you normally would, two-factor prompts included, and press Done. Pad keeps the signed-in session, not what you typed, and nothing from a sign-in is ever recorded.
The same flow works from a link: a single-use link, valid for fifteen minutes, that you can open on your phone. Sign in there, press Done, and your other devices update on their own.
Saving your login
After signing in, Pad offers to save your password, and an authenticator key if the site asks for one-time codes, so the browser can sign in again without you when the session expires. This is optional. A saved login is typed into the site's own sign-in page by Pad and is never shown to the model or to anyone.
The authenticator key is the setup key the site shows when you turn on its authenticator app (the text offered beside the QR code, a long string of letters and digits) or the otpauth link behind that code; Pad computes each one-time code from it. In a password manager it is the value of the item's one-time password field when you edit the item. The six-digit code itself expires in seconds and is not the key, and 1Password's secret reference (an op:// address) is not either; the form says so if you paste one.
Signing in with Google, Microsoft, or another connection
Many sites sign in through an identity provider instead of a password of their own. When you connect such a site, choose Single sign-on as its sign-in method and pick the connection it signs in with, or create one on the spot from the Google, Microsoft, GitHub, Apple, or Okta presets. The sign-in connection is an ordinary website connection: sign in to it once on its Browser tab, save its login there if you like, and every site linked to it uses that sign-in from then on. Update the login in one place and every linked site follows.
A linked site keeps no saved login of its own. The browser opens the site already signed in to the provider, so the site's "Sign in with Google" button is one click, and the model can press it and fill the provider's saved login when a session expires. The link is a choice of the people who manage the site; both connections must use the same account mode, and a site can use another site as its sign-in connection only when you have access to both.
A sign-in connection's page lists the sites that use it. Archiving it leaves those sites without a sign-in method until a manager chooses another, and the archive confirmation names them.
What chats get
A chat's browser starts signed in to every website connection you hold among the chat's sources. A signed-in session is yours alone: a teammate's turn in the same chat uses their own sessions, never yours.
Staying signed in
The Browser tab shows whether you are signed in, signed out, or whether a saved login was rejected. Sign in again from the same tab when a site signs you out. When the model signs in with your saved login during a chat, including through an authenticator code or a sign-in connection, that session is kept the same way. A session unused for 45 days is dropped. Sign out from the tab at any time; leaving the organization or archiving the connection removes every session and saved login.
Settings for a website
On the connection's General tab: Sensitive turns off recordings and screenshots for the site and limits watching to the person driving. Approve actions asks before every click or submit on the site. Enhanced stealth uses extra measures on sites that block automated browsers.