We basically only capture publicly available web pages, so if login is required we cannot make a screenshot of it.
However, sometimes a workaround is possible:
- When you're in control of the server and can whitelist our IP-addresses so that our "screenshot engine" does not require a login.
- With our option to add custom cookie data in Expert mode, from a technical perspective it may work to copy the authentication cookie from your browser session and use this in your screenshot settings to access a page that requires being logged in. However, from a security point of view, we do not recommend this, nor do we provide support for it. But it may work and you're free to try at your own risk.
- For some logins, it works to put the username and password in the URL, like `https://username:firstname.lastname@example.org/`. (Which is not advisable for very sensitive data, since you're sharing the login credentials. But it might be acceptable to use for pages that you only protected so that Google doesn't index them.)