How the roll-up gate works

How the Logged In Is Not Allowed gate works

This tool grades each route on whether being signed in is doing a job only a permission check can do. It reads 10 routes and rolls them into one verdict — the worst, never the average — then a gate that can only make it worse.

The 10 routes

01R-01 · Open the dashboardreaches only this person's own dataMEMBERSHIP IS ENOUGH

02R-02 · Download an invoice PDFchecks the record belongs to the callerAUTHORIZED

03R-03 · View a customer orderno signed-in check at allNOBODY IS CHECKING

04R-04 · Edit a saved documentsigned in, but no ownership checkLOGGED-IN ONLY

05R-05 · Delete a saved documentsigned in + countable id → gate firedNOBODY IS CHECKING

06R-06 · Open a saved documentchecks the record belongs to the callerAUTHORIZED

07R-07 · Submit feedbacknever reaches another person's recordMEMBERSHIP IS ENOUGH

08R-08 · Admin list of all usersownership check could not be foundLOGGED-IN ONLY

09R-09 · Change account emailchecks the record belongs to the callerAUTHORIZED

10R-10 · Read the team directoryfix firstnot found → noneNOBODY IS CHECKING

PERMISSIONS HOLD

every route that can reach someone else checks ownership

SIGNED IN IS DOING TOO MUCH

a route stops at signed-in on someone else's record

ANYONE CAN WALK IN

a route checks nothing, or its ids can be counted through

Enumeration · worsen-only

A signed-in check on a route whose record id can be counted through is not a permission check. Signing up is free, so the account requirement buys nothing — the route drops straight to NOBODY IS CHECKING however carefully the login was built. An observation you could not find resolves to the unsafe side.

ANYONE CAN WALK IN

Why: Three of ten routes check nothing that holds. One of them looked fine — it requires an account, but takes the document id from the request as a number anyone can count through, so the gate fired and dropped it to the bottom. Two more stop at signed-in on records that belong to other people. Five routes are genuinely fine and never count against you. 3 of 10 check nothing · 1 gate fired · worst-not-average.

Fix firstR-10, read the team directory — whether it checks for a signed-in caller could not be found, so it scores as no check at all

No single route is the crisis — the clustering is. The roll-up takes the worst, the gate escalates when trouble compounds, and it names the one thing to fix first. Grades how routes are built, never a person. Not a scanner or a penetration test — it reads back what you tell it, using rules you can see.

RedHub AIthe AI that tells you when to doubt it redhub.ai/quick-kits/logged-in-is-not-allowed