License Details (View‑Only)

Vincent Jay

14 Jan 2026 — 2 min read

Overview

The License Details (View‑Only, Masked) feature provides operations users with a secure, read‑only view of license‑specific client configuration data. Configuration is fetched via the ClientConfig API and rendered exactly as returned, with all sensitive fields masked. No unmasking or editing capabilities are provided.

Scope & Goals

In scope

Fetch and display client configuration by licenseId
Render masked JSON exactly as returned by the API
Clearly communicate which fields are masked

Route: /ops/config/licenses/:licenseId
Deep links: Supported (page loads correctly on cold start)

UI & UX

JSON Viewer

Collapsible JSON tree view
JSON is rendered exactly as returned by the API
No transformation or enrichment of values

Masked Fields

Masked values remain obscured at all times
Nodes whose paths appear in _metadata.masked display a “Masked” badge
No control or action exists to unmask values

Masked Paths Panel

Side panel lists all entries from _metadata.masked
Panel is always visible to clearly communicate hidden data

Utilities

Copy Path:
- Users can copy the JSON pointer / dot‑notation path of any node
- Useful for support, debugging, and cross‑referencing

Approach: Improve Bot Discoverability with Search and Team Scoping

1. Global Bot Search Bar What: * Add a persistent search input at the top of the bot directory. * Search should match: * Bot name * Short description * Tags / keywords * Owner or team (optional enhancement) 2. Role-Based Bot Filtering What: * Automatically filter bots based on the user’s authenticated role, team, or department.

Browse & Search Licenses

Overview This deliverable introduces a searchable License List page within OpsConfig. The page allows operators to browse and locate licenses using substring search across key identifiers, while ensuring all sensitive data remains masked according to the ClientConfig API response rules. The feature is read-only and intended to support operational visibility

How do you setup identity or age verification so that only certain locations need to get verified?

Answer: Use Location-Based Identity Verification. This is enabled via the locationRestrictions.requiresVerification attribute in your application configuration to define which countries and regions require verification. Summary Token of Trust now supports location-based verification requirements through the locationRestrictions configuration. This feature allows you to specify which geographic locations (countries and regions)

cd_release Link Docs Test

this is the test btw, ignore this.