Site rules
Tell Regress in your own words what it must leave alone, what matters most and what it should know about your site.
Write them in your own words
Open Project settings → Site rules and write what you would tell a new colleague, for example “Don't touch the subscriptions page, that can't be undone. Checkout matters more than anything. We call the basket a bag.” Regress turns it into rules and shows what each one would do before you save. Don't put passwords there: sign-in details go in Sign-in settings.
- Leave alone
- Something Regress must never do or touch, like a subscriptions page or a button that creates tickets. Every browser Regress runs on your site follows it, while learning and in scans.
- Matters most
- The part of your site Regress explores first and writes flows for ahead of anything else.
- Good to know
- Something Regress keeps in mind while it explores and writes flows, like the words you use or products that come and go.
- Doesn't count
- Page changes that mention it are no longer changes to tell you about. Regress still checks those pages, and flows still test everything.
Once Regress has learned your site, it asks on the overview whether there is anything it should know, and keeps your answers as site rules. If it stopped before saving something while exploring, it lists what it would have saved so you can leave any of it alone.
Rules for every site or one client
In Settings → Site rules you can write rules once for every project, or for all of one client's sites. Each project shows them in its own Site rules, and new projects get them too.
What Regress never does, rules or not
- Never pays, places an order or confirms a purchase or plan change
- Never signs up for an account, unless you asked it to on a site you have verified as yours
- Never sends contact, newsletter or invite forms
- Never signs out
- Changes and deletes only records it created itself, and only once you allow it
- Never follows links off your site