You buy modules you will never use
The licence covers everything, the sidebar shows everything, and your people spend a year navigating past the two-thirds that does not apply to them.
Administration & customization
Your ERP, shaped to your organization
Every module and every individual tool can be switched on or off. Roles are built from individual permissions. The system you run in six months does not have to be the one you started with.
Shared platform configuration
Illustrative product view with sample data. Request a live walkthrough.
Before Caspian ERP
Most ERPs are configured once, by someone else
You pay for an implementation, the shape is frozen, and every later change is a change request with a price on it.
Permissions come in three sizes
Admin, manager, user. Anything more specific than that needs a conversation with a consultant and a quotation.
Changing your mind is expensive
The organization evolves, and the system does not — because every adjustment is a project rather than a setting.
What it does
The controls that make it your system
This is what an administrator can do without contacting us, without a consultant, and without a release.
Switch departments and tools on and off
The sidebar, the search and the permissions all follow the switches.
- Turn whole modules on or off for your organization
- Turn individual tools off within a module you do use
- People only see what applies to them — no navigating past dead weight
- Turn something on later and it appears, with the data still there
Roles you build yourself
Start from the defaults and then define exactly what a role can do, tool by tool.
- Owner, Admin, Manager and Member to start from
- Custom roles built from individual read / create / update / delete permissions
- A role per real job — permit issuer, storekeeper, budget holder
- Every member holds exactly one role per organization
Enforced server-side, not in the interface
Hiding a button is not a control, and never was.
- Permissions evaluated by server-side security rules
- A permission you did not grant cannot be reached by any client
- Multi-tenant isolation between organizations
- The audit log records who changed access, and when
Shape the organization itself
Departments, job titles and members are yours to define and change.
- Organization profile, departments and job titles
- Invite members by email; they join with the role you chose
- One account can belong to several organizations, cleanly separated
- Change structure without a migration
Branding and language
The system reads as yours, in the language each person prefers.
- Your organization’s branding inside the workspace
- English, Azerbaijani, Turkish, Russian, Norwegian, German and French included
- Each member chooses their own language
- No separate instance needed for a different site
An audit trail of the configuration
Changes to who can do what are recorded, because they matter.
- Membership, role and permission changes recorded and attributed
- Answers "who changed this, and when?" without guesswork
- Useful in a client audit as well as an internal one
- Configuration history, not just data history
From an empty organization to a working system
This is a settings exercise, not an implementation project.
Create organization
Choose modules
Define roles
Invite members
Tune settings
In use
Every tool in the module
What an administrator controls
Configure the shared platform from one place.
Organization Profile
The organization’s own details, structure and defaults — the top of everything else.
Members
Who belongs to this organization, what role each holds, and their current status.
Roles
Custom roles assembled from the permission registry, so a role matches a real job.
Permissions
Read, create, update and delete per tool — the registry every role is built from.
Invitations
Invite by email; the person joins with the role you chose before they arrive.
Departments & Tools
The switches that decide which modules and which individual tools your organization sees.
Audit Log
A recorded, attributed history of membership, role and permission changes.
Branding
Your organization’s identity inside the workspace, so it does not read as generic software.
Language
Seven languages shipped with the product, chosen per member rather than per installation.
Connected, not bolted on
Configuration reaches into every module
These settings are why two organizations on the same platform can look nothing alike.
Your permit types and risk matrix
HSEQ bends to your safety management system — permit types, risk scales and observation categories are all configuration.
Your approval thresholds
Who signs at what value, and whether a three-way match is required before payment, are policy decisions you set here.
Your chart of accounts
The account structure, tax rates and budget periods are defined by you, and every posting module follows them.
Who lives in it
Who does this work
In most organizations, one or two people — and not for very long.
System administrator
Sets up the organization, decides which modules are live, builds the roles and invites people. Usually a few hours, not a project.
Compliance owner
Cares that access is restricted correctly and that the audit log can answer who changed what.
Department head
Asks for a tool to be switched on and can use it once the administrator has configured access.
Yours to shape
The limits, stated honestly
Configuration is deep, but it is configuration — here is where the line sits.
- Modules and tools: switch any of them on or off, at any time, immediately
- Roles and permissions: build any combination of read, create, update and delete per tool
- Structure: departments, job titles, members and multiple organizations under one account
- Workflow settings: approval thresholds, statuses, categories, intervals and warning windows
- What it is not: custom code, bespoke database fields or a private build — if you need those, talk to us first
Administration · Settings
| Setting | Value |
|---|---|
| Active modules | 9 of 11 |
| Custom roles | 7 defined |
| Permission enforcement | Server-side |
| Languages | 7 available |
| Audit log | All access changes |
Administration questions we get asked
Can we really turn off modules we do not use?
Yes — whole departments or single tools, at any time. The sidebar, the global search and the permission registry all follow the switches, so people are not navigating past features that do not apply to them.
What happens to the data if we switch a module off?
It stays. Switching a module off hides it from the interface; turning it back on later brings it back with its records intact.
How specific can a custom role be?
Down to read, create, update and delete on an individual tool. That is enough to build a role that matches a real job — a permit issuer who can sign but not configure, a storekeeper who can issue stock but not adjust it.
Is hiding a tool the same as securing it?
No, and we do not treat it that way. Permissions are enforced by server-side security rules, so a permission you did not grant cannot be reached by any client regardless of what the interface shows.
Do we need a consultant to set this up?
No. Creating the organization, choosing modules, defining roles and inviting people is a settings exercise an administrator does directly. If you want help with a large migration, ask us — but the configuration itself is yours.
Can one company run several organizations?
Yes. Groups, joint ventures and consultancies commonly do. One account can belong to several organizations and switch between them, and data never crosses the boundary between them.