Organization-bound accounts
Credentials open only the organizations assigned to that account.
Commission operations for independent uplines
Your team. Your payout account.
Each upline signs in to a private calculator. Team data and payout rules stay behind the account boundary.
Private by defaultServer-enforced access
Payout AtlasAccess boundary
Closed by defaultSigned-in identityUpline accountThe browser does not choose an organization.
SessionVerified on the serverPass
MembershipMatched to an assigned workspacePass
ResponsePrivate workspace only
Built for more than one upline
One front door. No shared workspace.
Every account opens only its assigned organization. The server decides what data is returned, never a browser setting or edited URL.
Open the account loginAccountupline.owner
Server membership
AuthorizedAssigned workspaceOnly membership-scoped data returned
Not returnedOther organizationsNo hierarchy or rates exposed
Inspect the page. The private data is not there.
Security comes from withholding protected information until the server verifies both the account and its organization membership.
Account sign-inCredentials checked→
Secure sessionHTTP-only cookie→
Membership checkServer enforced→
Workspace responseAssigned data only
What stays private
The public site never receives a team model.
Agent rosters, hierarchy, rates, calculation rules, and results are loaded only after an authorized account opens its assigned workspace.
Server-only rulesAccount-scoped accessNo public samples
Isolation is part of the calculation.
A result is trustworthy only when it comes from the right organization's protected rules.
No public team model
Agent names, hierarchy, rates, and results stay inside an authorized workspace.
Server-side calculation
The browser sends approved inputs. Protected rules and hierarchy are resolved on the server.
Separate configurations
One organization's rules never become another organization's defaults by accident.
Ready when the payout question starts.
Sign in