Admin
Placeholder added · 4 October 2026.
admin/public/contains a static holding page.make devserves it on port 4141; the future combined Docker image can serve the same files through nginx. Authentication and platform administration are not implemented.
The admin panel is the planned place for whoever operates Store Deputy itself — not for shop owners. A holding page exists; functional screens remain future work.
Three things called admin
The word is used for three different things in this project. Only the third is this part.
| Name | What it is | Where it lives |
|---|---|---|
| The OpenCart admin panel | The shop's own back office, where the owner installs the module and presses Connect | In the shop. Store Deputy does not replace it |
| The admin role | A team role between owner and member. An admin may connect stores and invite people; an admin may not change roles, remove an owner or delete the team | In the API, built |
| Admin, this part | A panel for the people who operate the platform | Not built |
What exists today
- A reserved port. 4141 is set aside for it on a developer's machine. The static preview listens there during
make dev. - An allowed origin. The API's example configuration already lists that address among the browser origins it accepts.
- An unused field. Each person's record can hold a platform role. No API route grants it and no rule checks it, so today it gives nobody anything.
What CleanSlice says
CleanSlice lists admin/ beside api/ and app/ as an optional admin panel built with Nuxt. It has no separate standard for it: a search of the CleanSlice documentation scoped to the admin panel returned only the Nuxt standards. So an admin panel would follow the same rules as the app: slices as Nuxt layers, setup slices for plumbing, provider components, Pinia stores and an API client generated from the API's description.
The sibling Agentfy repository has an admin panel built this way. That is a precedent to look at, not a decision that applies here.
To decide before building
- What an operator needs to do first. No list of operator tasks exists. Inventing screens before there is a platform to operate would be guesswork.
- How someone becomes an operator. Nothing grants the platform role today.
- Whether operators sign in with the same accounts as shop owners.
- What an operator may see of a team's stores. The product's promise is that the owner holds authority over their shop; see Authority and recovery.