Skip to content

Admin

Admin and marketing site

Admin: /admin (login /admin/login) Marketing: /, /about-us, /our-services, /blog, /faq, /contact, legal pages

Last updated Aug 20, 2026 · 2 min read

Admin: /admin (login /admin/login)
Marketing: /, /about-us, /our-services, /blog, /faq, /contact, legal pages

Operating ProfileSuite after install: users, content, and the public brochure site. Full admin reference: Admin overview.

Scenario: agency operator

You host ProfileSuite for clients. You need staff accounts, a blog, and a place to moderate user-generated landing pages.

  1. Sign in at /admin/login.
  2. Users — create staff; use Roles for permission sets.
  3. Settings → Global — site name, and other runtime options.
  4. Settings → Languages — translations for the UI.
  5. Front pages — edit marketing copy (front_pages/{slug}).
  6. Posts / FAQs / Knowledge base — content the public site and help center use.
  7. Landing pages, Link-in-bio, Resumes, Lead forms, Leads — moderate or export client output.
  8. Email templates — system mail copy.
  9. License — purchase code status.

Done: Public site reflects your brand; tools stay available at /tools/*; inbound leads are searchable.

Dashboard

The admin home (/admin) summarizes users, content, and recent activity. Regular users also have a personal dashboard with shortcuts to their leads and assets.

Marketing pages (built in)

These are part of the Laravel app (Inertia pages under Pages/Landing), not the optional _landing/ static site.

Path Page
/ Home
/about-us About
/our-services Services
/team Team
/blog Blog index
/faq FAQ
/contact Contact form
/terms-of-services, /privacy Legal

SEO defaults live in config/seo.php (titles, descriptions, per-tool meta, theme color).

Registration and passwords

  • Register: /admin/register (if enabled in your deployment)
  • Password reset: /admin/password-reset

Lock down registration in production if this install is not a public SaaS.

← All ProfileSuite – Digital Business Card, Bio Link & Lead Capture Platform documentation

We use cookies to understand how visitors use this site. Cookie Policy