Admin panel overview
How the SeedWebs admin panel is laid out, the vocabulary it uses, and the four reasons a menu item might be missing from your site.
Last updated 2026-10-09
This page maps out the admin panel: what the sections are, where they live, and what the words mean. If you are brand new, read Getting started first, then come back here for the full map.
Where the admin panel is
It lives at {slug}.seedwebs.app/admin/, where {slug} is your site’s name on the platform.
The admin panel runs on the .seedwebs.app address only. If you have connected your own domain (see Your own domain), you can still type yourdomain.com/admin/: it forwards you to {slug}.seedwebs.app/admin/, and you sign in there.
The parts of the screen
The screen is a sidebar on the left and a content area on the right.
| Part | Detail |
|---|---|
| Top of the sidebar | Favicon (or the first letter of your site name) + site name + tag line. Clicking it opens the live site in a new tab. |
| Collapse button | The circled-arrow icon in the corner of that header. Collapses the sidebar to icons only; remembered in your browser. |
| Sidebar | Every menu item. Click a heading to expand its sub-items. |
| Bottom bar | Your avatar, name and role. Click to open the user menu. |
| Mobile menu button | The hamburger icon at the top right, which shows and hides the sidebar. |
The user menu at the bottom holds four things:
- Edit Profile, at
/admin/profile - Admin theme: Light / Dark / System
- Admin language: EN or ไทย. Stored in the browser you are using, so it does not follow you to another machine
- Log out
If your site is on the trial plan, a yellow “Beta preview / pre-launch access” bar sits under the sidebar header.
Dashboard
/admin/dashboard is always the first item, and every role can see it. It holds:
- Analytics — a 7 days or 30 days range, total views split into Desktop / Mobile, and a daily bar chart
- Top Pages and Top Referrers — the top 8 for the range
- Recent Activity — the 5 most recent entries, with a More link to the full Activity page
- An AI Content button, which appears once an AI API key is saved under Settings → General → AI Features
The sidebar, in its real order
- Dashboard
- Every content group, in the order set under Settings → General → Admin Menu
- Store, if enabled
- Tools
- Settings
The Logs group counts as one row in the Admin Menu list, so you can drag it in among the content groups. Store has a row in that list too, but in the sidebar it always sits after the content groups no matter where you drag it. Tools and Settings are not in the list at all, so they cannot be reordered and are always last.
A newly created site shows only Dashboard · Pages · Posts · Media · Logs · Tools · Settings. Everything else starts switched off.
Content groups and their sub-items
| Group | Sub-items | Main URL |
|---|---|---|
| Pages | All Pages · Add Page · Structure · Templates | /admin/pages |
| Posts | All Posts · Add Post · Categories · Tags · Authors · Author Categories | /admin/posts |
| Media | All Media · Folders | /admin/media |
| Sliders | All Sliders · Add Slider | /admin/sliders |
| Forms | All Forms · New Form · Entries · Form webhooks | /admin/forms |
| Docs | All Docs · Add Doc · Structure · Templates | /admin/docs |
| Events | All Events · Add Event · Categories | /admin/events |
| Books | All Books · Add Book · Categories | /admin/books |
| Staffs | All Staff · Add Staff · Categories | /admin/staffs |
| Members | All Members · Signup Form · Login Settings | /admin/members |
| Newsletters | All Newsletters · New Newsletter · Subscribers · Interests | /admin/newsletters |
| Tours | All Tours · Add Tour · Categories · Bookings | /admin/tours |
Everything from Docs downwards in that table is hidden on an ordinary site — see Why a menu item is missing at the end of this page.
What visitors submit through every form is collected under Forms → Entries (/admin/forms/entries); a single form’s entries open from its Entries link in the table at /admin/forms.
Importing entries from a CSV
Moving from another site, such as WordPress with Gravity Forms, you can bring the old entries into the matching form. Open that form’s entries (its Entries link at /admin/forms) and press Import CSV, next to Export CSV. The button appears for Super Admin and Admin only.
- The file uses the same columns as Export CSV:
Submitted at(the entry’s date),Status,Page URL, and one column per field, headed by the field’s label or its name. Any other column is ignored. A file you exported from a form imports straight back into a form with the same fields. - Before anything is saved you see how many rows were found, which column goes to which field, which columns are ignored, which fields have no column (they are stored empty), and the first three rows.
- Nothing is sent. An import sends no notification email, no auto-reply to the person who filled the form in, and nothing to your form webhooks.
- Each entry keeps the date in
Submitted at. Write it in UTC as2024-05-01 09:30:00, or in ISO form such as2024-05-01T16:30:00+07:00. A row whose date cannot be read, or lies in the future, is not imported and is listed with its row number. A row with no date gets the time of the import. - A row with no status is filed as read, so old entries do not crowd the new count.
- Importing the same file twice is safe. A row whose submitted time and answers match an entry already on the form is skipped and counted as already there. A row with no date cannot be matched this way, because it gets a new time on every import.
- An answer for a question the form no longer has is kept on the entry, where the entry page shows it, but it does not appear in Export CSV.
- When it finishes you see how many entries were imported, how many were already there, and which rows could not be imported, with the reason.
Settings, Tools, Logs and Store are four separate places
All four are top-level groups in the sidebar. None is nested inside another. The common mistake is the address of Tools and Logs: they are /admin/tools/ and /admin/logs/, a different family from /admin/settings/.
Settings, at /admin/settings/*
Configuration for the site itself. Opening plain /admin/settings takes you to General.
| Item | URL |
|---|---|
| General | /admin/settings/general |
| Site status (maintenance mode, coming soon — see Maintenance mode and coming soon) | /admin/settings/site-status |
| Themes | /admin/settings/themes |
| Code | /admin/settings/code |
| Menus | /admin/settings/menus |
| Banners | /admin/settings/banners |
| Cookies | /admin/settings/cookies |
| Chat Buttons | /admin/settings/chat-buttons |
| Marketing | /admin/settings/marketing |
| Payments | /admin/settings/payments |
| Users | /admin/settings/users |
Settings → Payments configures the payment gateways and tax mode for tour bookings. The store’s gateways are a different page, at Store → Payment.
Tools, at /admin/tools/*
Data and system jobs. Opening plain /admin/tools takes you to SEO.
| Item | URL |
|---|---|
| SEO | /admin/seo |
| Redirects | /admin/tools/redirects |
| Import / Export | /admin/tools/import |
| Demos | /admin/tools/demos |
| API Tokens | /admin/tools/api-tokens |
| Connected Apps | /admin/tools/connected-apps |
| Backup | /admin/tools/backup |
| Reset | /admin/tools/reset |
SEO is the first item in this group, but its URL is still /admin/seo, not /admin/tools/seo.
Logs, at /admin/logs/*
Opening plain /admin/logs takes you to Activity.
| Item | URL |
|---|---|
| Activity | /admin/logs/activity |
/admin/logs/email | |
| Conversations | /admin/logs/conversations |
Conversations only appears once an AI API key is saved and the AI chat widget is switched on.
Store, at /admin/store/*
| Item | URL |
|---|---|
| Dashboard | /admin/store |
| Orders | /admin/store/orders |
| Products | /admin/store/products |
| Categories | /admin/store/products/categories |
| Brands | /admin/store/products/brands |
| Attributes | /admin/store/products/attributes |
| Templates | /admin/store/products/templates |
| Coupons | /admin/store/coupons |
| Shipping | /admin/store/settings?tab=shipping |
| Payment | /admin/store/settings?tab=payments |
Old URLs still work
The former addresses of pages that moved to Tools and Logs still open and forward themselves — /admin/settings/api-tokens → /admin/tools/api-tokens, /admin/settings/activity-logs → /admin/logs/activity. Old bookmarks are safe, but worth updating.
An admin URL that does not exist shows a “Page not found” screen with a button back to the Dashboard.
Vocabulary
Pages vs Posts vs Docs
All three store the same kind of content. They differ in how they are grouped and where they live on the site.
| Pages | Posts | Docs | |
|---|---|---|---|
| For | Content that sits still — About, Contact | Content that flows with time — news, a blog | Manuals, reference material |
| Parent/child nesting | Yes (has a Structure page) | No | Yes (has a Structure page) |
| Categories | No | Yes | No |
| Tags | No | Yes | No |
| Author | No field | Primary author + co-authors | No field |
| Address on the site | /{slug} at the top level | /posts/{slug}, with a listing at /posts | /docs/{slug} |
| Automatic listing page | No | Yes, at /posts | No |
Docs have no listing page on the public site; each document is reachable only at its own address. For a table of contents, build a page with the links yourself, or put them in a menu.
Your home page is the page whose slug is home and whose status is Published. Without one, SeedWebs falls back to the first published page. Writing content is covered in Pages and posts.
Theme vs theme part vs template
A theme is your site’s entire look. It lives at Settings → Themes, and one theme is active at a time. A theme has five tabs:
| Tab | Holds |
|---|---|
| General | That theme’s Header, Footer, Global Styles, Global JavaScript and Body Class |
| Nav | The parts that draw the navigation menu |
| Elements | Reusable parts, such as a post card |
| Templates | The page shell for each content type — post-list, post-detail-page, page |
| Emails | Email templates. Only appears when the Newsletters group is enabled |
A theme part is one piece of HTML inside a theme. The kinds are header, footer, element, template and email. Everything shown under the Nav, Elements, Templates and Emails tabs is a theme part.
The word template means two different things in the admin panel. Which one depends on where you are:
| Where | What it is |
|---|---|
| Settings → Themes → a theme → Templates | The HTML shell for a whole content type — every post’s detail page, for instance |
Pages → Templates (/admin/pages/templates) | A named set of fields (plus HTML, if you add any) that you attach to individual pages through the Template field in the page editor |
Docs and Products have their own templates of the second kind, at /admin/docs/templates and /admin/store/products/templates. Details in Themes and templates and Template tags.
Categories vs tags
| Categories | Tags | |
|---|---|---|
| Nesting | Yes, they have parents | No, one level only |
| Used by | Several content types, each with its own separate set | Posts only |
| Address on the site (for posts) | /category/{slug}, or /category/{parent}/{slug} with nested category addresses on | /tag/{slug} |
| Fields | Name · slug · description · image · Icon SVG · parent | Name and slug only |
Each content type’s categories are their own set. Post categories never mix with event categories or product categories. The types with a categories screen are Posts, Events, Books, Staffs, Authors, Tours and Products.
Other words you will meet
| Word | Meaning |
|---|---|
| Slug | The short text used as that item’s URL. Generated from the title, and editable |
| Published | Visible to the public on your site |
| Draft | Visible in the admin panel only |
| Trash | Moved out of the main list, still recoverable |
| Locale / language | An item’s language code — en, th. Each language is its own item, linked to the others as a translation set |
| role | A user’s permissions on the site: super_admin, admin, editor, writer |
Not every content type uses the same set of statuses. Staffs and Members use active / inactive rather than Published / Draft.
Rename a content type
You can give a content type your own name, for example “Staffs” → “Faculty” or “Docs” → “FAQ”.
- Go to Settings → General (
/admin/settings/general), Admin Menu card. - Click the pencil on the row. It appears only on rows your site can see and use, and not on Logs.
- The dialog has one tab per language of your site. Fill in:
- Name — the plural or collective name, used in the sidebar, list headings and “All …”.
- Singular (optional) — used for “Add …”, “Edit …” and “New …”. Left empty, the Name is used. The preview line shows how the admin will read, including a sub-heading such as ”… Categories”.
- Press Done, then Save Settings. Nothing is saved until you press Save Settings.
Reset to built-in in the dialog removes your names for that row. An empty field always means “use the built-in name”, never a blank menu.
The Store row renames two things: the Store section itself and the products inside it.
A name can be at most 40 characters. It cannot contain <, >, {{, }} or hidden control characters.
Where the new name shows
- In the admin: the sidebar, list pages, page headings, “Add …” / “Edit …” buttons and breadcrumbs. The admin uses your name in the admin panel’s language. If there is none for that language, it uses the name for your site’s default language, and failing that the built-in name.
- On your public site, only on pages in the language the name was written for. A Thai name never appears on English pages; those keep the built-in word. It shows in:
- the page title of the type’s list pages (browser tab and the title shown when the link is shared),
- the automatic header menu (the one used while you have no published header menu),
- search results, when your theme prints
{{item.type_label}}, llms.txtand the website chat assistant.
What a rename never changes
- Addresses (URLs).
/staffs/…stays/staffs/…. Change the address in the Content URLs card on the same page. - Slugs, template names, loops such as
{{#each staffs}}, and the API. - Headings written inside your theme’s templates. A list page whose template says
<h1>Posts</h1>, or a breadcrumb typed into a template, keeps that text. Edit it at Settings → Themes → a theme → Templates. See Themes and templates. - Words inside longer sentences, such as “View product” or “Delete Newsletter”, keep the built-in word.
Why a menu item is missing
No two sites have the same sidebar. There are four reasons, and this is the order to check them in.
1. The Admin Menu switches
Settings → General (/admin/settings/general) has an Admin Menu card: a list of every content type, each row with a drag handle, an icon, a name and an on/off switch. Drag to reorder the sidebar, switch to hide or show, then save.
The names in this list follow the admin panel’s language. A row you have renamed shows your name with the built-in one in grey after it. The pencil on a row renames that type — see Rename a content type above.
Opening the URL of a type whose switch is off usually shows ”… is not enabled”, with a link to the settings page.
2. Your plan
A row your plan does not include is greyed out: it cannot be dragged, its switch is disabled, and a badge names the plan that unlocks it — Pro or Business.
| Type | Seed | Pro | Business |
|---|---|---|---|
| Pages · Posts · Media · Sliders · Forms | Yes | Yes | Yes |
| Docs · Books · Events · Staffs | Yes (see note) | Yes (see note) | Yes (see note) |
| Store (product catalogue) | No | Yes | Yes |
| Orders + Coupons | No | No | Yes |
| Members · Newsletters | No | No | Yes (see note) |
Note: the marked rows also have to clear the experimental condition in point 3. The plan alone is not enough.
A newly created site is on the trial plan, which unlocks every type in this table up front. The experimental condition in point 3 still applies.
Rows that are experimental features (point 3) carry no plan badge, and their switch can be turned on even where the plan does not include them — but the page will then fail to load its data. Treat the table above as the authority: Members needs Business, for example.
Pro gets the product catalogue without the back office, so on Pro the Store menu appears but has no Orders or Coupons inside it.
Opening a store page your plan excludes — /admin/store/orders on Pro — shows ”… is not included in your plan” along with the plan you need.
The plan governs other things too. On Seed, the add-language field in the Languages card is disabled and labelled “Multi-language requires the Pro or Business plan”. Plan details are in Plans and billing.
3. Experimental features
Some features are open only to sites the team has flagged as experimental: Events · Docs · Books · Staffs · Members · Newsletters · Tours.
A site without the flag sees them neither in the sidebar nor in the Admin Menu list — as though they did not exist. A site with the flag sees the row with a yellow Experimental badge.
Put together: an ordinary site without the flag can enable Pages · Posts · Media · Sliders · Forms and Store (subject to plan). If you need one of the others, contact the SeedWebs team.
4. Role permissions
The Settings, Tools and Logs groups filter their sub-items by your role. A group with no sub-items left disappears entirely.
| Group | super_admin | admin | editor | writer |
|---|---|---|---|---|
| Settings, all items | Yes | Yes | Payments only | Group hidden |
| Tools | Every item | Every item except Reset | Group hidden | Group hidden |
| Logs | Yes | Yes | Group hidden | Group hidden |
Reset is visible to super_admin alone.
Opening a URL your role cannot use shows “Not available for your role” with a button back to the Dashboard. Each role is described in Users and permissions.
The checklist
- Go to Settings → General → Admin Menu and look for the row.
- No row at all → it is an experimental feature your site does not have enabled.
- A row, greyed out, with a plan badge → you need to upgrade.
- A row whose switch works → it was simply off. Turn it on and save.
- Rows look normal but the Settings / Tools / Logs group is missing → that is your role. Ask the site’s admin.
If the feature is not in SeedWebs at all, see What SeedWebs does not have.