Trusted Browser Behavior
Use trusted browser behavior without losing sale-quality context, source nuance, or the final number a client will rely on.
Fast read
Use the left sidebar or direct page link named in the guide, then check the visible page title before touching filters, sends, downloads, or billing buttons.
Open the final page, shared link, tracker link, embedded widget, or exported report in the same browser before treating the task as complete.
Copy the URL from the address bar, note the account email in Account Settings, take a screenshot, and include the last button you clicked.
Step-by-step
- Start at /login and enter the exact account email you want to use on this browser.
- If trusted browser behavior shows a verification or approval screen, leave that screen open while you check the matching inbox for the code or approval email.
- Enter the code into the CURVE screen or open the approval link in the same browser session whenever possible.
- After approval, open Account Settings and confirm the signed-in email and session state match the intended account.
- If the wrong account keeps loading, sign out from CURVE, close duplicate CURVE tabs, reopen /login, and start with the correct email again.
- If the expected result does not happen, copy the full URL from the browser address bar, open Account Settings and note the signed-in email, take a screenshot of the current page, and write down the last button or link you clicked.
Mistakes to avoid
Changing filters or modes without checking the final rendered surface.
Assuming a highlighted, shared, or pinned item changed source truth instead of presentation or access.
Frequently asked questions
Start with account, URL, selected mode, filters, building or unit, date range, and recipient context. Most confusion comes from looking at the right data through the wrong workflow state.
Most controls change the view, filter, workflow state, access, or presentation layer. Source sale and unit records remain unchanged unless an admin data-sync or data-correction process explicitly updates them.
Open the final surface the client will see and verify that the key evidence, action, label, or next step is visible without needing you to narrate it separately.
Send the account email, URL, building or unit, saved search or report name, timestamp, screenshot, and the exact action you took immediately before the issue appeared.