Netforge.ai Docs
Open the app →
Docs/Administration/Account & Security

Account & Security

Profiles, email verification, password compliance, two-factor authentication, sessions and sign-out, geo-restriction.

Relevant for:Admin / OwnerEnterprise / NetOps

Your profile#

Where to find itAvatar menu→Edit Profile

Name, phone and contact details, password change, and two-factor authentication(TOTP with backup codes). The signed-in avatar menu is present on every page — the floating badge, the landing-page nav, and the canvas top bar are the same control, and it is fully keyboard-operable: arrows and Home/End move, typing jumps to an item, Esc closes and returns focus.

Sessions & signing out#

Where to find itAvatar menu→Sign out
  • Sign out ends the session on the server — for every device the account is signed in on, not just the browser that clicked it. A token that leaks after you sign out is dead on arrival.
  • Changing or resetting your password signs out every other session. The session that made the change continues without interruption; everything else — including a session someone else may be holding — is evicted immediately. This is deliberate: a password reset is most often done because the old password may be compromised.
  • A deliberate sign-out clears the browser — saved deploy credential profiles, Azure service-principal secrets, locally stored design copies and dismissed findings are all removed, so nothing sensitive survives on a shared machine.
  • An expired session clears only credentials. If your session times out mid-work, secrets are removed but locally saved work is left alone — an expiry never deletes a design.
Why
“Sign out” that only forgets the token in one browser is a promise the server never kept — the token itself stayed valid until it aged out. Ending the session centrally, and tying password changes to it, means the account holder always has one immediate, reliable way to cut off access: change the password, and every open session everywhere is gone.

Account security policy#

  • Email verification — accounts activate only via the emailed link (check junk/spam).
  • Password compliance — 12+ characters with upper/lower/number/special; the last five passwords cannot be reused; resets are rate-limited and tokens are one-time.
  • Login protection — failed attempts are rate-limited per source; 2FA challenges are burned after use.
  • SSO — enterprise OIDC/SAML is available for on-prem installs (see the SSO setup guide).

Two-factor authentication#

Where to find itAvatar menu→Edit Profile→Two-Factor Authentication

Enrolment takes a minute: scan the QR code with any authenticator app (Google Authenticator, Microsoft Authenticator, Authy, 1Password), enter the six-digit code to verify, and save the backup codes — they are shown once, with copy and download buttons, and each one works a single time if you lose the authenticator. Regenerating backup codes and disabling 2FA both require your password again.

Important
Two-factor authentication is mandatory for privileged roles — owner, admin and lab_editor. Signing in without it lands you straight on the profile enrolment panel, and the rest of the application stays locked until a code is verified. It cannot be switched off while the account holds one of those roles, and the requirement is checked on every request — so being promoted into a privileged role takes effect immediately rather than at the next sign-in. Editors, viewers and observers are unaffected.
Why
A privileged account reaches every design in the organisation, the stored device credentials behind deploy and drift, and the lab runtime that can boot privileged containers. A password alone is too thin a wall in front of that, and a grace period that never ends is the same as no requirement — so enrolment is enforced at the door instead of being requested by email.

Platform-edge security#

The public deployment fronts through Cloudflare with geo-restriction (US, Canada, India) and tuned caching. Designs never contain live secrets — generated configs carry PLACEHOLDER where credentials belong.

Why
Layered account security is table stakes for a tool that holds network designs: verified identities, strong passwords, second factors, and an edge that drops traffic from geographies you don't serve. Keeping secrets out of designs means even a leaked export is an architecture document, not a credential dump.