Tenant identity through the full request.
Customer separation needs to extend from source data to the authority for an action.
Fibric carries reseller and tenant identifiers through its event and storage contracts. That identity determines the context a request may use and the customer on whose behalf work is proposed. Filtering the final screen is insufficient if an earlier query or action can cross the boundary.
Bearer credentials, database access, source bindings, and operator context each need a consistent customer scope. A request that lacks that scope must not silently fall back to a different customer or a shared demonstration dataset.
Live data and placeholders.
BearScope’s real-data tenants are expected to render governed source data. When a source is unavailable, the interface should show an unavailable or explicitly marked fallback state. A plausible number is not a substitute for a source record.
White labeling changes the product presentation for a tenant. It does not change the requirement to keep source data, policies, and execution records bound to the correct customer.
Action authority.
An action also needs the tenant and user context that permits it. The deployed action inventory and runtime configuration determine which operations are available. A product role, an API capability, and a tenant’s source permission must agree before an enabled path can proceed.