Multi-Account Management

The main customer account can maintain separate buyers without creating a separate Magento customer for each employee. Each sublogin gets its own credentials and identity while staying attached to the company account.

What the base package controls

For each sublogin, the available base fields can include:

first and last name;
unique email and password setup;
store context;
active and expiry state;
email and newsletter preferences;
permission to manage other sublogins;
selected parent addresses;
allowed payment and shipping methods.

Installed add-ons contribute their own fields, such as role, group, budget, approval threshold or catalog assignment.

Delegate account management carefully

The main account can allow a sublogin to create and manage other sublogins. The global Default Value Can Create Sublogins is off, which is a sensible default for ordinary buyers.

When delegated management is needed:

grant it to a small number of named team leads;
decide which frontend mass actions they may use;
test whether add-on fields are visible and editable as intended;
keep account activation and deletion aligned with your offboarding process.

Base accounts are flat

The base package attaches sublogins directly to the main customer. Hierarchical groups and reusable roles require mageb2b/sublogin-role.

A common structure with that add-on is:

Main customer account
└── Operations
    ├── Procurement
    └── Warehouse

The hierarchy can also support approval routing when Order Approval is installed and group approval is enabled. It does not create arbitrary amount-based approval tiers.

Offboard a buyer

Deactivate access before deleting a record. Historic orders retain the sublogin association and use the configured fallback label if the record is later removed. Check reports, exports and integrations before permanent deletion.

For a person who should become an independent Magento customer, use the reviewed Transform Accounts workflow in staging rather than manually moving identifiers.