Settings

1Purpose #

The application runs in your browser but keeps none of your data there: every company, voucher, report and master is fetched from an InvoiceNET server. This screen is where you say which server, and it is normally set once, when the application is first opened on a machine.

• The address you save is used by every request the application makes — signing in, listing companies, opening a master, saving a voucher, printing a report.
• It belongs to this browser on this machine , not to your user account. Change it and you change it for everybody who signs in on this browser; sign in on another machine and that machine keeps its own address.
• Nothing here is sent to or stored on a server, so there is nothing to approve, nothing to audit and nothing that can go wrong for other people because of what you type.
• Most sites never touch it. Change it only if you have been told to — a new server address, an on-premises installation, or a test system.

2Setting the address, step by step #

1. Normally you never need this screen: the address lives in the site's appsettings.json , and when the site forbids browser overrides (the production default) the box here is read-only and the notice above it says so — edit the file instead and reload the page.
2. Where the site DOES allow the override: read the Configured URL line under the box first. If the box already shows that address and nothing works, the address is not your problem — the server or the network is.
3. Type the address you were given into Application Url , complete with http:// or https:// . Copy and paste it if you can; a single wrong character is invisible and fatal.
4. To go back to the configured address, clear the box completely rather than trying to retype it — an empty box saves the configured value.
5. Click Save . There is no confirmation and no success message: a save that worked simply returns you to the sign-in screen.
6. Sign in. That is the test — the first thing that actually calls the address. If it fails, come back here and check the address again.
7. Back leaves without saving. Anything you typed is discarded.

3Field details #

• Application Url — the only editable field on the screen, and editable ONLY where the site's appsettings.json allows the browser override; otherwise it is read-only with the notice above saying so. Spaces at either end are removed; the trailing slash is added for you if you leave it off. Nothing else is corrected or checked. An empty box is saved as the configured address, so the box can never be left blank.
• Configured URL — a fixed line of text, not a control and not a link. It is the address the site's appsettings.json supplies (or the built-in fallback when that file names none), and it is what an empty box falls back to. It never changes from this screen, whatever you save.
• Save — writes the address, applies it to the session at once, and returns you to the screen you came from. While it is working the button reads Saving... and both buttons are disabled.
• Back — returns without writing anything.
• The red message — appears only when the browser refused to store the value at all (private-browsing restrictions, storage disabled or full). It is never a comment on the address you typed: no message here means saved, not correct.

4Rules and integrity #

• The address is never validated. Nothing checks that it is a web address, and nothing calls it to see whether a server answers. A typed mistake saves silently and looks exactly like a success.
• A wrong address disables the whole application , because there is nothing left to talk to. Signing in fails with a network or address error rather than "wrong password" — which is the tell.
• You are never locked out. This page opens without signing in, at its typed address — and when the override is off, the browser cannot hold a wrong address at all: the site's appsettings.json value always wins. Clearing the site's browsing data discards any stored override, but also forgets the remembered login name and password.
• The change applies immediately to the session you are in — no reload, no sign-out. It also survives closing the browser, because it is stored, not merely remembered.
• Http and https must match the page. If the application itself was opened over https:// , an address beginning http:// is blocked by the browser before it ever leaves the machine. The company-selection screen recognises this and says so in as many words instead of showing an empty list; the fix is an https:// address here.
• It is a browser setting, not a user setting. Nobody's permissions are involved: anyone who can reach the sign-in page can change it, and it changes for everyone using that browser. On a shared machine, treat it as you would any other shared preference.
• Nothing is written to any database , so there is no history of who changed it and no server-side copy to fall back on.

5Why nothing works after a change #

• Sign-in reports a network or address error. The address is wrong or the server is not reachable from here. Compare it character by character with the one you were given.
• Sign-in says the user was not found. The address is fine and reached a server — this is an account problem, not a settings problem.
• The company list is empty and the screen mentions mixed content. The page is on https:// and the address on http:// . Use an https:// address.
• It works on one machine but not another. Expected: the address is per browser. Set it on each machine, and check the browser is not in a private window, where the value is forgotten when the window closes.
• The box comes back empty or showing the old value. The browser is blocking storage for this site; the red message on save says the same thing.

6If something does not work #