SGEN in 5 minutes
| Field | Value ||---|---|| Audience | sgen-admins || Page type | guide || Area | Documentation || Updated | 2026-05-14 || What this covers ||---|| What is this for? || Good use cases || What NOT to use this for || How this connects to other features || Before you start || Where to go || Steps — Get your bearings in SGEN || What success looks like || What to do if it does not work |How to get oriented in SGEN
Read time: about 5 minutes. Hands-on orientation in your dashboard: 15 minutes. The opening sections explain what SGEN is and how the pieces fit together. The numbered Steps section near the end walks through a first-session orientation pass if you want to do it now.
SGEN is a website platform built for teams who want to own their site — its content, its design, its performance — without depending on a developer for every change. It is a content management system in the same category as WordPress, but built on a different set of decisions: a visual editor that works the way designers think, a content model that fits structured data, and an admin surface designed for non-technical users who need to move quickly without breaking things.
If you are reading this because someone sent you an admin link and you are not sure where to start, this is the right page. It covers what SGEN is, what you can do with it, and how the pieces fit together — all in the time it takes to read two or three pages of a book.
You do not need to know anything about web development to use SGEN. You do not need to touch code. You do need to know what you want to say and be willing to explore the dashboard — which is organized clearly enough that most first-time users find the thing they are looking for within a few minutes.
By the time you finish reading this page, you will have a clear mental map of what SGEN is and a sense of where to go for the tasks you care about. The more detailed guides in this documentation cover each area in depth — this is the starting frame, not the full picture.
What is this for?
This page is for anyone who is brand new to SGEN and wants a fast, plain-language orientation before diving into the specifics. It is intentionally short. It does not try to cover everything.
You might be a business owner who was handed admin access. You might be a marketing manager who will manage the blog, run campaigns, and update the homepage. You might be a team member who has never used a CMS before and wants to understand what you are working with before your onboarding call.
Whatever brought you here, the goal of this page is the same: leave with a clear picture of what SGEN does, how it is organized, and what to do next. Everything else is in the detailed guides.
Good use cases
SGEN is used across a wide range of business types. These examples show the range.
- A specialty food brand that updates their site weekly.
A regional olive oil producer uses SGEN to publish their weekly product blog, update their catalog when new harvest varieties arrive, and manage their trade inquiry form. Their marketing manager makes all updates directly in the SGEN dashboard — no developer involved.
- A professional services firm managing a content-rich site.
A strategy consultancy uses SGEN to maintain their portfolio, publish thought leadership articles, and run a client inquiry form. Their team updates the site themselves between client projects.
- An e-commerce brand with both a store and a content site.
A wholesale supply company manages their product catalog in SGEN Custom Objects, runs targeted landing pages for campaigns, and publishes industry content for their trade audience. The content team and the commerce team both work in the same dashboard.
- A local venue running events and managing reservations.
A cooking school uses SGEN to publish class listings, manage RSVP forms, and post recaps after each session. All content lives in SGEN and is updated by the events coordinator without any technical support.
- A growing brand adding a second language.
A Manila-based lifestyle brand launches a Spanish-language version of their site by adding translated pages with language-prefixed slugs in SGEN. No plugin required — SGEN's URL and SEO fields handle the structure natively.
- A team managing multiple campaigns at once.
SGEN's own marketing team runs three campaigns simultaneously, each with a dedicated landing page, embedded form, and unique slug. The marketing manager creates each page, embeds the appropriate form, and monitors lead submission counts — all without leaving the dashboard.
- **A brand that needs a visual redesign without rebuilding
everything.** A growing e-commerce brand wants to refresh their homepage layout without touching the other pages. They use SG-Builder to redesign the homepage visually, section by section, while the rest of the site stays live and unchanged.
What NOT to use this for
SGEN is a capable platform, but it is worth knowing what it is not designed to handle on its own.
- Do not expect SGEN to automatically translate your content.
SGEN manages the structure for multi-language sites but does not provide built-in machine translation. You bring the translated text; SGEN stores and presents it.
- **Do not use SGEN as a substitute for a dedicated e-commerce
platform if you need complex inventory management, shipping rules, or multi-currency checkout.** SGEN handles products and checkout for many use cases, but complex e-commerce operations may need purpose-built tooling.
- **Do not expect changes you make in the dashboard to appear
instantly on a heavily cached site.** Some hosting setups cache pages aggressively. If you publish a change and do not see it on the live site, clearing your site's cache is usually the first step.
- **Do not use the SG-Builder for content that changes daily
or weekly.** Blog posts, product updates, and news items belong in the Blog and Custom Objects areas — not built as static sections in the visual editor. Builder sections are for layout and design, not for content that you update on a regular schedule.
How this connects to other features
SGEN is one platform with several connected areas. Here is how they fit together.
- Pages — The foundation. Every URL on your site that is
not a blog post or Custom Object detail page is a Page. Your homepage, about page, contact page, and landing pages are all Pages. You create and edit them in the Pages area.
- Blog — The publishing engine. Blog posts are dated,
reverse-chronological content — news, articles, guides. They live in the Blog area, appear in your blog index feed, and can be assigned to categories for filtering.
- Forms — The lead capture system. Native Forms lets you
build contact forms, inquiry forms, and RSVP forms that store submissions in your dashboard and send notification emails. Forms are embedded on Pages or Blog Posts.
- Media — The file storage. Every image, PDF, or video
you upload to your site goes through the Media area. Media items are reusable — you upload once and can use the same file on multiple pages.
- Custom Objects — The structured content system. When
you have repeating content with consistent fields — team members, products, testimonials, case studies — Custom Objects give you a record-based way to manage them that scales as you add more.
- SG-Builder — The visual editor. SG-Builder is a drag-
and-drop layout tool for designing the visual structure of your pages section by section. It works alongside your content — you design the layout in the builder, and the content lives in the relevant content area.
- Settings — The control surface. Domain, SEO defaults,
appearance settings, user management, and integrations all live under Settings. Most settings are configured once at setup and rarely touched again.
Before you start
A few things to know before you log in for the first time or start making changes.
Your role in the dashboard determines what you can see and do. An admin can access everything. An editor may not see Settings or user management. A contributor may only be able to create content in Draft — not publish it. If you are trying to do something and the option is not visible, your role may not include that permission.
SGEN's dashboard is organized around the left sidebar. Every major area — Pages, Blog, Forms, Media, Custom Objects, Settings — is accessible from the sidebar. If you are looking for something and cannot find it, the sidebar is the first place to look.
Changes you make in the dashboard do not go live until you click Save or Publish. Draft content is visible to admins in the dashboard but not to visitors on the public site. You can work on content in Draft mode indefinitely and publish when it is ready.
Where to go
Log in to your SGEN dashboard. The URL is typically yoursite.com/sg-admin or a URL provided by your account owner. Once logged in, you will see the dashboard home screen with the left sidebar.
For your first session, explore these areas in order: Pages (to understand what pages your site already has), Blog (to see existing posts), and Settings (to see how the site is configured). Exploring read-only before making any changes gives you a baseline understanding of the site's current state.
Steps — Get your bearings in SGEN
These steps are not about making changes — they are about understanding what you have before you start modifying it. A fifteen-minute orientation session before your first real work session pays off every time.
1. Log in and take note of the sidebar
Log in to your dashboard. Look at the left sidebar. Note every section you can see — Pages, Blog, Forms, Media, Custom Objects, Settings, and any others. The sections you can see tell you what your role has access to. If a section is missing and you expected to see it, your role may not include access to that area.
Make a mental note of the section names and what each one is likely for. You do not need to open them yet — note that they exist and where they are in the list.
2. Go to Pages and scan your existing pages
Click Pages in the sidebar. Scan the list of pages your site already has. Note the page titles, their URL slugs, and their status (Published or Draft). This is the core structure of your site — the pages that visitors can reach.
Look for the pages you know about — home, about, contact — and confirm they are in the list. If you see pages you do not recognize, open them and read the content to understand what they are for.
3. Go to Blog and check existing posts
Click Blog in the sidebar. Scan the list of posts. Look at the categories used, the publication dates, and the status of each post. This tells you how active the blog has been and what type of content has been published.
If there are drafts in the list, open one and read it. Drafts often represent planned content that was never finished or published. Knowing about them helps you plan what to do next.
4. Go to Forms and see what is set up
Click Forms in the sidebar. See which forms are already built and published. Check whether each form has a notification email configured in its Mail Settings — a form without a notification address is one where leads arrive silently.
If a form says zero submissions and was published months ago, it may not be embedded on any page. Open the relevant page and confirm the form embed is present.
5. Go to Settings and note your domain and SEO defaults
Click Settings in the sidebar. Check the site name, the domain, and the SEO defaults (usually a section called Search Engine or SEO within settings). These defaults determine what appears in search results for pages that do not have their own custom SEO title and description set.
If the SEO defaults are blank or say "SGEN Site," they were never configured and should be updated with your actual site name and a short description of what your site does.
6. Make a short list of your first real tasks
After the orientation pass, write down the three most pressing things you want to do. Not everything — three. A first task list might be: update the homepage hero text, publish a new blog post, and configure the notification email on the contact form. Concrete tasks with a defined scope are more productive than open-ended "explore the dashboard" sessions.
Take those three tasks and look for the relevant guide in this documentation. Every major task has a step-by-step guide that walks you through the specific steps, shows you what the screen looks like at each stage, and tells you what success looks like when you are done.
What success looks like
A successful orientation session leaves you with the following.
- You have logged in and confirmed your role and access level.
- You have seen the Pages list and know what pages your site has.
- You have seen the Blog and know whether there are existing
posts and drafts.
- You have seen the Forms list and know which forms are live
and which have notification emails configured.
- You have checked the Settings and noted the domain and
SEO defaults.
- You have a short list of three concrete first tasks with
the relevant guide bookmarked for each.
That is all. An orientation is not about doing everything — it is about understanding the landscape before you start making changes. With that map in your head, every task becomes easier because you know where it lives and what it connects to.
What to do if it does not work
- **You logged in but the sidebar looks different from this
guide.** Your SGEN version or your role may show a different set of sections. The names and locations of sidebar items can vary between SGEN versions. If you cannot find a section you are looking for, ask your account owner which role you have been assigned and whether your plan includes the feature you are looking for.
- You see the dashboard but cannot access a specific section.
This is almost always a role permission issue. Only administrators can access all sections. Editors and below have restricted access. Contact your account owner to update your role if you need access to a section you cannot currently see.
- Your changes are not appearing on the live site.
Check that you clicked Save or Publish — the dashboard auto-saves drafts in some views but not always. Also check whether the content is still in Draft status. Draft content is not visible to visitors. Flip the status to Published and save again.
- The site looks different from what you expected.
Your site may have custom styling or an active theme that changes the appearance of certain elements. If you are seeing layout issues or unexpected styling, contact your account owner or SGEN support before making changes — appearance issues are often a theme or custom code conflict, not a content problem.
- You cannot find the page or feature described in a guide.
This documentation describes the standard SGEN admin surface. Some features may be disabled, renamed, or in a different location depending on your SGEN version or site configuration. If a guide describes something you cannot find, search the Settings area and sidebar for an equivalent option, or contact your SGEN support team.
## Related reading| Topic |
|---|
| Welcome to SGEN Docs |
| What is SGEN |
| Publish your first blog post on SGEN |
| Pages vs Custom Objects vs Blog Posts in SGEN |