A parts database is usually shared. Engineers, lab and production staff, and outside partners all need to see the same stock and the same BOMs. Every commercial PartsBox plan is multi-user, and every change is synchronized in real time: add a part, remove stock, or edit information, and it appears for everyone else who is logged in, with nothing to refresh.
Each organization starts with one admin. Admins add other users up to the plan's limit, and beyond it for an extra per-user charge. Any PartsBox account holder can be invited, at one of three levels:
For finer control than these three levels, the Control plan adds Role-Based Access Control, where you define roles with specific permissions and assign them to users.
The data is shared; the way each person works with it is not. Everyone sees the same parts, stock, and projects, while language, date format, and personal table presets are per user — one engineer works in German with their own column layout, a colleague in Japanese with another, on exactly the same database. Company-wide presets let one person define the views the whole team shares.
Changes carry their author. Stock history and build records show who did what and when, so "who received this reel" has an answer. API keys work the same way: each is its own named user with a role, without counting toward the user limit, so the receiving station and the test rig are separate, accountable identities.
A PartsBox account belongs to one person and must not be shared. A shared or departmental account gives you no security, no way to revoke one person's access, and no way to know who actually did something, so PartsBox does not allow them. If you need access for more people than your plan covers, buy additional user slots.
Multiple users start on the Essentials plan. The free Maker plan is single-user.