Team, permissions and security in Bruxel: who sees and who changes what

By Manuel Mattar3 min read

In short

In Bruxel, each organization is a separate space with its own catalog, balance and team. Five roles decide how much each person can decide and spend, scopes limit a viewer or an editor to part of the catalog and the audit log records every relevant action, with two-step verification through an authenticator app.

The problem it solves

On many catalog teams everyone is an admin, or they share one user, because nobody had time to think about permissions. It works until the day someone deletes a hundred products by mistake, an intern spends the balance generating descriptions or a supplier sees another supplier's products. The question isn't whether you trust your team, but whether each person has only what they need for their job.

Organizations: two spaces that share nothing

Everything you do in Bruxel lives inside an organization. Two organizations share absolutely nothing: if you belong to two, you have two catalogs, two balances and two teams. The only thing that follows you everywhere is your personal account: your email, your password, your second factor, your language and your theme. Your role is also per organization: you can be an owner in yours and an operator in another.

Five roles, each including the one before

The difference between roles isn't how much work someone does, but how much they can decide and how much they can spend:

  • Viewer: sees the whole catalog, comments on product pages and saves private views. Changes no data.
  • Editor: also creates products and changes their content by hand: values, texts, images, category and tasks. Doesn't spend credits, import, download or delete.
  • Operator: also imports, generates with AI (spends credits), downloads, deletes and defines attributes, families, categories and channels. Doesn't approve or publish content.
  • Admin: also approves and publishes, invites and removes people, and manages API keys and webhooks.
  • Owner: also grants and removes the owner role.

The two lines used most: an editor writes without spending balance, and an operator produces but doesn't approve what they generated. An organization always keeps at least one owner; the database guarantees it, not the screen.

Scopes: a part of the catalog for each person

A scope limits a viewer or an editor. For reading, checking categories, families or brands makes that person see only those products; the rest don't exist for them. The brand scope is a supplier's: they see and edit only their brands' products. For writing, checking attribute groups lets them see the whole product page but write only the attributes in those groups; the rest show a lock, and if they try to write them the server rejects it. Setting or removing a scope is for admins and is recorded in the audit log.

Security for each account

From Account → Security you change your password (at least 12 characters, with uppercase, lowercase, a number and a symbol) and turn on two-step verification with an authenticator app. Changing your sign-in email requires a code sent to the new address. When you sign out, that session stops working immediately on the server side. The organization's audit log records who invited someone, who changed settings, who approved content and who bought credits. API keys are created and revoked by an admin, and are shown only once.

How to get started, step by step

  1. An admin or owner goes to Account → Team, types the person's email and picks their role: viewer, editor, operator or admin.
  2. The person opens the link and signs in with the same email they were invited with. The link is shown once and expires after 7 days: treat it like a password.
  3. If they should see or write only one part, the admin sets a scope on their row in the team list.
  4. Each person turns on their two-step verification.

The team guide has the full roles table, the security guide covers account details, and the team and security module page summarizes what it includes. On the security page we explain how the platform is protected.

Who it is for

For any organization with more than one person, and especially for those working with suppliers or with teams by area. A hypothetical example: a sports store gives its content agency the editor role scoped to the text attribute group, its analyst the operator role and its footwear supplier a scope for its brand.

Honest limits

  • Only a viewer or an editor can be scoped; an operator or higher can't.
  • A product with no category or family falls outside any reading scope: scope after organizing the catalog.
  • API keys aren't scoped: they authorize by permissions.
  • There is no SMS second factor, no list of connected devices and no “sign out everywhere”.
  • You can't create a second organization from the app: you join another one by invitation.

Frequently asked questions

Which role do I give someone who writes but shouldn't spend credits?

Editor. An editor changes the content of product pages, but doesn't generate with AI, import, download or delete. If they also need to produce with AI without deciding what gets published, the role is operator.

Can I make someone see only part of the catalog?

Yes, if they are a viewer or an editor. A scope by categories, families or brands limits what they see, and one by attribute groups limits what they write. An operator or an admin can't be scoped.

Does two-step verification work by SMS?

No. The second factor is always an authenticator app, such as Google Authenticator, Authy or 1Password, which gives you a 6-digit code each time you sign in.

Sources

  1. Role-based access control (Wikipedia)
  2. Principle of least privilege (Wikipedia)
  3. Multi-factor authentication (Wikipedia)

About the author

Manuel Mattar

Founder of Bruxel.AI

In 2014 he founded Wolf Sellers, an e-commerce agency in Mexico City, and later Bruxel.AI, the AI-powered PIM.

See all posts by Manuel Mattar

Try it with your catalog

Create your free account and try Bruxel with your own products using the welcome credits.

Keep reading

Team, permissions and security in Bruxel: who sees and who changes what