Roles and access
The three user roles, which screens each one sees, and what each can change.
Every portal login has one of three roles. The role decides which screens a person sees and what they can change. The NC Access Matrix is the source of truth for these rules; this page summarizes it.
The three roles
| Role | Who | In short |
|---|---|---|
| NC Super Admin | Sean and the OpsKings team | Everything, on every account. The only role that manages client connections and users. |
| NC Internal User | Other National Commerce staff | The brand-facing screens plus the internal ops screens, on their assigned accounts. |
| Client User | Brand team members | The brand-facing screens, read-only, on their assigned accounts. |
A few rules apply to all of them:
- One role per person. A person has the same role on every account they are assigned to. The role is not picked per account.
- Accounts. Every role except NC Super Admin sees only the accounts assigned to it. Super Admins are on every account, including new ones.
- NC Super Admin is set in the database only. No screen offers it as a choice.
- Client User is the default. A new invite is a Client User unless the Super Admin picks NC Internal User.
Screens by role
R means read-only. A dash means the screen is hidden and its data is refused, even from a direct link.
| Screen | Super Admin | Internal User | Client User |
|---|---|---|---|
| Dashboard, Product Analysis | R | R | R |
| Replen Report, Inventory Snapshot, Inventory Forecast | R | R | R |
| Products | Edit | Edit | R |
| Reorder Point Settings | Edit | Edit | R |
| Purchase Orders | Edit | Edit | R |
| Draft POs and Push to ShipHero | Edit | Edit | - |
| Receiving Discrepancies | Edit | Edit | R |
| Shipments, Zone Analysis | R | R | R |
| Exclude from metrics toggle (Shipments) | Edit | Edit | - |
| Replenishment Accounts | Edit | Edit | - |
| Replenishments | Edit | Edit | R |
| SKU Sync | Edit | Edit | - |
| Product Categories | Edit | Edit | R |
| Security | Own sessions | Own sessions | Own sessions |
| Notifications | Own alerts | Own alerts | - |
| Client Connections | Edit | R | - |
| Users | Edit | R (list only) | - |
Exports stay available to every role that can see the data.
NC staff can switch an order's Exclude from metrics toggle on the Shipments list. Client Users never see it, but flagged orders drop out of their numbers too.
On Replenishments a Client User sees only their own accounts, without draft POs, the status timeline, or the request snapshot. See What brands see.
A brand's replenishment request link sits outside these roles: it needs no login, and the link itself is the access. Brands also find it on the replenishment's Replenishment Request tab. Its History tab only appears for someone signed in as NC staff.
Super Admin only
Some actions on screens Internal Users can edit stay with the Super Admin:
- Deleting a synced purchase order and queueing its re-import. Internal Users can still delete a draft.
- Resetting a classified SKU in SKU Sync.
- Pushing a SKU back to the sync queue from Reorder Point Settings. It deletes the SKU, so it counts as a hard delete.
- Everything that changes a client connection or a user.
Internal pages
NC staff keep one sidebar with every page, in the usual groups and order. A page brands can never open (every "-" in the Client User column above) carries an orange Internal badge, both in the sidebar and next to the page title. When every page in a sidebar group is internal, the badge sits on the group instead. Under the logo, staff see Master view · all pages.
Today the internal pages are Replenishment → Accounts, and Settings → Notifications, Client Connections, SKU Sync, and Users. Reorder Point Settings, Purchase Orders, and Replenishments and the Replen Report in the Replenishment group are brand-facing, so they carry no badge.
The badge comes from the same rule that blocks Client Users, so it can't disagree with real access. Client Users see no badges and no label.
Preview as client
NC staff can check exactly what a brand sees with Preview as client in the page header. It shows the portal as that client's Client User sees it, until staff exit. See Preview the portal as a client for the steps.
- Who can preview whom. NC Internal Users can preview their assigned accounts. Super Admins are on every account, so they can preview any client.
- What it shows. That client's Dashboard first, then the Client User sidebar, with no badges, and only that client's data on every screen. Draft POs stay hidden, as they are for the client.
- Read-only. Create, edit, and delete actions are hidden, and the server refuses any change a Client User couldn't make. On Security you see your own sessions, without the sign-out buttons.
- The way out. A bar at the top reads "Previewing as [client]" with an Exit preview button, and the sidebar label reads "Client preview · [client]". Exit returns you to the page you started from, with the badges back.
The preview belongs to your browser, so every tab shows it until you exit. Signing out ends it too. Client Users never see the button.
Alerts
Client Users never get alert emails, and the Notifications screen is hidden from them. The alert flows skip Client Users when they pick recipients, so a stored preference can't turn alerts back on. See Notify: PO Line Item Discrepancy and Notify: Shipment Cost Exceeded.
Changing someone's role
Only a Super Admin changes users. They pick the type when they invite someone, and can switch it later on the user's page. A switch applies to all of the person's accounts and shows up on their next page load.
How it is enforced
The app checks the role in three places:
- The middleware refuses a screen the role may not open, before the page loads.
- Each page checks again on the server.
- Each API route and server action checks the role before it reads internal data or changes anything. This is the check that counts. Hidden buttons only tidy up the screen.
During a preview all three checks treat staff as a Client User, and every read is pinned to the previewed account on the server. A preview is honored only for NC staff on an account they are assigned to, so it can only ever narrow what someone sees.
The Claude MCP connector keeps its own check: NC and OpsKings staff only.
Related
- Settings: the Users, Client Connections, and Notifications screens.
- Invite and manage users: add people and set their type.
- Preview the portal as a client: check what a brand sees.
- Users & Access: the tables behind roles.