Skip to content
HNROS Help Center
English
Start free
Contents1. What do the three layers do?2. The whole story of one document: the Document File3. Security gates — six stoppers3.5 The administrator decision now comes from the server3.6 What a permission refusal tells you4. How to open a gate5. Anomalies — not an accusation, a place to look6. A ten-minute weekly routine7. Four new gates (2026-09): single signature, automatic period lock, CoC lot requirement, automatic lot pattern8. Role templates and permissions taking effect on open sessions immediately9. Login errors come in three classes: identity, throttle, load10. Staff portal: login throttle and unlocking11. Where to look when a message mentions a “security gate”Session life cycleUploaded file typesSign-in and password error codes (integration)The period lock is a single gateSecurity classification and need-to-know

Audit Trail, Security Gates and Anomalies

This guide covers three separate layers of defence. In short: the first one records, the second stops, the third shows. Each is useful on its own, but their real strength appears when they are used together.

⏱ How long does it take?

Sections 1–2 are what every manager should read: ten minutes. If you are going to switch gates on, read sections 3–4 too.

1. What do the three layers do?

What separates an accident from an abuse is intent, and no software can see intent. That is why the system answers three separate questions separately:

Layer The question it answers Where
1 · Audit trail Who did this, when, and from which machine? Management → Audit → Search
2 · Security gates Should this have been possible at all? Management → Audit → Security gates
3 · Anomalies What looks normal on its own but is not? Management → Audit → Anomalies

2. The whole story of one document: the Document File

On invoice, order, quote, delivery note, voucher and cheque-bordereau screens — if you are signed in as a manager — you will see a Document File button. One click opens that document's entire story:

⚠ Numbers get reused

HNR can hand out a deleted document's number again. That is why the Document File matches the trail not by number alone but by the document's own timestamp. Distant matches are shown in a separate number history block — do not confuse the two.

3. Security gates — six stoppers

Every gate is off by default. Nothing stops by itself for a company upgrading to a new version; switching a gate on is a deliberate decision. Every gate has an escape, and it is always printed on screen — a gate whose escape is invisible gets switched off wholesale at the first complaint.

Gate What it does / why it exists Escape
Period lock Prevents adding documents to a month whose tax return has already been filed. A manager can pass (this too can be switched off).
Delete threshold Let small mistakes be fixed; make large documents pass a second pair of eyes. A manager can delete any amount.
Voucher ceiling Large cash movements should not happen on a single signature. A manager writes without limit.
Scrap tolerance Scrap is the easiest place to hide missing goods. An explicit approval is added to the confirmation; the approver is recorded.
Cost lock Typing a cost by hand is the shortest route to making the profit report say what you want. It can be set to manager-only; in the closed mode only the calculated cost counts.
New account approval An invoice to a made-up customer is a receivable that will never be collected. Editing existing accounts is always free.
💡 Advice for a small business

In a one-person business, switch nothing on; "no gate is open" on the screen is not a shortcoming. When a second employee joins, open the period lock first, then the delete threshold. The others go on only if that line of work truly needs them.

3.5 The administrator decision now comes from the server

The question of whether a user is a system administrator used to have two possible answers: the server's answer and the screen's own interpretation. Because both sides read the same permission bits separately, they could — rarely — diverge: the button showed, the action was refused. Now there is a single answer: as you sign in, the server settles "is this user an administrator" itself and states the verdict to the program explicitly. The screen reads that verdict and does not interpret anything on its own.

🔑 What changed in practice?
  • Consistency: What you see and what you can do no longer diverge. If you can see a button, the server also counts you as entitled to that job.
  • Immediate effect: When your administrator changes your rights, signing out and in once is enough; the program refreshes the verdict from the server at startup.
  • What has not changed: Visibility is still only decoration. The real gate is on the server — hiding a button is not a permission; removing a permission is.

3.6 What a permission refusal tells you

When an action is refused the program no longer just says "you are not authorised"; it names the permission that is required. That lets you go to your administrator with "could you turn this permission on" instead of "something is not working" — and the fix takes minutes. The message always follows the same shape:

