Test pages behind your login
BetaGive Scout a test account so it can sign in and audit the pages only signed-in users see.
Most of a product lives behind its sign-in page. Give Scout a test account, and it signs in and audits those pages too.
Before you begin
- You need the Editor, Admin or Owner role.
- Select the project in the sidebar project switcher.
- Create a test account on your own site first. Flamio only signs in with the login and password you enter — it never creates accounts.
- Use an account whose data you are happy to see in screenshots. Findings show what Scout saw while signed in.
Add a test account to a run
Fill the basics
Open Flamio Scout, enter the Site URL, pick the Screen and set the Research budget. Then open Additional settings.
Let Scout type
Under What can Scout do?, select Interactive. Signing in means filling a form, so a Read-only run cannot use a login: with one, the form reads "Signing in means filling a form — choose Interactive under “What can Scout do?”." and blocks the launch.
Decide on destructive actions
Interactive ticks I own or am authorised to test this site — allow destructive actions. Untick it to keep delete and remove controls blocked. Scout still signs in, fills and submits forms.
Enter the login
Under Site access, enter the test account in Login or email and Password. Fill both or clear both: half a pair reads "Fill both the login and the password (or clear both)." and blocks the launch.
The line under the fields confirms: "Sent encrypted, used only to sign in on this site, and discarded when the run ends."
Launch the run
The folded Additional settings line now ends with Signs in. Click Launch Scout.
Result
Scout signs in with the test account and audits the pages behind your login along with the public ones.
Flamio never stores the login with the run. To Continue or Re-scan a run that signed in, enter the login again in the dialog. See Stop, continue or re-scan a run.
Screenshots can show the account's data