Login-walled context capture
Last updated 2026-06-14
Definition
Login-walled context capture reads pages that sit behind a login, but only when you authorize it. Some product detail lives inside an account or a gated docs area that a public crawl never sees. With your permission, Quri captures that context too, so its understanding of your product is not limited to what an anonymous visitor can reach.
How to do this in Quri
- Decide which login-walled area holds product context worth capturing.
- Authorize Quri for that area from the context scan at /app/audit.
- Quri captures the gated pages you allowed, alongside your public crawl.
- Review the captured context and revoke access whenever you want.
Frequently asked
- Does Quri read login-walled pages without my say-so?
- No. Public pages are the default. Login-walled capture happens only on pages you explicitly authorize, never on a gated area you have not allowed.
- Do you store the login-walled pages you read?
- Quri keeps the captured product context scoped to your account, like the rest of your data, and you can revoke access and purge it whenever you choose.