The message you see What actually happened What to do
"This action requires the '…' permission or system administrator rights." Your session is valid but the permission bit for that job is off Tell your administrator the name inside the quotes — it is enabled from Settings › Users
"This action requires system administrator rights." This job is not gated by a bit but reserved for administrators (user management, HR, quality, warehouse definitions…) Hand the job to an administrator; no partial permission opens it
"A session is required: … you must be signed in to WebOS." Not a permission problem: your session has expired or was never opened Sign in again; nothing is lost, retry the action
💬 If you say "I can see the button but it does not work"

Instead of refreshing the screen, read the message and pass it on verbatim. The permission name inside it is the one clue your administrator can find without searching. If you are on an old session (the program has been open for days) signing out and in once may also be needed — on sign-in the program takes the administrator verdict from the server again.

4. How to open a gate

  1. Open the Management window → Audit tab → Security gates.
  2. Read the gate's description and its Escape line. If you cannot explain the escape to your team, do not open that gate.
  3. Enter the value (a date, a number or a choice) and press Apply. An open gate turns amber and the header says "1 gate open".
  4. If you change your mind, Close returns the setting to its default; no record changes, only the gate closes.
⚠ A typo will not stay silent

The system only accepts setting names it knows. A misspelled setting would silently do nothing while the company believes the gate is on — so an unknown name is rejected and the valid names are listed.

5. Anomalies — not an accusation, a place to look

Deleting an invoice is normal. Issuing a new invoice for the same account on the same day for a similar amount is normal too. The two happening back to back is not. This screen shows exactly that class of event — four views:

⚠ A count is not a finding

The numbers on this screen count rows to look at. A non-zero count does not mean there is a problem, and a zero does not prove everything is fine. Every row may have a perfectly good explanation — a wrong invoice was corrected, two branches bought the same item, a subscription costs the same every month.

6. A ten-minute weekly routine

  1. Open the Anomalies tab and look at the four badge counts. Any jump compared with last week?
  2. In same-day delete-and-rewrite, open the rows where "same person = yes" and the difference is negative. Read the story with the Document File button.
  3. In duplicate purchases, look only at rows where "document no is the same"; the rest is usually regular buying.
  4. If you find something, ask the person involved — the system does not judge, you do.
  5. If you must send the list to your accountant, use the CSV button; the "this is not an accusation" note travels with the file.

7. Four new gates (2026-09): single signature, automatic period lock, CoC lot requirement, automatic lot pattern

You will see four new rows on the same screen (Management › Audit › Security gates). The rule is unchanged: all off by default, each with an escape and a trace, changed only by the system administrator.

Gate What it does / why it exists Value, escape and trace
Single signature (depo.dort_goz_tek_imza) Whoever opens a transfer instruction cannot approve it (four eyes). With a single manager in the company this rule deadlocks work. With the gate on, that lone manager may approve his own instruction. kapali | acik. If another manager exists the setting is NOT applied (they are the second signature). When applied, a "TEK_IMZA" trace in the notes plus a separate Audit-trail row.
Automatic period lock (mali.donem_kilidi_otomatik) On day N of every month the previous month locks by itself; no more "we forgot to set the lock" after the tax return. 0 = off, 1–28 = day of month. The lock date written is the 1st of the month (that day open, earlier closed). A lock moved forward by hand is never pulled back. Every run posts an announcement to managers + an audit record; manual rollback: mali.donem_kilidi.
CoC lot requirement (kalite.coc_lot_zorunlu) On a card where a certificate is mandatory, a CoC check without a lot number gives a "general" answer. With the gate on, a lotless query is refused. kapali | acik. Off: the response carries a "general check — not lot-based" warning; on: LOT_GEREKLI. Details: Quality guide.
Automatic lot pattern (depo.otomatik_lot_kalibi) When a lot-tracked card is received on a purchase invoice without a lot number, the program opens a lot with this pattern. Text, at most 60 characters; placeholders {belgeNo} {sira} {kod} {tarih} {depo}; {belgeNo} is mandatory. Default "{belgeNo}-{sira}". Details: Warehouse guide.

8. Role templates and permissions taking effect on open sessions immediately

