A / Secure sign-inService · checking
Service secret

OpenID Connect / secret

Copy the secret now

The secret is shown only once. AuthGuard stores only a cryptographic digest; it will not show it again.

Service
Credential

RADIUS clients

New RADIUS client

Transport

Devices send the password inside TLS to AuthGuard and must check its certificate. With a code as second factor, people type the code after the password (password,123456).

Legacy method for devices that only offer PEAP: people sign in with a network credential from their portal, never their password. Prefer EAP-TTLS.

Risk

      Assessment digest
      Model
      Features

      The person can contest this decision with the organization's administrators.

      Network credentials

      Your network credential

      Type these on the device now. The password is shown once and is never shown again.

      User name:

      Password:

      RADIUS clients

      Shared secret

      This secret is shown once. Enter it in the client now; AuthGuard keeps it sealed and never shows it again.

      New local proof

      Passkey / WebAuthn

      Add device

      A recent ProofFlow or Presence session authorizes directly. The password only authorizes the account's first authenticator.

      WebAuthn boundary. AuthGuard receives no biometrics or PIN; it receives the public key and signed responses.

      Presence / new device

      Pairing / five minutes

      Pair authenticator

      Create a disposable QR for the new device. The QR does not contain your session and is no longer accepted after this ceremony.

      QRSingle-use secret · 256 bit
      ValidityMaximum · 05:00
      BiometricsAlways local

      Local setup

      Instance / bootstrap

      First organization

      The bootstrap token is only sent to the service and is never stored by the browser. A safe retry temporarily keeps only the idempotency key and a signature of the non-secret fields.

      Use 15 to 1024 Unicode characters, for example a long, unique phrase. Spaces and accents are accepted; new passwords are normalized to NFC before secure derivation. The service rejects values known to be common or compromised, without contacting external services.

      Organization / activation

      First administrator

      Activate the organization

      Sensitive change

      Credential / revocation

      Remove device

      This device will no longer be able to authenticate the account.

      Warning. The last passkey can only be removed after you confirm the recovery method. A recovery session only removes an authenticator if another one remains active.

      Computers

      Organization / computer sign-in

      Sign-ins

      WhenAccountHowOutcome

      Local accounts on this computer

        Offline

            Agent version

            Helpdesk recovery

            Check who is calling first. Type the challenge the computer shows; read the answer to the person. Each answer is audited and the computer gets a new recovery key afterwards.

            Install tokens

            Organization / computer sign-in

            Copy the install token now

            AuthGuard stores only a digest of the token and does not show it again. The instructions below carry it; they are gone when this window closes.

            Account / phone

            Approver phones

            Add a phone

            An approver phone approves sign-ins and sensitive changes with a code you type and your fingerprint or screen lock. You need the AuthGuard Presence app on an Android 14 phone or later.

            Session / phone

            Phone approval

            Approve on your phone

            Open AuthGuard Presence on your phone. When it asks, type this code, then confirm with your fingerprint or screen lock.

            Code to type on the phone

            The code is not a secret and grants no authority; it shows that the phone and this screen are about the same request. Close this window to cancel the request.

            Sensitive change

            Approver phones

            Remove phone

            Removing a phone needs a recent confirmation. You can add the phone again later.

            My phones

            Approver phones

            Rename phone

            Up to 64 letters, numbers and spaces; you may also use - _ . , ' ( ) + # / :. You, your administrators and the phone itself see this name.

            Link received by email

            Single use

            Account security

            Local confirmation + current password

            Change password

            Ends all sessions, including this one, and invalidates pending sign-ins. Devices, local biometrics and other factors are kept.

            Use 15 to 1024 Unicode characters. Spaces and accents are accepted; new passwords are normalized to NFC before secure derivation. The server rejects common and predictable passwords.

            Emergency access

            Recovery / safe rotation

            New codes

            The current set stays active while you prepare and save the new one. It will only be replaced after your explicit confirmation.

            Fallback / one-time code

            TOTP / open standard

            One-time code

            A compatible generator can create standard codes. ProofFlow remains the primary proof and is required to enable, resynchronize or remove this fallback.

            Different assurance. TOTP, HOTP and OCRA use a shared secret shown once; a passkey uses asymmetric cryptography. These classic factors do not satisfy PQ Required. None of these flows is, on its own, a Presence attestation.

            StatusFetchingWaiting for the server.

            Offline codes for your computers

            When your work computer has no connection, it asks for the code of that computer. Add it to your authenticator app now; it works only on that computer and only for a few days offline.

              Manage / Presence invitation

              Invitation / PQ channel

              Invite with Presence

              The browser prepares only the email and the organization. Android confirms the Match, creates the identifiers and the secret locally and sends the request through the Presence session. No secret or authority passes through this QR.

              Manage / new user

              Identity / creation

              Create user

              Create only the access that is needed. The initial password must be delivered through a separate channel and replaced by ProofFlow at first sign-in.

              Use 15 to 1024 Unicode characters, for example a long, unique phrase. Spaces and accents are accepted; new passwords are normalized to NFC before secure derivation. The service rejects values known to be common or compromised, without contacting external services.

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.

              Manage / authentication records

              User / Presence

              Presence credentials

              Credential records, not physical devices. This lookup does not attest online status, compliance or current PQ qualification. Biometric images, templates and results are not shown. Passkeys are not included in this view.

              Manage / approver phones

              User / approver phones

              Approver phones

              Phones registered for this person, with what each phone attested at enrollment. Keys and attestation chains are never shown. Removing a phone needs a recent confirmation and ends the sessions it approved.

              Manage / support

              User / lost authenticators

              Reset authenticators

              Authenticators to revoke

              All of this user's sessions and recovery codes are revoked. The enrollment code is shown only once.

              Manage / transitional credentials

              User / WebAuthn

              Registered passkeys

              Passkeys are transitional credentials, not Presence or proof of PQ support. Includes disabled records; does not identify physical devices. New records are not added to a lookup in progress. The status of each page is observed at the time it is read and is not a frozen history.

              Manage / data subject rights

              User / GDPR

              Privacy

              Each action requires recent confirmation and is recorded in the audit. Deletion is irreversible: it replaces the email, disables the account, revokes sessions and removes free text; the audit and signed receipts are pseudonymized.

              Manage / sensitive change

              User / access

              Change access

              • Suspending revokes all of that user's sessions.
              • Demoting removes administrative access.
              • The last active administrative account cannot be suspended or demoted.

              Recent ProofFlow. Confirmation requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes), according to the server clock. Status · confirmation requested on execution.

              Manage / limited authority

              User / direct operation

              Act on a known UUID

              Use only an identifier obtained through an authorized channel. This operation does not confirm whether the user exists, nor does it reveal the email, role or current status.

              No preview. Authorization is checked again in the same operation. Privileged identities and the last administrative account remain protected by the server.

              Recent ProofFlow. The action requires recent local verification and is bound to the exact UUID and command. Status · confirmation requested on execution.

              Recent confirmation

              Session / confirmation

              Confirm this change

              Choose how to confirm that it is you. The session is replaced by a recent session; nothing is changed without this confirmation.

              Third-party request

              Decision / passkey

              Review request

              Comparison code—

              Operate / revocation

              Session / end access

              Revoke session

              The selected session loses access immediately. The ProofFlow credential is not removed.

              Recent ProofFlow. This action requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). Status · confirmation requested on execution.

              Operate / limited authority

              Session / direct revocation

              Revoke known UUID

              Use only an identifier obtained through an authorized channel. The browser does not confirm the session's existence, owner or status before the operation.

              Immediate revocation. If the UUID identifies the current session, the browser deletes the local authority after the server confirms.

              Recent ProofFlow. The action requires recent local verification and is bound to the exact UUID. Status · confirmation requested on execution.

              Manage / immutable revision

              Policy / access

              New revision

              Edit only the versioned request below. The server validates and normalizes the closed language before computing the canonical digest; creating does not activate the revision.

              Contract: schemaVersion, version and rules. Limit of 256 KiB, 256 rules and 32 conditions per rule.

              New OIDC portal sign-in rule

              Use the client_id from the OIDC registration, not the trade name or the portal address. The server requires it to match the request approved by Presence. Prefixes and wildcards are not accepted.

              Choose groups by name or enter UUIDs directly. The lookup requires groups.read and only adds references to the draft. Belonging to one of the listed groups is enough. Empty: this rule does not restrict by group. Names, wildcards and repeated IDs are not accepted; the server checks current membership when authorizing.

              Access schedules · UTC

              The start is included and the end is excluded. UTC does not follow local daylight saving changes. An overnight period is split between the selected day and the next.

              Start days · UTC

              Only changes the draft, without activating the policy. Replacing or removing a schedule can broaden access and requires review. The other conditions are preserved. Rules with several AND schedules require explicit editing in the JSON.

              This preview does not authorize access: it does not evaluate the other conditions or revoke sessions. The server uses its own time when issuing and consuming authorizations.

              Authentication requirements

              In ProofFlow authorizations, these filters use the proof validated for the operation: passkey or Presence. They do not change the organization's sign-in methods. A Presence approval can be the operation's proof even when the browser session started with a passkey.

              New condition
              One of these methods

              Each condition is a filter of this rule, not a change to global MFA. Methods within the same condition are alternatives (OR); different conditions must all match together (AND). Removing or replacing can broaden access. Review the effect (allow, deny or request step-up) and the other rules.

              Network zone conditions

              The server classifies each connection by the verifiable network address and the organization's CIDRs. Public is a known connection with no match in the catalog; it does not mean access is allowed. Headers sent by the client do not define the zone. Without verifiable context, a policy with network conditions does not authorize access.

              Alternative zones within this condition · OR

              The rule's other conditions remain joined by AND. If there are several network conditions, select exactly the one you want to change; the editor does not merge them. Also review the rule's effect: allow, deny or request step-up.

              Immutable. Once created, a revision cannot be changed or deleted. Status · confirmation requested on execution.

              Manage / immutable revision

              Policy / read

              Review revision

              Revision · —Immutable—

              Created · —

              Safe read. Always compare the digest shown with the rollout identity before preparing or promoting.

              Manage / advisory lab

              Policy / simulation

              Test decision

              Revision · —No authority—

              Edit a synthetic context and observe the decision, reasons and matching rules produced by the same deterministic engine.

              The tenant, schema and simulate mode are set by the server. This data is never accepted as proof of authentication, device, network or risk.

              Manage / shadow observation

              Rollout / no effects

              Prepare candidate

              Revision——

              The candidate will be evaluated in parallel only for comparative evidence. It does not allow, deny or require factors in any operation.

              Rollout state · —

              Shadow only. Promotion is always a separate, confirmed action. Status · confirmation requested on execution.

              Manage / sensitive transition

              Rollout / confirmation

              Confirm transition

              Review the change before applying it.

              Source
              —
              Target
              —
              Expected state
              —

              Authority change. The operation uses compare-and-swap and requires recent ProofFlow. If the state changes, nothing is applied.

              Policies / Presence

              Request prepared · awaiting confirmation

              Continue on your phone

              In Presence, choose “Ler pedido de política por QR” (scan policy request by QR) or “Importar pedido de política” (import policy request). Compare the Match and review the full command before authorizing.

              The file contains the policy, but it contains no credentials and does not authorize changes. Share it only through the channel approved by the organization. It expires in five minutes; closing this window does not delete files already downloaded. The Match is public; it does not authenticate the sender.

              After confirming in Presence, choose “Mostrar confirmação ao browser” (show confirmation to browser). This window accepts only the visual confirmation of this still-valid request. An uncertain result does not allow the change to be repeated.

              The confirmation is bound to the visual channel; it does not authenticate the server. Anyone who obtains the request file can forge it; do not use it as audit proof. It does not change permissions, versions or state in this console.

              Policies / approval

              One exact change

              Approve this change

              Approve exactly this change on your approver phone or with your passkey. The approval works once, for this command only, and expires in a few minutes. If the policy changes in the meantime, nothing is applied.

              Action
              —
              Policy
              —
              Revision
              —
              Rules
              —
              Expected state
              —
              Command digest
              —

              The phone shows the same action, policy, revision and command digest. Approve only if they match what you meant to change.

              Manage / group

              Organization / authorization context

              New group

              Up to 64 lowercase letters without accents, numbers, dots, hyphens or underscores. The name stays reserved even when the group is archived.

              Up to 512 Unicode characters. Do not include sensitive data.

              Changes require recent local confirmation. In production, the server requires Presence; a classic passkey does not replace that authorization.

              Account / local tracking

              Operations / result

              Confirm without retrying

              These identifiers let you check the result of your management requests, even after signing in again. We do not store passwords, profiles or tokens in this tracking record.

              An unknown result does not mean failure or cancellation. Checking never repeats the change. The record belongs to this browser; clearing the site data may delete it.

              Organization / creation

              Create organization

              The organization is created awaiting activation, with no users, on the AuthGuard plan. Its first administrator activates it afterwards.

              3 to 63 lowercase letters, digits or single hyphens, starting and ending with a letter or digit, not only digits. It names the organization's address and is never reused.

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.

              Organization / creation

              Create an organization with its licence

              In one step: the organization is created awaiting activation, with seats from one of your pools. Issue an activation code for its first administrator afterwards.

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.

              Organization / lifecycle

              Suspend

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.

              Organization / domains

              Remove domain

              Users who registered passkeys on this domain must use another address afterwards. Type the domain to confirm.

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.

              Organization / branding

              Branding

              Name shown:

              Distributors / onboarding

              Create distributor

              The distributor is created awaiting activation. Issue an activation code for its first operator afterwards.

              3 to 63 lowercase letters, digits or single hyphens, starting and ending with a letter or digit, not only digits. It names the organization's address and is never reused.

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.

              Activation code

              Copy the activation code now

              This code is shown only once. AuthGuard keeps only its digest. Deliver it to the administrator through a separate, trusted channel.

              Activation link

              Licences / pools

              Issue a licence

              The licence is usable at once; its signed record follows within minutes. Seats count active users.

              Licences / pools

              Revoke the licence

              Billing / orders

              Order more seats

              The price comes from the platform's price list and your partner discount. A different price at the time of ordering is never charged silently: you are asked to see the price again.

              Billing / orders

              Revocation plan

              If this payment is still missing 60 days after its due date, the batch's seats end. Say which customers lose them first; without a plan, the customers allocated last lose them. Inside a customer nobody is deleted: the people who have not signed in for the longest are suspended.

              Organization / licence

              Swap who is suspended

              Billing / orders

              Record the payment

              A waiting order is activated at once and the pool grows. The payment is recorded with your name in the platform's audit.

              Billing / orders

              Reject the order

              Billing / orders

              Change the price list and terms

              A new price list applies to the next quote. Orders keep the price they were placed at.

              Billing / orders

              Change the credit terms

              New distributors prepay (credit limit 0). A limit grows with the deposit, the bank guarantee and payments made on time.

              PAM / inventory

              Add target

              Legacy and weaker: turn it on only for MariaDB or older MySQL accounts that cannot move to caching_sha2_password or ed25519. Turning it on or off is recorded in the audit log.

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.

              PAM / accounts

              Add account

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.

              PAM / sessions

              Session recording

              PAM / application secrets

              Application secret

              The value is sealed in the vault and is never shown again.

              PAM / application secrets

              Approval profile of

              With a profile that needs approvals, a workload receives this secret only after the profile's approvers approve its request.

              PAM / application secrets

              Rotation notice

              Send when

              PAM / workload identities

              Workload identity

              The rule pins the owner, the repository and the branch or environment exactly. Pull-request runs are refused.

              PAM / rotation

              Rotation policy

              PAM / access

              Access profile

              Approver groups
              Database sessions

              Access

              Request access

              Access

              Credential

              Shown for 30 seconds. A copy is cleared from the clipboard 30 seconds later.

              
                    
                    

              Access

              Connect to the database

              Use these settings in psql, mysql, DBeaver or another client within one minute. The password works once and only over TLS.

              Host
              Port
              User
              Database
              
                    
                    

              Command line

              
                    

              JDBC address

              
                    

              PAM / accounts

              Credential of

              The secret is sealed in the vault and is never shown again. Each change creates a new version.

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.

              Versions

              VersionStatusSince
              PAM / accounts

              Rotation of

              The policy sets how often the credential changes; the connector sets how.

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.

              PAM / accounts

              Access profile of

              Requests for this account follow its profile: approvals, lease length and what the requester may do.

              Strong confirmation. This change requires a passkey or Presence with local verification within the last 15 minutes (5 for sensitive changes). The server validates the session and the credential again. Status · confirmation requested on execution.