<?xml version="1.0"?>
<doc>
    <assembly>
        <name>Wingman.Shared</name>
    </assembly>
    <members>
        <member name="T:Wingman.Shared.Authorization.UserEmailUniquenessLane">
            <summary>
            Separates Identity normalized email storage so the same mailbox can exist once as an Admin account
            and once as an Operator / custom-role account (<c>|A</c> vs <c>|O</c> suffix on normalized email).
            </summary>
        </member>
        <member name="F:Wingman.Shared.Authorization.UserEmailUniquenessLane.Legacy">
            <summary>Existing users before lane suffix was introduced (normalized email has no <c>|A</c>/<c>|O</c> suffix).</summary>
        </member>
        <member name="F:Wingman.Shared.Authorization.UserEmailUniquenessLane.Admin">
            <summary>Admin-role account; normalized email is stored as <c>{NORMALIZED}|A</c>.</summary>
        </member>
        <member name="F:Wingman.Shared.Authorization.UserEmailUniquenessLane.OperatorOrRole">
            <summary>Operator or operator-scoped custom role; normalized email is <c>{NORMALIZED}|O</c>.</summary>
        </member>
        <member name="M:Wingman.Shared.Authorization.UserEmailUniquenessLane.FromCreateRoleName(System.String)">
            <summary>
            Lane used when registering via create-user API. Only explicit Admin role uses the admin lane;
            everything else (including default Operator) uses <see cref="F:Wingman.Shared.Authorization.UserEmailUniquenessLane.OperatorOrRole"/>.
            </summary>
        </member>
    </members>
</doc>
