Users and roles
Access is configured for the actual work.
MenschOS. Luna
Public website and business system in one MenschOS.
MenschOS Luna is not just a presentation site or a separate back office. The same system powers the public mensch.rs website, the team's internal work, the client portal, and Luna AI. Projects, contacts, leads, documents, and reports use one shared database.
This page · Admin · Portal · Illustrative scenarios
MenschOS Luna · pregled
MenschOS Luna · radni prostor
Ilustrativni primerOtvoreni zadaci14
Aktivni projekti6
Za potvrdu3
Poslednje aktivnosti
Projekat · rok ažuriran 10:42
Prijava · status promenjen 09:15
Luna · predlog nacrta izveštaja Juče
Pregled aktivnosti
09:41
MenschOS
Luna
Za potvrdu03Aktivnosti čekaju odluku
Luna · pripremi nacrt ↗
Projekat · pregled rokova ↗
Prijave · u proveri ↗
Public website and business system in the same MenschOS.
Visitors see pages, articles, and contact options. The team behind the scenes sees leads, projects, tasks, and documentation. Clients with portal access see status, files, and agreed information. Data is not split across separate tables that you merge by hand; everything runs on one platform.
An inquiry from the site does not disappear into an inbox: it becomes a CRM record and can get a project, tasks, and an owner. Site content is updated from the admin area, with the same access rules and change history as the rest of the work.
MENSCH uses MenschOS for its own operations, including the site you are reading now. This page is part of the same system we offer to clients.
- Public website
- Admin and delivery
- Client portal
One foundation. Modules for your work.
The same MenschOS can cover a marketing site, operational admin, a portal, and integrations. We adapt the platform to each organisation with modules, roles, and rules - from public pages to internal processes. We agree the initial scope together and add capabilities in planned steps.
Exact features, automations, and integrations are defined for each implementation.
Different work. Clear organisation.
See how the same foundation adapts to two organisations with different day-to-day needs. Choose an example and follow the full flow, from the first request to the report.
Illustrative scenario, not a view of real business data.
menschOS
1 / 5
Same foundation. Different ways of working.
EmPower tracks programmes, participants, and results. Netvist tracks projects, development, and delivery. Both scenarios show how one MenschOS can carry both the public-facing part and internal work - with different screens, processes, and responsibilities, but without splitting data.
See what your programme could look like ↗Luna AI within MenschOS
Luna AI works with MenschOS data in the admin area, the portal, and contact chat on the site. The team can find information faster, draft content, or check status without switching between multiple tools.
Users get help within their permissions. Suggestions that change business data go through approvals and confirmation; public chat does not open access to internal data.
Choose a sample question
Documents and calls
Review requirements, checklists, and draft applications.
Projects
Summaries, suggested next activities, and draft reports.
Communication
Draft replies, conclusions, and follow-up messages.
Forms
Suggested questions and questionnaire structure.
Analytics and content
Explain indicators and draft content based on approved data.
System development
Prepare specifications, review change history, and suggest improvements.
AI features and the level of automation are reviewed individually; do not present everything as already delivered capability.
✳Luna AI
Choose a sample question
Illustrative conversation. The AI actions shown demonstrate the planned way of working; availability depends on the implementation.
You decide who can do what.
Access to information is set by user roles and responsibilities. Sensitive changes require appropriate permissions and confirmation, and integrations have a clearly defined purpose.
Separating workspaces
Rules define boundaries between organisations and teams.
Audit trail
Important activity and changes are recorded to the agreed extent.
Protection and continuity
Backups, security controls, and recovery procedures are defined for the implementation.
Human confirmation
AI assistant suggestions should not automatically become sensitive business decisions.
EmPower · uloge
Programme coordinator vidi programe, odluke i izveštaje.
Applications associate vidi prijave i proveru dokumentacije.
Netvist · uloge
Project manager vidi plan, rokove i odobrenja.
Developer vidi zadatke sprinta i evidenciju rada.
We start from how you work.
First we understand processes, people, and information. Then we agree initial scope, modules, and access rules. We plan configuration, development, testing, and training in concrete phases.
You can start with a limited set of processes and expand the system when the need shows. Exact scope, cost, and timelines are set in the proposal.
01
Conversation and analysisProcesses, users, existing systems, and goals.
02
Proposed solutionSelected modules, integrations, scope, and order.
03
Configuration and developmentWorkspace, rules, interface, and agreed features.
04
Testing and rolloutScenario checks, documentation, and user training.
05
SupportMaintenance and next phases per the agreed model.
Luna. A name with meaning.
Luna is the MENSCH founder's beagle. Curious, persistent, and impossible to forget.
She now has grandchildren and great-grandchildren and lives happily in Seća Reka, near Kosjerić.
For us, Luna is part of the personal story behind MENSCH. That is why this version of MenschOS carries her name.
MenschOS Luna.
What you should know.
What is MenschOS Luna?
MenschOS is a business platform developed by MENSCH. Luna marks this generation of the system and its built-in AI assistant. It covers the public website, the team admin area, the client portal, and one shared database - not separate products stitched together later.
Does the mensch.rs site run on MenschOS?
Yes. Pages, articles, contact chat, and inquiries you send from the site are powered by the same MenschOS the team uses for leads, projects, and delivery. This presentation page is part of that same system.
How are the public site and admin connected?
Content is published from the admin area. Inquiries from the site become CRM leads without manual re-entry. Projects, documents, invoices, and the client portal use the same organisations, contacts, and permissions where the implementation defines that.
What is the client portal?
Limited, secure access for clients: view projects, documents, and invoices the team shares. Accounts are created by the MENSCH team after agreement; there is no public self-service registration on the site.
Do EmPower and Netvist use the same interface?
The illustrative scenarios show how the same foundation adapts to different processes. Modules, screens, and access rights differ by need - as with real clients.
Are EmPower and Netvist real clients on this page?
No. They are fictional workflow examples. They show how MenschOS can look in practice; they are not a display of real data.
Does every implementation include all modules?
No. Scope is agreed: some clients start with the site and leads, others with projects, a portal, or integrations.
Can we start with a smaller scope?
Yes. We typically define a first phase (e.g. site + CRM, or portal + projects), then plan extensions.
Does MenschOS connect to existing systems?
When APIs, permissions, and technical conditions allow, integrations are planned separately - e.g. email, billing, external archives, or partner services.
Does Luna AI see all data from the internet?
No. Luna in a business context works with data and permissions defined in your implementation. Public contact chat collects inquiries for the team; it does not give visitors access to admin data.
Does Luna AI automatically execute business decisions?
AI provides suggestions, summaries, and drafts. Sensitive changes require human confirmation and appropriate permissions. We agree the level of automation per module.
How is pricing determined?
By modules (public site, admin, portal, integrations, AI), scope of customisation, training, and support model. After analysis we prepare a proposal.
What happens after rollout?
Maintenance, support, and next phases are defined in the contract. The system can grow without replacing the platform.
A conversation about how you work
Describe how you run the site, inquiries, projects, and client relationships today. Together we assess whether you need the public part, internal work, a portal, or all of it in the same MenschOS.
Schedule a conversation ↗