Staff accounts & permissions

Add teammates to your store and give each one the right level of access. Every person signs in with their own Sellerlane account — never share one login. You pick an access level when you invite them, and Sellerlane translates that into a precise set of permissions behind the scenes.

You manage your team under Settings → Users & Permissions.

Roles vs. access levels

There are two layers, and it helps to keep them straight.

• Role is the underlying authority: every store user is either an Admin or Staff. Admins bypass the permission map entirely — they can manage staff, payments, domains, checkout, settings, products, events, schedules, and all store data. Staff can only do what their permissions allow.
• Access level is the label you choose at invite time — one of eleven presets (plus a special Custom state). Picking the Administrator preset sets the role to Admin; every other preset is a Staff role with a curated permission set.

So there is no separate “Owner” tier. The person who created the store is simply the first Admin. Any Admin can be removed or demoted as long as one other Admin remains — Sellerlane blocks the action that would leave the store with no admins.

The eleven access-level presets

When you invite someone, you choose the preset closest to their job. Each preset bundles a fixed list of permissions.

Preset	Role	What it covers
Administrator	Admin	Full access to the store, staff, billing-sensitive settings, and every operational area.
Store manager	Staff	Runs day-to-day store operations without staff administration.
Operations	Staff	Manages products, customers, orders, fulfillment, shipping, and POS workflows.
Fulfillment	Staff	Handles order fulfillment, returns, refunds, customer lookup, and shipment work.
Merchandiser	Staff	Manages catalog, collections, media, search merchandising, bundles, and discounts.
Content editor	Staff	Manages pages, blogs, menus, policies, media, and storefront content.
Marketing	Staff	Manages campaigns, discounts, customer segments, review programs, pixels, and reports.
Analyst	Staff	Read-only access to reports and the operational data needed to interpret them.
Support	Staff	Supports shoppers with customer profiles, orders, gift cards, returns, and refunds.
Developer	Staff	Manages theme code, checkout setup, domains, pixels, and metafield infrastructure.
Booking manager	Staff	Manages service hosts, schedules, booking availability, and event assignments.

Tip

Day-to-day work rarely needs Administrator. A Fulfillment teammate can pack, ship, and refund orders but can’t touch prices, themes, payments, or your domain — least-privilege access is cheap insurance.

Inviting a team member

1. Go to Settings → Users & Permissions and select Add New User.

2. On the Add store user screen, enter the teammate’s email address.

3. Choose one access level preset. The right-hand panel previews the exact permissions that preset includes, so you can confirm before sending.

4. Select Send invite.

What happens next depends on whether the email already belongs to a Sellerlane seller:

• New to Sellerlane — Sellerlane creates the account and emails a temporary password. They sign in and are prompted to set their own password on first login.
• Existing seller — they receive an email letting them know they were added to your store. They sign in with the password they already have.

Note

You invite by email, not by username. The invite is tied to that email address — if a teammate later changes their email, re-invite them at the new address.

Permissions reference

Under the hood, each access level grants permissions drawn from a set of thirty. They are organised by area, and most areas split into a View permission and a Manage permission.

Area	Permissions
Store settings	View store settings, Manage store settings
Staff	Manage staff
Products	View products, Manage products
Orders	View orders, Manage orders
Customers	View customers, Manage customers
Content	View content, Manage content
Themes	View themes, Manage themes
Marketing	View marketing, Manage marketing
Discounts	View discounts, Manage discounts
Analytics	View analytics, Manage analytics
Reviews	View reviews, Manage reviews
Shipping	Manage shipping
Taxes	Manage taxes
Payments	Manage payments
Domains	Manage domains
Checkout	Manage checkout
Pixels	Manage pixels
POS	Manage POS
Bookings	Manage bookings and schedules
Custom data	Manage custom data

How permissions imply each other

A Manage permission automatically grants the matching View permission — you can’t manage orders without being able to see them. A few cross-area implications also apply: granting Manage pixels implies View marketing, Manage bookings implies View products, and Manage custom data implies View content. Because of this, the permission list shown on a preset is the expanded, effective set.

Caution

Some permissions are sensitive by design. Manage staff, Manage payments, Manage domains, and Manage checkout are not bundled into the everyday presets like Operations or Fulfillment — they live in higher-trust presets (Store manager, Developer) or are reserved for Administrators. Hand them out deliberately.

The Custom access level

Custom isn’t a preset you pick from the invite screen. It appears automatically when a user’s permission set doesn’t exactly match any of the eleven presets — for example, after you fine-tune an existing teammate’s permissions. It’s a label that says “this is a hand-tuned set,” not a starting point you assign directly.

Editing and removing users

Open Settings → Users & Permissions, then choose a user to view their profile. From there you can change their access level and permissions, manage booking-host settings (see below), or remove them.

A few rules protect your store:

• Only Admins can change or remove other Admins. Staff with staff-management access can manage other staff but can’t touch Admin accounts.
• Non-admin staff can’t grant Admin access or promote anyone (including themselves) to Admin.
• Sellerlane refuses to remove or demote the last remaining Admin — promote someone else to Admin first.

Removing a user revokes their access to that store immediately. They keep their Sellerlane account (and access to any other stores they belong to); they simply no longer appear in your team. Removal is keyed to the user’s email address.

Booking managers and service hosts

If you sell event bookings or appointments, the Booking manager preset — and the booking-host settings on each user — let you run a roster of people who deliver those sessions.

Open a user’s profile to configure them as a host:

1. On the General tab, connect the host’s Zoom or Google Calendar account so booked sessions generate meeting links and respect their calendar. (Connecting requires the relevant OAuth client to be configured for the store; if it isn’t, ask a store Admin.)

2. Mark a user as the Default Host to receive bookings that aren’t assigned to a specific person. Only one user can be the default at a time.

3. Use the Availabilities tab to set the host’s weekly working hours, breaks, and blocked dates.

4. Use the Global Buffer tab to add padding before and after every booking, so back-to-back sessions don’t collide.

For how these hosts and schedules connect to your bookable products, see the event bookings guide.

What Sellerlane does not have yet

To set expectations honestly:

• No staff two-factor authentication. There’s no TOTP/2FA setup for seller accounts today. Encourage strong, unique passwords and remove access promptly when someone leaves.
• No “collaborator” / external-partner accounts. Everyone you add is a full store user invited by email — there’s no separate request-access flow for agencies or developers. Use the Developer preset for technical partners and the Custom permission set if you need to narrow it further.

Next steps

Payments

Decide who should hold the sensitive Manage payments permission. See Payments.

Event bookings

Set up hosts, schedules, and availability in Event bookings.

Themes & editor

Give designers theme access without exposing orders — see Themes & editor.

Custom domains

The Manage domains permission controls who can change your store’s address. See Custom domains.