First setup

Invite your team

Get your own colleagues into the Cockpit — and why that is a different thing from your customers' buyer accounts.

Cockpit users are the people at your company who administer the platform: product management, sales support, marketing, whoever maintains prices. This page is about them.

Two completely separate populations. Cockpit users work for you and log in at app.revenexx.com. Your customers' buyers work for someone else, log in to your storefront, and are managed as Contacts and roles under their organisation in Commerce Studio › CRM. Never create a Cockpit user for a customer — it would give them access to every price and every other customer's data.

Before you begin. You need to be able to reach Settings › Team. Have each colleague's business email address ready — the invitation goes there and nowhere else.

Invite someone

Go to Settings › Team.
Select Invite member.
Fill in Given name, Family name and Email. Use the real name; it is what your colleagues see next to changes across the Cockpit.
Set the Preferred language — this decides which language their Cockpit opens in and which language the invitation email is written in.
Select Send invitation.

They receive an initialisation email and set their own password from it. You never see or set a password for anyone, and you should not ask for one.

Watch the status, not the invitation

The Team list shows each person's state, and you can filter by it:

Status	What it means	What to do
Invited	The email went out; they have not activated the account	After a few days, Resend invitation
Active	Signed in and working	Nothing
Suspended	Blocked from signing in, record kept	Reactivate when they return
Locked	Locked out, usually after failed sign-in attempts	Ask them to reset, or reactivate

When someone leaves

Open the person from the Team list and use Suspend under Account state. That blocks sign-in immediately while keeping the user record, so the audit trail of what they changed stays readable.

Remove from organisation is permanent. It deletes the person's record in the identity provider, and it is not the same as suspending. Use it only when you are sure — for a departure, for a long absence, or while you work out what should happen, Suspend is the right answer.

Roles and what people may do

Inviting someone gets them into the Cockpit. Deciding what they may do once inside — which apps, which data, which actions — is a separate subject, and it is worth doing deliberately rather than giving everyone everything. See Users, roles and permissions.

If your company already runs Active Directory or Azure AD, you can federate sign-in instead of maintaining accounts here, which means leavers lose access the moment IT disables them centrally. See Single sign-on.

What to check

The new person appears in Settings › Team with status Invited, and moves to Active after they follow the email.
They can reach the Studios they need in the icon rail.
No customer contact has appeared in this list. If one has, remove it and create the person as a contact under their organisation instead.

If the invitation does not arrive

Check the address for a typo — the invitation goes to exactly what was typed.
Ask them to check their spam folder. Automated mail from a new sender domain is a classic casualty of corporate filtering.
Use Resend invitation from their entry in the Team list.
If several invitations are disappearing, it is a mail-delivery problem rather than a Cockpit one. See Notifications and email.

Create products: the first real thing in the tenant.
Guide: Users, roles and permissions in the Administration book.
Product Help: the Team screen.

Edit this page

First setup

Six short walkthroughs that put one real thing each into your tenant, in the order that works.

Create products

One real product by hand, from your own catalog, so the data model shows you what it needs before you import eight thousand rows.