When creating a user you now pick a role template (sales, purchasing, warehouse, production, quality, finance, accounting, HR, planning, management) — the era of "clone the warehouse clerk, then flip bits one by one" is over. How to use it is in the Settings guide. Two rules matter for security:

  1. No template contains the system-administrator bit. Administrator rights are always granted by hand and deliberately; even the "management" template does not open the Management cockpit.
  2. A permission change takes effect on open sessions immediately. Users used to have to log out and back in; now, the moment the administrator saves, that user's open sessions are refreshed transparently — the session does not drop, a page refresh is enough. If a user's password is changed their open sessions drop (they log in with the new password) — expected and safe.

Permission by invoice kind: return invoices are issued with the bit of their own commercial area — sales return faturacikis, purchase return faturagiris. A permission refusal now always arrives as 403 and names the required right (some paths used to show a "server error" 502). Details: Purchasing guide.

9. Login errors come in three classes: identity, throttle, load

Not every refused login is "wrong password". Read the message:

Code Message What to do
401 User name or password is wrong Your mistake; after the third attempt each wrong login adds a growing delay (up to 2 s).
429 “Too many wrong sign-in attempts — this address is temporarily blocked; try again in a few minutes.” The per-computer (IP) sign-in throttle. Only wrong logins count; colleagues logging in correctly from the same network do not trigger it. While the block lasts, the Retry-After header of the reply gives the real remaining time (at most 5 minutes) in seconds and it shrinks with every attempt; you do not have to wait a fixed minute. If the lock was set on the MES terminal, the staff portal reports the same remaining time.
503 Server busy: concurrent session ceiling reached / cannot connect to the HNR server Not your fault, and it does not count towards the throttle. When the session ceiling is full, idle sessions are swept first; if there is still no room, retry shortly. If it persists, tell a user with the Administrator right (the Administrator in the Settings › Users list).

Attachment upload: when many files are being scanned at once you may see "File scan queue full — try again shortly" (503); your file was not rejected, it just was not queued. Upload again a few seconds later.

10. Staff portal: login throttle and unlocking

The portal has two separate protections. (1) The computer (IP) throttle: too many wrong PINs from the same address in a short time returns 429 with “Too many wrong sign-in attempts — this address is temporarily blocked; try again in a few minutes.”; Retry-After gives the real remaining time and it shrinks. Correct logins do not count; fifty people logging in from the same factory network at shift change do not trigger it. (2) Account lock: 5 wrong PINs for the same personnel number → 15-minute lock; the MES terminal and the staff portal share the same counter. The HR manager unlocks it without waiting with the Unlock button on the row in Personnel › Portal accounts; the action is logged. The “Unlock” in Settings › Users is for WebOS user accounts and does not unlock a portal or MES account. Details: HR guide.

🔗 Related guides

The Print button at the top right produces an A4-friendly version. Related guides: Cockpit, Settings and Log, Archived Records.

Per-account sign-in lock. The per-computer (IP) sign-in brake stays; in addition, if 10 wrong passwords are typed for the same user name within 15 minutes, that user’s sign-in is stopped for 15 minutes. While locked even the correct password is rejected and the message does not say whether the user name exists. You open the lock with the Administrator right under Settings › Users; for details see the Settings guide.

The same logic on the portals. On the personnel portal 5 wrong PIN attempts per user name lock it for 15 minutes; a wrong old PIN typed while changing the PIN is counted too. The lock sentence does not reveal whether the account exists. A PIN must be 4–6 digits; a repeated digit (0000) and consecutive digits (1234, 4321) are refused. When the PIN or role changes, the account is closed or it gets locked, open portal sessions are closed; a portal session lives at most 24 hours.

11. Where to look when a message mentions a “security gate”

Security gates live in Cockpit › Audit › Security gates (the Cockpit window in the dock, Audit tab; the “Management window” in section 4 is today the name of this window). Messages about a gate write this path and the gate’s title (e.g. “Cockpit › Audit › Security gates › Plant capacity load (rough capacity)”); the internal setting key appears in no message, you look for the gate by its title in the list.

Permission messages also say where to grant it: in a sentence such as “Warehouses module permission required — Settings › Users.” the window’s visible name is written and the permission is granted in Settings › Users. Do not look for a person called a “system administrator”: the permission’s name and the place to grant it are written in the message.

Session life cycle

