minipim is built to run more than one catalog. Agencies run one per client; brands run one per business unit. Each is an organization, and one login can belong to as many as you need, with a switcher in the sidebar.
Invite your team
On the Members page, add someone by email. If they already have an account they’re added straight away; otherwise minipim creates an invitation with a link you can copy, and on Hosted an invitation email goes out too. Admins manage who’s in each organization, and anyone can leave one they no longer need.
API keys for everything else
Scripts, CI jobs, storefronts and AI agents authenticate with API keys. Create one on the API keys page and give it a name; the full key is shown once and stored only as a hash, the list shows a prefix so you can tell keys apart, and you can see when each was last used and revoke it at any time. A key belongs to one organization, so it can never read another’s data.
Isolation you don’t have to trust the app for
Every catalog table in minipim carries the organization it belongs to, and Postgres row-level security enforces the boundary inside the database itself. Even a bug in application code can’t return one organization’s products to another.
Good to know
- Keep API keys server-side; they aren’t meant for browsers.
- Hosted accounts sign in through our managed login. Self-hosted APIs accept JWTs from any OIDC provider.