Protected sign-in overview
Understand the difference between account login, email verification, and trusted-device approval.
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
- Sign in with the account email first. Email verification proves the inbox, while device approval proves the browser/device is trusted.
- If CURVE shows a device approval screen, leave that tab open and check the same account inbox for the approval message or code.
- Enter the code in the approval screen or click the approval link from the same browser whenever possible.
- After approval, open Account Settings and confirm the signed-in email is the account you meant to use.
- If CURVE keeps returning to a different account, sign out, close duplicate CURVE tabs, reopen /login, and start again with the correct email.
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.