A session closes at most 24 hours after it was opened. Lock session also locks on the server (unlocking means signing in again; if the page is refreshed while locked a full sign-in is required). Changing the password closes the sessions on other devices; if an administrator resets a user’s password, renames the user or deletes the user, that user’s sessions are closed immediately. Responses that carry session information are not cached by the browser and signing out also works through the cookie. For details see the Settings guide.

Uploaded file types

Every file you upload to the program (document attachments, product and card pictures, production and quality attachments, shipping documents, invoice OCR images, warehouse and field photos) passes through a file-type allow list. Accepted types: pdf; pictures (jpg, jpeg, png, gif, webp, bmp, tif, tiff); text (txt, csv); office files (docx, xlsx, pptx, odt, ods) and zip. Engineering attachments and production files also accept technical drawing types (dwg, dxf, step/stp, iges/igs, stl). html, htm, svg, js, exe, bat, ps1, msi and every type not on the list are refused.

The extension alone is not trusted: the file’s content must match its extension. A file named picture.jpg that actually holds a web page or a script is refused (“… the file content does not match the .jpg type. Upload the file in its original form; allowed types: …”). A name with no extension or an unknown one returns “the file type could not be determined: the name must end with an allowed extension (e.g. document.pdf)”; a file that is too large returns “File too large (size; limit …)”. A refused file is not saved and is not attached to the document.

On download a file always arrives as a file; it is never run as a page in the browser. Pictures and PDFs whose content has been verified can be opened on the screen as a preview. For a file or picture that does not exist you see a 404 sentence such as “Picture not found.” If you must share a document in HTML or SVG form, convert it to PDF and upload that.

Some channels have their own narrower list: invoice OCR upload (PDF, JPG, PNG and e-Invoice XML; an XML that contains a script, html or svg is refused), customer-portal request attachments (JPEG, PNG, WebP; PDF as well on a payment request; at most 2 MB), shipping delivery and return photos and signature (PNG, JPEG, WebP, GIF; svg and html are refused), the asset-assignment signature (PNG or JPEG) and the bank statement upload (PDF, XLS, XLSX, CSV, MT940; it is only read, not stored).

Sign-in and password error codes (integration)

For integrations: a wrong user name or password at sign-in returns 401 with the code KIMLIK_HATALI; a wrong current password when changing the password returns 401 and MEVCUT_PAROLA_HATALI (the session is not dropped). The sign-in brake returns 429 and the Retry-After header gives the remaining wait time in seconds: at most 15 minutes for the account lock and at most 5 minutes for the computer (IP) brake; while the block lasts, the remaining time shrinks with every request. The PIN lock of the employee portal and of the MES terminal uses the same header (5 wrong PINs → 15-minute lock); a wrong current PIN when changing the PIN on the MES terminal returns 401 and MEVCUT_PIN_HATALI. The 401/403 responses of the messaging and bank connection services also carry the same body as the other endpoints: hata, kod, degerler.

The period lock is a single gate

The date lock in the security gates, the period lock on the Accounting › Periods tab and the period lock in Settings › Corporate controls are the same gate: a document, receipt or stock movement dated in a locked or closed month cannot be written, edited, deleted or moved to another date (409). The refusal sentence says “A {belgeTuru} dated {tarih} falls in the locked accounting period {donem}; first unlock the period with a reason.” Applying and removing the gate requires a reason of at least 5 characters; the reason appears in Cockpit › Audit on the “Security gate — record” row. Details: Accounting › Period lock.

The scope is no longer limited to accounting documents: cheque payroll/collection/endorsement, consignment movements, MES finish, direct production, bank statement lines, quarantine release and human-resources writes (advances, leave, absence, overtime, punches, day close) pass through the same gate. Details: Accounting › Period lock.

HNR Help Center · Audit, Gates and Anomalies · This page is updated together with the program. Report anything missing or wrong to your system administrator.

Security classification and need-to-know

For companies working in defence, file attachments and projects are filtered by security classification: public < internal < restricted < secret. A user without the clearance does not even see the record IN THE LIST, because the existence of a document is itself information. This gate has no visible escape and every refused access is written to the access trail. Detail: Defence Traceability → Need to know.

Related guides