What problem does it solve?
Provides a clear, repeatable way to determine whether a given phone or member ID corresponds to an active 2B business member and exposes the relationships between Member, BusinessMember, Brand, Store, and permissions so developers and operators can make correct authorization and data-linking decisions.
Core Features & Use Cases
- Clear 2B identification: Rules and SQL/API patterns to detect active business members by phone or UUID and differentiate 2B vs 2C accounts.
- Permission and role mapping: Explanation of the Permissions bitmask, default Agent behavior, and Store vs Agent differences for authorization checks.
- Brand and store relationships: Guidance on linking BusinessMember to Brand and optional store metadata, including queries and notes about brand tables and EffectYn filtering.
- Operational scripts: A PowerShell query script to call Member service endpoints for ByPhone and ById lookups for diagnostics and integrations.
Quick Start
Query the member by phone or id using the provided script or the documented SQL to confirm BM.IsActive = 1 and interpret the Permissions bitmask to determine Agent or Store status.