All courses

Team

How to add people to your organization and what each one can do based on their role.

Video transcript

In this video, you'll add someone to your organization and choose their role.

From Team, you type the person's email and choose the role they join with.

Below, the screen tells you what that role can and can't do.

They get an invitation by email; the link lasts seven days and works only once.

There are five roles: viewer, editor, operator, administrator and owner. Each can do what the one before can.

An editor changes content without spending credits; an operator does spend, but doesn't approve or invite.

If the invitation is no longer needed, you revoke it; and you remove a member from their row.

In the next video, you'll limit a person to part of the catalog.

How to invite someone

From Account → Team you enter the person's email and choose the role they join with. Bruxel sends them an invitation with a link; when they open it and sign in, they're part of your organization.

Inviting can be done by an administrator or an owner. No other role can.
When inviting you choose between viewer, editor, operator and administrator. The owner role can't be granted in an invitation: it's assigned afterwards, and only by another owner.
The person must accept with the SAME email you invited. If they sign in with a different one, the invitation doesn't apply.

The invitation link is shown only once and expires after 7 days. Treat it like a password: whoever has it gets into your organization, so don't paste it in a public channel. If it's lost or expires, revoke the invitation and create a new one.

What each role can do

There are five roles and each one includes what the previous one can do. The underlying difference isn't how much work someone can do, but how much they can decide and how much they can spend.

Role	Can	Cannot
viewer	See the whole catalog, the history and past downloads; comment on products and save private views.	Change any data: not a value, not a text, not an image.
editor	Everything a viewer does, plus creating products and changing their content: values, manual text, images, category, family, links and tasks.	Spend credits (generate, translate, AI-fix, the Studio), import, download, delete, or define attributes, families, categories or channels.
operator	Everything an editor does, plus importing the catalog, generating descriptions and using AI (spends credits), buying credits, downloading, deleting, defining attributes, families, categories and channels, submitting content for approval and requesting invoices.	Approve or publish content, invite or remove people, or touch the organization's settings.
admin	Everything an operator does, plus approving, rejecting and publishing content; inviting and removing people; tax and organization details; API keys, webhooks, the low-balance alert and buying image storage.	Touch an owner: neither remove them, nor change their role, nor promote anyone to owner.
owner	Everything an administrator does, plus granting and revoking the owner role.	—

The two lines you'll use most day to day. An editor changes content but does NOT spend credits: if you want someone to write and fix without burning your balance, that role is editor. And an operator does spend, but does NOT approve their own work: if you want someone to produce without deciding what gets published, that role is operator.

Organization owners

Only an owner can grant or remove the owner role. An admin can't promote themselves or anyone else, even though they can invite and remove people.

An organization must always keep at least one owner. That's not enforced by the screen but guaranteed by the database: if you try to remove the last owner or lower their role, the operation is rejected. This is deliberate, so an organization is never left without anyone able to administer it.

Removing someone

From the same screen. An administrator can remove anyone except an owner; removing an owner requires being an owner. Access is cut immediately.