Database Reference

Sublogin creates additional users beneath a Magento customer account. Orders and the commercial customer relationship remain with the main customer, while each sublogin can receive its own permissions, addresses, payment methods and optional add-on assignments.

Sublogin ownership and restrictions

Relationship	Why it matters
`customer_sublogin` belongs to one `customer_entity`	Keeps every additional user under the correct company customer account.
`customer_sublogin_address` links one `customer_sublogin` with one `customer_address_entity`	Limits the customer addresses available to that user.
`customer_sublogin_payment` belongs to one `customer_sublogin`	Restricts the payment methods the user may select.
`customer_sublogin_shipping` belongs to one `customer_sublogin`	Restricts the shipping methods the user may select.
Magento wishlist and API token records can belong to one `customer_sublogin`	Keeps user-specific shopping and API activity distinct within the main account.

Budget add-on

Relationship	Why it matters
`customer_sublogin_budget` can belong to one `customer_sublogin`	Applies a budget directly to an additional user.
`customer_sublogin_budget` can belong to one `customer_entity` and one `store_website`	Supports account-level budgets with website-specific periods and currency context.

Custom Catalog add-on

Relationship	Why it matters
A sublogin product assignment links one `customer_sublogin` with one `catalog_product_entity`	Provides a direct product allowlist for an individual user.
A sublogin catalog product assignment links one catalog with one `catalog_product_entity`	Builds a reusable catalog for several sublogins.
A sublogin catalog customer assignment links one catalog with one `customer_entity`	Keeps the catalog under the correct company account.
A sublogin catalog assignment links one catalog with one `customer_sublogin`	Reuses the same curated product set for selected additional users.
Catalog assignments belong to one `store`	Allows access to vary by Store View.

Role add-on

Relationship	Why it matters
`customer_sublogin_role` can belong to one `customer_entity`	Keeps reusable roles private to the company account that created them.
`customer_sublogin_role_permission` belongs to one `customer_sublogin_role`	Defines what users assigned to the role may do.
`customer_sublogin_group` can belong to one `customer_entity`	Organizes additional users within the same company account.
`customer_sublogin` can belong to one role and one group `customer_sublogin_role` and `customer_sublogin_group`	Applies reusable permissions and organization to each user.

Passwords, tokens and internal version records are deliberately excluded. Use the customer account, Admin screens or service contracts so permissions and cache invalidation remain consistent.