Skip to content
IdentitéTrust starts here
English
EnglishEspañolPortuguês
Contact

Products / NoPass™

Trust at sign-in. Control at the next decision.

Give employees a clear way to authenticate and your team the tools to manage access. NoPass also supports integrated approval requests where an application needs a person’s decision before continuing.

Original NoPass app authentication request with matching picture on the connected service

Use NoPass™ where a person’s decision matters.

The approval capability also applies beyond the workforce: a bank can ask its customer to confirm a transaction, or an application can ask an owner to approve an AI-agent action.

Full Duplex Authentication® connects this access journey to the enrolled app’s authentication-service relationship. The employee can check the intended request, while the application keeps control of permissions.

Use NoPass where a person’s decision matters.
MomentWhat changesWho benefits
Workforce sign-inUse an enrolled device and configured local factors to reach an application, gateway or Windows workstation.Employees and the IT team supporting them.
Sensitive-operation approvalHold an operation until the responsible person confirms the request on their device.Customers, employees and the system owner.

Keep people and devices manageable.

The administration console brings users, devices and authentication activity together. Teams can enroll users, manage registered devices, set authentication factors and remove access when a device is lost or an account is no longer needed.

That gives the support team a place to resolve access problems and gives the person using NoPass a defined route back to their work.

  • See people and their enrolled devices together.
  • Review the relevant account and device state.
  • Keep administrative actions with the responsible IT team.

Plan access beyond the first login.

From enrollment to a changed device.

  1. Enroll

    Connect the employee, account and approved device through the organization’s enrollment process.

  2. Return

    Use the configured application, gateway or Windows access path.

  3. Change or recover

    Identify the support owner, revoke a lost device and restore access under the organization’s policy.

Add confirmation before the operation proceeds.

Your system chooses the sensitive operation and responsible person. NoPass brings the request to that person’s phone; the application continues according to the approval result.

Privileged-action approval · interactive example

A sensitive operation is ready.

The application sends a NoPass approval request to the person responsible. Start the request in the application.

Your work application
Example application request

Grant elevated access

NoPass
Enrolled deviceReady when you are.

Try the highlighted button or use the controls below.

Connect to the environment you operate.

NoPass supports configured federation and RADIUS access paths, Windows Desktop Unlock, and application integration. The installed service can run on your infrastructure, including on-premises and private-cloud environments; cloud-service options depend on the product edition.

Keep your application’s business permissions and choose the authentication or approval point where NoPass participates.

Evaluate one workflow.

Define a useful decision before planning a wider rollout. Agree scope, responsibilities and success criteria with the team.

  1. Choose one workflow

    Identify the people, application and access or approval moment.

  2. Agree the integration

    Map enrollment, account ownership, result handling and recovery.

  3. Evaluate with representative users

    Observe completion, recovery and support workload against agreed criteria.

  4. Decide on rollout

    Use the findings to decide what to change, expand or stop.

Review your NoPass deployment

Plan the environment and the support path.

NoPass connects through a configured integration. Start with one application or gateway and the people responsible for enrollment, access policy and recovery.

Plan the environment and the support path.
DecisionWhat to establish
Access pathFederation, RADIUS or Windows access for the selected environment.
Local confirmationThe factors enabled for the enrolled device and the organization’s policy.
Day-two ownershipEnrollment, device revocation, recovery, offboarding and escalation.