Site addresses and modes
Register every address the site runs on and choose who can use EkhaneMark there.
A project lists the addresses (origins) its website runs on, such as http://localhost:5173, https://staging.client.com and https://client.com. The widget only works on these. The project key in the script tag is public, so this list is what stops anyone from using your project from another website. Localhost addresses are the exception: they work for your team without being added, and join the list the first time you sign in there.
Modes
| Mode | Use it for | What happens |
|---|---|---|
| On | Staging (and localhost) | Signed-in team members and approved clients. Once signed in, the widget stays on in that browser. |
| Review | The live site | The same people, signed in for one tab only. Visitors never see anything. |
| Off | Pausing EkhaneMark | The widget doesn't start at all on that address. Existing feedback is kept. |
localhost is for your team only
Addresses like localhost, bikalpo.localhost:3001 and 127.0.0.1 only open on your own computer, so the dashboard marks them Team only. Your team doesn't need to add them: run the site, add #ekhanemark to the address and sign in. Clients never get in on them, and never get them in their portal or emails. When you mark a client's feedback done, you pick the staging or live address where they can check the fix. Deploy first, then mark it done.
Same page, different addresses
Feedback is grouped by page path (/pricing, /products/shoes), not by full URL, so a pin left on staging shows on your localhost copy of the same page. Query strings are ignored; hash routes (/#/settings) are kept.