A staged workflow across teams

In this video, your catalog moves through several teams: each writes its part and works its queue.

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.

A scope limits a viewer or an editor to part of the catalog; you set it from their row, with “Scope”.

For reading: categories, families or brands. The person only sees those products; it's a supplier's scope.

For writing: attribute groups. They see the whole record, but only write the attributes in their groups.

Each team has its queue: the filters for its share, here the incomplete clothing.

In “Views”, “Save the current view” gives a name to that way of looking at the catalog.

It starts private; if you share it with the organization, it shows up in everyone's menu.

The button tells you which view is on.

A task says a product belongs to someone: a person and, if you want, a note and a due date.

You select the products and assign them in one go; whoever gets them sees it in their bell.

On the other side, “My tasks” leaves only their products, sorted by due date.

“Done” closes the task and the counter drops right away; closed tasks are kept.

Type @ and pick someone: they get a notification in the bell, with a link to this comment.

A comment stays pending until someone resolves it; resolved ones fold away and can be reopened.

That's a staged workflow: each team writes its part, sees its queue and they talk on the record.