Every branch set up, every action recorded.

The Administration module is the control room of LogiSoft.

• Users + Roles — create users, assign roles. A user can hold multiple roles.
• Role Permissions / User Permissions — granular tree per Module → Screen → Right.
• Branches + Companies + Company Groups — multi-tenancy hierarchy.
• SMTP — configure outgoing email server used for password resets, escalations, etc.
• Module Settings — per-module key/value config (some keys are encrypted).
• Audit Logs — every Add/Edit/Delete is recorded here automatically.
• Help — Field Hints / Screen Topics / Workflows — in-app help content management.
• Chat — FAQs / Logs — assistant FAQ corpus + moderation queue.

A Company Group is a parent holding entity that owns multiple Companies. It's optional — you can have Companies without a Group.

When to use Company Groups:

• You operate one corporate group across multiple jurisdictions, each with its own legal entity
• You want consolidated P&L / volume reports across all Companies under the Group
• Different Companies under the Group share customers / vendors / charges via the master data

When NOT to use:

• Single-legal-entity operations (just create a Company without a Group)
• Different brands of the same Company (use Branches or trade names instead)

A Company is a legal entity registered in your jurisdiction (e.g. "ABC Logistics Pvt. Ltd."). Each company has:

• A legal name + trade name
• A tax/registration number (NTN, VAT, GST, etc.)
• One or more Branches (offices / locations) underneath it
• Optionally a parent Company Group for consolidated reporting

When LogiSoft generates invoices, the Company is the legal payer/payee on the document — not the branch.

Common configurations:

• One Company, many Branches — single legal entity with multiple offices (Karachi, Lahore, Islamabad)
• Many Companies under one Group — holding company with separate legal entities per country/regulatory zone

A Branch is a physical office or operational location belonging to a Company. One Company can have many Branches (e.g. Karachi, Lahore, Dubai office of the same legal entity).

Why branches matter:

• Users are scoped to one or more branches — operations staff in Karachi don't need to see Lahore's pending shipments
• Reports filter by branch so each office sees its own work
• Default Tax Group per branch — invoices created from this branch automatically apply that tax group (useful when branches in different jurisdictions have different VAT/GST rules)
• Document numbering can include the branch code (e.g. KHI-INV-2026-00001 vs LHE-INV-2026-00001)

Users are people who log in to LogiSoft. Each user has a Role that grants module/screen access, plus a list of allowed Companies and Branches. The Companies & Branches tab on the user form controls which branches the user can read and write data in. Operational records (bookings, sales, GRN) created by this user are stamped with the active branch from their header switcher.

SMTP screen manages Email Profiles (host, port, credentials, from address) and ties them via Email Usage Mappings to specific Email Templates.

Three tables involved:

• EmailProfiles — connection details for one SMTP server
• EmailTemplates — subject + body templates with placeholders
• EmailUsageMapping — links a usage type (e.g. "ChatEscalation", "SiReminder", "InvoiceEmail") to one profile + one template

When code calls EmailService.GetEmailConfig("ChatEscalation"), the service looks up that mapping and returns the SMTP config + template — code stays generic, configuration is data-driven.

Role Permissions is where you tick the boxes for what each Role is allowed to do.

The grid is organized as: Module → Screen → Right (view / add / edit / delete / print).

Tick a box → that role can perform that action on that screen.

Untick → the action button is visible but disabled (LogiSoft never hides — it disables, so users know the feature exists).

Best practice — use the principle of least privilege:

• Admin — everything ticked
• Operations — view / add / edit on operational screens; no delete; no admin screens
• Sales — view / add / edit on sales + customer screens
• Accountant — view / add / edit on finance screens; view-only on operations
• Read-only auditor — view-only on everything

Need exceptions? Use [User Permissions](/UserPermissions/Index) to override per-user without changing the role.

Audit Logs records who did what, when. Every Save / Update / Delete in any controller (via AuditService from MasterBaseController) writes a row with:

• ScreenName
• UserId + Username
• ActionType (Add / Edit / Delete / View)
• RecordId
• Old values (JSON, for Edit/Delete)
• New values (JSON, for Add/Edit)
• Description
• IP address + timestamp

Compliance-grade — never edit or delete log rows. Filter by user / date / screen to reconstruct any record's history.

Import Master Files is the bulk-data refresh screen. Each row = one master file source with Last Sync timestamp + Sync button. UN/LOCODE has a sequential 5-step button (Countries → States → Cities → SeaPorts → AirPorts) with per-step progress.

Configuration of each source is in [Module Settings](/ModuleSettings/Index) under Master Files module — URLs, API keys (where needed), local folders.