Loading…
Velaxe
AccessGuard — Authentication, Customer Identity, Consent, Notifications & App Authorization | Velaxe

AccessGuard

Connect an external website with Bridge v2

Create a scoped site credential and connect the server-side bridge proxy/browser SDK to AccessGuard.

15 min Intermediate Platform Administrator, Web Application Engineer Updated Aug 23, 2026
View App All Guides

Overview

Create a scoped site credential and connect the server-side bridge proxy/browser SDK to AccessGuard.

Prerequisites

None.

Permissions required

connections.manage configure

Steps (4)

Estimated: 15 min
  1. 1

    Create the site credential

    Platform Administrator 4 min Back to top

    Create an AccessGuard site credential with the allowed origin, canonical operations/scopes, status, callback metadata, and rate limit.

    Tips

    —

    Validation

    —

    Success criteria

    —

  2. 2

    Configure the server-side proxy

    Web Application Engineer 4 min Back to top

    Set the AccessGuard Bridge URL, client ID, and secret in the website server environment so the browser never receives the credential secret.

    Tips

    —

    Validation

    —

    Success criteria

    —

  3. 3

    Connect the browser flow

    Web Application Engineer 4 min Back to top

    Use the AccessGuard JavaScript bridge helpers for registration/login/token/profile/inbox operations through the site proxy.

    Tips

    —

    Validation

    —

    Success criteria

    —

  4. 4

    Verify the signed path

    Platform Administrator 3 min Back to top

    Run a health/login request and confirm AccessGuard accepts the HMAC v2 request and records the client activity.

    Tips

    —

    Validation

    —

    Success criteria

    —

About this guide

AccessGuard centralizes workspace authentication and customer identity. External websites can use the signed Bridge v2 proxy and JavaScript SDK for registration, login, verification, recovery, token refresh, profile management, protected media, and notification inbox operations.

Inside the workspace, AccessGuard owns users, sessions, verified identities, customer profiles, communication preferences and consent, approval state, KYC documents, risk flags, notification state, audience segments, application operation grants, delegation policies, and trusted context actions. Canonical capabilities are available through Handler and RCP, with selected operations available through Bridge v2.

Configured providers handle downstream delivery and human work: email, SMS, WhatsApp, voice, push, and case/problem operations can be delegated while AccessGuard preserves the identity, authorization, provenance, and customer-policy record.