Administration
The Yönetim (Administration) menu manages who signs in to CoreX ERP and what they can see and do inside: user accounts, roles and permissions, organizational units, the modules turned on in the installation, and sign-in records. This section is intended for the system administrator; the steps are written so that they can be carried out without needing any other information.
Access is determined in four layers — details in the Permission model:
- License and Module Management — which modules and features are turned on in the installation. Nobody can use a feature that is turned off.
- Permission — keys such as
erp-sales-orders.createthat come from the user's roles (and, if any, from unit roles and person-specific additional permissions). Buttons, screens and API requests check permissions. - Screen catalog — the screens the role shows in the menu. It does not grant permissions; it only simplifies the menu.
- Data restrictions — warehouse and work center restrictions, sales channel membership, price and cost visibility.
End-to-end example: New user and permissions.
Tasks
Concepts and reference
Menu map
| Section | Screen | Required permission | Description |
|---|---|---|---|
| Kullanıcı ve Roller (Users and Roles) | Kullanıcılar (Users) | users.view | Users |
| Kullanıcı ve Roller | Roller (Roles) | roles.view | Roles |
| Kullanıcı ve Roller | Çalışanlar (Employees) | organization.view | The people who perform the work in operation confirmations; they do not need to be ERP users and hold no permissions. |
| Onay Süreci (Approval Process) | Onayımı Bekleyenler (Awaiting My Approval) · Onay Şablonları (Approval Templates) · Onay Vekaletleri (Approval Delegations) | approval permissions, erp-approval-templates.view | In the approval process's own document. Their permissions are in the Permission list. |
| İzleme (Monitoring) | İşlem Kayıtları (Audit Log) · Erişim Günlüğü (Access Log) | audit.view | Monitoring screens |
| İzleme | Gönderim Kuyruğu (Dispatch Queue) | outbox.view | The outgoing email queue. |
| Araçlar (Tools) | Toplu Belge Yazdırma (Bulk Document Printing) · Veri Aktarımı (Data Import) · Toplu Belge Gönderimi (Bulk Document Sending) | one of the permissions of the relevant document | In their own modules. |
| Özelleştirme › Kuruluş Yapısı (Customization › Organizational Structure) | Organizasyon Şeması (Organization Chart) | organization.view | Organization chart |
| Özelleştirme › Genel (Customization › General) | Modül Yönetimi (Module Management) | company-profile.view (changing requires company-profile.edit) | Module management |
| Özelleştirme › Genel | E-posta Ayarları (Email Settings) · Uyarı ve Bildirim Yönetimi (Alert and Notification Management) | email-settings.view · alerts.view | Email settings are required for invitation and password links. |
The Yönetici (Administrator) role holds all permissions and is intended for setup. For daily work, use a separate account that holds the person's job role; the system also shows a segregation of duties warning when the Administrator role is assigned together with another role.