Identity · AI access · Signing

IOPass

Connect the person to the permission.

IOPass brings account authentication, application access and AI model controls into a shared platform. Its mobile companion helps people approve sign-in requests, while IOPass Sign adds document review, explicit consent and PDF sealing.

Open IOPass accountDiscuss integration →

A Tech Pro Innovations product, offered through tag.digital’s product and integration portfolio.

How the platform connects
PeopleApplications
IOPassIdentity and access decisions
  • Sign-in
    Account authentication
  • AI gateway
    Permitted models and usage
  • Mobile companion
    Review and approve requests
  • IOPass Sign
    Document review and consent

Capability overview. Access to each service is granted separately.

What it does

Shared services for connected products.

01 / Identity

Sign in across connected applications.

Applications can delegate authentication to IOPass instead of maintaining a separate login system for every product. OAuth 2.0 and OpenID Connect support a shared identity, with access scoped to what an application is allowed to request.

  • Email one-time codes and password-based authentication.
  • Authenticator-based multi-factor authentication where required.
  • Phone-assisted QR sign-in with explicit request approval.
  • Account, security, device and activity management.
02 / AI gateway

Control who can use which models.

IOPass provides a common API for configured AI providers. Administrators manage model and voice access for applications and individual users, with usage records, rate limits and daily or monthly quotas.

  • OpenAI-compatible interfaces for supported chat, image, speech and embedding services.
  • Application and user permissions for models and voices.
  • Central provider configuration and usage visibility.

Available models and functions depend on the providers and permissions configured for your environment.

03 / Mobile companion

Review an account request on your phone.

The IOPass app supports multiple isolated accounts, QR and link-based request review, and device approval. Its Authenticator keeps verification codes separate from the app’s local assistant tools.

The companion also includes local reminders, reusable routines, an encrypted Inbox and Wallet, QR/OCR capture and local search. These assistant features run without hosted AI. IOPass Sign is available from All Tools and opens its hosted signing screens in the browser.

Availability: iOS and Android builds are currently distributed internally. About the mobile app →

04 / Document workflow

Move a PDF from review to recorded consent.

IOPass Sign lets an authorised application prepare a PDF, assign recipients and signature fields, and send invitations in sequence or in parallel. Recipients authenticate and explicitly consent before the document is sealed.

Completed packages can include the sealed PDF, signing record, evidence and certificate information. An API key or an application integration cannot approve a signature on a recipient’s behalf.

See the signing workflow →
Example / QR sign-in

Scan, review, then approve.

  1. 01 / Request

    Start in the application

    A connected application presents an IOPass sign-in request as a QR code or supported link.

  2. 02 / Review

    Choose the account

    Open the request in IOPass on the enrolled phone and select the account to use.

  3. 03 / Approve

    Confirm deliberately

    Review the request and approve it. Additional authentication applies when the application’s policy requires it.

  4. 04 / Continue

    Return to the application

    The application completes its sign-in flow and applies its own access rules.

Scanning a code is not approval. An IOPass account also does not automatically grant access to every connected application.

IOPass Sign

A document workflow with a clear record.

  1. 01 / Prepare

    Set up the PDF

    Upload a document, add recipients, place signature, name and date fields, and choose the signing order.

  2. 02 / Send

    Invite the recipients

    Sending freezes the document, recipient list and field layout for the review and consent process.

  3. 03 / Consent

    Each person decides

    Recipients use the hosted workflow to authenticate, review the document and explicitly consent.

  4. 04 / Keep

    Download the record

    Retrieve the completed PDF and its supporting record. Integrations can receive signed webhook events.

Check a completed document.

The browser-based verification service checks supported IOPass PDF seals and optional evidence packages. Document content stays in the browser; only the embedded certificate fingerprint is queried against the public certificate registry.

Results distinguish document integrity, certificate status and available consent evidence. Missing evidence is not treated as proof of participant consent.

Open PDF verification →
Explore IOPass SignTry the sample signing flow →

The sample flow requires sign-in and explicit actions to send an invitation and sign. Developer documentation and the document workspace require approved access; production signing is enabled separately.

For product and IT teams

Connect the services your product needs.

Customer and staff portals

Use OAuth 2.0 / OpenID Connect with the authorisation code and PKCE flow to connect account sign-in. Define the requested scopes and keep business roles and application eligibility explicit.

AI-enabled applications

Route supported model requests through the gateway, grant access per application or user, and set usage limits. Your product determines what data to send and how people review the output.

Document-driven services

Use the signing API and SDK to create PDF workflows, open hosted preparation and signing screens, receive status events and retrieve completed records. Sandbox and production access remain separate.

Implementation with tag.digital

We help map the login journey, account roles, integration points and document workflow. Start with the service you need, then agree the access configuration and a suitable rollout scope.

Practical questions

Before you integrate.

Do we need to use every part of IOPass?

No. Sign-in, AI model access and signing have their own integration and permission requirements. A product can begin with account sign-in and add other services when they are needed and enabled.

Does signing in give a user unrestricted AI access?

No. Authentication establishes the account identity. Model and voice access, quotas and application permissions are configured separately.

Can we download the mobile app from a public app store?

The current iOS build is distributed through internal TestFlight and the Android build through an internal APK. Public App Store, Google Play and HarmonyOS availability is not announced here. Contact us about access.

Is IOPass Sign the same as a government or CA-issued signature?

No. The current service records the recipient’s authentication and consent and applies an IOPass document seal. Government-provider signing is not yet available. Select a signing method that fits your organisation’s document and recipient requirements.

How do we discuss pricing and implementation?

Tell us the applications you want to connect, the expected users, model usage and signing volume. We will discuss service access, integration and support for that scope. This page does not publish fixed pricing or service-level commitments.

Bring your product into the conversation.

Share the sign-in, AI or document workflow you want to connect. We’ll help define how IOPass fits.

Enquire about IOPassAll products →