Screenshots of Pages Behind a Login
Capture the logged-in pages of your SaaS app for your help docs and keep them current. Save a test account once, and captures sign in when they need to, on a schedule or after each deploy.
The problem
The screens help articles show most, like settings, billing and dashboards, sit behind a login. Capturing them needs a signed-in browser, so teams retake them by hand after every release, or keep scripts that log in first and break when the login page changes.
How ScreenshotAgent solves it
Add a login URL, username and password under Authentication on a project, or with Page needs a login on one screenshot. The username and password are stored encrypted and kept out of capture logs. The capture agent signs in, captures the page and keeps the project's browser session for the next run. A recapture that replays its saved steps and lands on the sign-in page signs in again and reopens the page. If a page still asks to sign in, the capture says so: "The page asked us to sign in before showing its content."
Example: the billing page of your app
In the project settings, under Authentication, add a test account:
The help article embeds the screenshot's permanent URL and shows the current billing page after every recapture.
> Login URL: https://app.example.com/login Username: docs-demo@example.com Password: (stored encrypted)
- 1.Add a screenshot of https://app.example.com/settings/billing to the project.
- 2.The capture agent opens the login page, signs in with the test account, then captures the billing page.
- 3.The browser session is kept for the next capture of the project.
- 4.Set the screenshot to recapture weekly, or call the Recapture API after each deploy.
Expected outcomes
- One saved login covers every screenshot and view in a project, and a screenshot can have its own.
- Recaptures run daily, weekly or monthly, or from your deploy pipeline with the Recapture API.
- Customer data is hidden by CSS selector, or blurred by an AI annotation, on every capture.
- Permanent image URLs, so help centers and docs that load images from their URL show the new capture.
- In ChatGPT or Claude, ask for a screenshot of a page in a project with a saved login. The assistant is told never to ask for your password in chat: the login is saved in the app.
FAQ
- Which logins work?
- A login page with a username or email and a password, including forms that ask for the username first. For flows with extra steps, like a "Sign in with Google" button followed by an email and password, describe the steps in the agent instructions.
- What about two-factor authentication, magic links or captchas?
- A login that needs a fresh one-time code, a link from an email, or a captcha at every sign-in cannot be automated: there is no way to give the capture a new code, and the agent never solves captchas. Use a test or demo account that signs in with a password.
- How are the credentials stored?
- The username and password are encrypted at rest, decrypted only when a capture needs to sign in, and kept out of capture logs. The login URL is stored as plain text. Use a dedicated demo account rather than a real person's account.
- What happens when the session expires?
- The browser session is kept between captures of a project. A recapture that replays its saved steps signs in again when it lands on the sign-in page. Other captures are done by the AI agent, which is given the login and signs in as part of the capture.
- Can signing in trigger security alerts?
- Some apps send an alert or lock an account after many sign-ins from new browsers. Keeping the session between captures keeps sign-ins rare, and a dedicated demo account keeps any alert away from a real person.
Related features
- AI AnnotationsCircle, highlight, or point at the part of a screenshot that matters. AI finds it, we draw on top, and your screenshot's pixels are never changed.
- Screenshots of Modals, Dropdowns and TabsAutomatically capture the open modal, the expanded dropdown and each tab of your web app for your documentation, and recapture them when your UI changes. Describe the clicks in plain words. No Playwright scripts to write or maintain.
- Searchable Screenshot LibraryEvery screen of your product that you have captured, in one library the whole team can search by meaning, not just keywords. Find a screen by what it shows, kept current on a schedule or after each deploy, with no extra cost per seat.
Automate this workflow in your team
Start a free trial and connect your first project to see ScreenshotAgent capture and keep pages fresh.