Portal administration
Portal administration is the set of settings that define how the whole company works in LadVen OS: module rules, access, email, and sign-in. They are changed by the owner or administrator; this requires administrative rights.
This page is an overview of what you can configure. The access model is described in detail in the Access and roles section, and the second sign-in factor in the Two-factor authentication section.
Module rules
The administrator sets rules by module — how the portal behaves by default for everyone:
- Tasks — rules for distributing work (whether tasks can be assigned downward, upward, or across departments), the automation mode for regular employees, and default requirements (result review, preliminary estimate).
- CRM — the default access mode (strict or open) and role rights to client data.
- Chats — who is allowed to have private conversations: active employees, colleagues from their own or a related department, or only within a project.
- AI — whether the module is enabled and who can use AI connections.
- Documents and files — rules for working with the company's documents and files.
Change a module rule as a company-wide policy, not for a single situation: it affects all users at once.
Workspaces
Workspaces separate large perimeters inside the portal. For each one you can set members and their roles, as well as the rule enforcement mode: off, soft (warns), or strict (blocks the violation). Turn on strict mode when a workspace's boundaries must be enforced firmly.
Security
In the security section the administrator sets:
- the default access mode for modules (see Access and roles);
- department visibility — whether an employee sees the whole company structure or only their own branch;
- the two-factor authentication policy for employees and external participants (see Two-factor authentication).
System email
System email is how the portal sends messages (notifications, invitations, process emails). The administrator configures sending profiles, templates, and email subjects, and monitors delivery. Correctly configured system email is needed so that invitations and notifications reach employees and clients.
Custom fields
The administrator can add extra fields to employee profiles — for example, a free-form job title, an internal identifier, or a start date. Different types are supported: text, number, date, a list of values, a reference to a user or department; a field can be made required or multiple.
Before creating fields en masse, agree on why each one is needed and who fills it in: where exactly a field is shown to employees depends on the portal configuration, so introduce fields deliberately rather than in reserve.
Corporate sign-in (SSO)
LadVen OS supports sign-in through an external identity provider (corporate SSO). Right now such a connection is set up together with the LadVen OS team, not through a self-service interface in the portal. If your company needs a single corporate sign-in, discuss the connection with your portal provider — do not try to set it up as an ordinary integration.
Good practices
- Change module rules as a company-wide policy, thinking through the impact on everyone in advance.
- For sensitive modules keep the strict default access mode.
- Set up and test system email before mass invitations and process launches.
- Introduce custom fields for a specific need, not in reserve.
- Accompany policy and rule changes with a clear reason — it stays in the history.
Common mistakes
- Changing a module rule for one case, forgetting that it applies to everyone.
- Leaving an open access mode where there is client or financial data.
- Sending invitations before setting up system email — the messages do not arrive.
- Creating custom fields with no purpose, and the profile turns into a dumping ground.
- Expecting corporate SSO to configure itself like an ordinary integration — it is connected with the portal team.