Website and Content

Under System Control → Landing Page.

These screens govern the public-facing website that can sit in front of the application — not the HR system itself. Everything here is seen by visitors who have not logged in.

The landing page is switched off by default

In a standard Embernxt deployment the public landing page is disabled, and anyone visiting the address is taken straight to the login screen.

That is deliberate. An internal HR system does not usually want a marketing front page, and not having one means less to keep updated and less exposed to the internet.

If the screens below look irrelevant to you, that is why — and nothing here needs your attention. Enabling the landing page is a deployment change; ask whoever administers your installation.

Landing Page

The landing page editor configures the public home page section by section — a hero banner, features, an about section, testimonials, statistics, frequently asked questions, a call to action, and contact details. Each section can be switched on or off, and colours, images and wording are set per section.

It is a small website builder, and it is only worth opening if your deployment actually serves a public page.

Custom Pages

Landing Page → Custom Pages

Extra public pages beyond the home page — Privacy Policy, Terms of Service, About Us.

Each has a title, a URL slug, the body content, and a published or draft status.

Two of these are usually not optional

If your deployment serves anything publicly — including a careers page that collects applications — a privacy policy is generally a legal requirement, not a nicety, because you are collecting personal data from the public.

Terms of service is the usual companion. Check what your jurisdiction requires rather than assuming; this manual cannot tell you.

Contact Inquiries

Landing Page → Contact Inquiries

Messages submitted through the contact form on the public site: who sent it, their email, the message, and when it arrived.

Nothing here chases you

Inquiries arrive quietly. There is no queue that nags, no badge, and — unless email is configured to forward them — no notification at all.

If your public site has a contact form, somebody needs to be responsible for opening this screen on a schedule. Otherwise messages sit here unread, which is worse than not having the form.

Newsletter

Landing Page → Newsletter

Email addresses collected through the signup form on the public site.

The screen holds the list. Actually sending a newsletter is normally done with a dedicated mailing tool, exporting these addresses into it.

These addresses come with obligations

A collected email address is personal data. Depending on where you operate, you may be required to record consent, offer a working unsubscribe route, and delete addresses on request.

Do not export this list into a mailing tool without knowing which rules apply to you.

Common questions

None of this is in my sidebar. Either your role lacks the permission, or the landing page is disabled for your deployment — which is the default. Both are normal.

We enabled the landing page and it looks like a template. It ships with placeholder content. Work through the sections in the landing page editor, and set your logo and colours in Settings → Brand Settings.

Is the careers page part of this? It is related but separate — the careers page is driven by Recruitment and lists your active job postings.

Can I stop the public site without losing the content? Yes. Disabling the landing page leaves the pages and their content in place; visitors simply go to the login screen instead.

Where do search engine settings live? Settings → SEO Settings. See Settings.