Access

Access begins with an approved organization.

How organizational boundaries, user scope, and session safety apply to HARBINGER.

01

Only qualified enterprises and institutions receive organizational access

Reading this site does not grant access to HARBINGER, a customer workspace, data, credentials, or a Sandbox. There is no personal signup or instant credential.

Customer access follows an enterprise or institution application, organization and business-purpose qualification, approval of scope, price, and contract, and then an invitation to named users. Each user remains bound to the approved organization, role, purpose, and data scope.

02

Protect the session boundary

  • Use only the account issued or approved by your organization.
  • Do not share credentials, recovery codes, session tokens, or customer URLs.
  • Export or capture information only under your organization’s handling rules.
  • Report unexpected access instead of attempting a workaround.
03

Read access states literally

  • ACCESS_DENIED — the current identity is not permitted to view the resource.
  • NO_DATA — no permitted input is available.
  • UNMAPPABLE_VERSION — the workspace cannot safely interpret the contract version.
  • FAILED — processing stopped without exposing sensitive internal detail.