Back to Home

Site Admin

This section offers extensive customization options. You only need to configure your preferences once. These are system side settings and the settings will apply across the entire application. After the initial setup, there is no need to repeat the process—your chosen preferences will be saved and consistently used throughout the system.

Application setup covers following :

On the Server Settings

  1. Appsettings.json

  2. Appsettings.Producton.json

Inside Application Settings

(After Login SiteAdmin Menu)

  1. Customization

  2. User Types

  3. Languages

  4. Set Vocabulary

  5. Edit Site.css

Using these options entire application can be customise to your specific requirement.

On the Server Settings

appsettings.json

There are settings available in appsettings.json file.


  "ProgramSettings": {
    "Title": "IMSPL",   //Title displayed in browser
    "ContactUsonLogin": "Yes",  // Yes or No to allow creating enquiries by anonymous user
    "LoginWithGoogle": "No",     // Yes or No to allow login with Google
    "Menu": "Button",              // Button for Button menu and NoButton  for Standard Menu
    "CRMKey": "Type CRM Key  here",   
    "RecordsKey": "Type Records Key  here",  
    "OpenAiApiKey": "Open Ai API Key",
    "OpenAiModel": "gpt-4o",
    "GeminiAiApiKey": "Gemini Api Ai Key",
    "GeminiAiModel": "gemini-2.5-flash",
    "GoogleClientId": "Google Client ID",
    "GoogleClientSecret": "Google Client Secret",
    "UserFilesFolder": "Content/UserImages/",      // Folder to Save User Files  DO NOT CHANGE
    "AttachmentFilesFolder": "Content/uploads/"    // Folder to Save Files Uploaded with Tickets  DO NOT CHANGE
  },
Warning

Comments shown in above appsettings ProgramSettings are only for explanation and should not be included in appsettings.json file.

appsettings.production.json

There are settings available in appsettings.production.json file also. These are same as appsettings.json. Normally these overrides appsettings.json file settings.

Inside Application Settings

Customization

The customization page has following tabs:

  1. General
  2. Emails
  3. SMS
  4. Enable Ai
  5. WhatsApp
  6. Records

Now we will set these options one by one.

  1. General

    The General tab provides a few basic options that come pre-configured. However, you can easily customize them based on your preferences. It includes following settings:

  • Default Country

Select your preferred country from the provided list. Once selected, the application will automatically adjust its settings—such as currency, and formats—according to the chosen country.

  • Default Language

This option lets you choose the language in which you want to use the application. English is set as the default, but you can switch to any available language to make the interface easier to understand and operate.

  • Year Start Month

Normally the year start month is either January or April. The records number will restart from 1 from new year, The graphs and reports will be prepared accordingly.

  • Terms and Conditions URL

When a user is registering on the application he has to agree to certain terms and conditions. You can prepare a page on your website or add a pdf having terms and conditions and provide URL here.

  • Reasons for Task Failure

When a ticket or task cannot be completed successfully, it’s important to record the reasons for failure. This helps in tracking patterns, identifying bottlenecks, and improving overall service and sales strategy. Enter reasons separated by comma. Each reason should be up to 16 char only.

  • Source of Information

When a ticket or task is created, its source of information is specified. List of the sources here. Enter sources separated by comma. Each source should be up to 16 char only.

  • Enable Messaging

    Use this toggle to enable or disable the Messaging service as per your requirement.

  • Enable Chat

    Use this toggle to enable or disable the Chat service as per your requirement.

  1. Emails

    Configure your email in appsettings.json file, Enter a test email and click "Send" to test the settings.

Now decide who you want email to be sent and also decide the format of the email. The options are:

  • Email for Tasks

Use this toggle to enable or disable the Email for Tasks as per your requirement.

  • Email for Assignee

Use this toggle to enable or disable the Email for Assignee as per your requirement.

You can also decide the format of the email to task Creator, Assignee and for Update/Reply. These are several "TAGS" available for email setup. These TAGS will get converted to actual current values.

For example "{TaskDate}" will become actual date on which task / ticket is created.

  1. SMS

    The application includes SMS functionality to provide real-time updates to customers. This can be used for notifications related to tasks, complaints, or general updates.

  • Enable/Disable Toggle

    Use this toggle to enable or disable the SMS service as per your requirement.

  • SMS API Provider

    A list of supported SMS service providers will be displayed.

    You need to:

  • Choose a provider from the list.

  • Purchase a plan with that provider.

  • Set up the API key in appsettings.json

  1. **Ai (Artificial Intelligent)

    The application includes an integrated AI feature to help automate routine tasks and reduce manual workload. AI can handle certain operations intelligently to improve efficiency. Turn ON to let AI help users write better replies in tickets. When ON, AI will auto-generate ticket replies using available ticket data.

  • Enable/Disable Toggle

    Use this toggle to activate or deactivate AI services within the application.

  • AI API Provider

    A list of supported AI service providers is available.

    To activate:

    • Select a provider from the list.
    • Purchase the required service or API plan.
    • Set up the API key in appsettings.json

  • Enable Ai for reply improvement

Enable this to get option to improve your reply by Ai as may be selected by you.

  • Enable Ai for reply from Ai vector

Ai can reply based on your database or a simple word file. but this will use lot of resources. So other option is to create an Ai Vector whihc will e stored on Ai Providers portal. This will make reply faster as well as consume less data, in turn it will cost significantly less.

  1. WhatsApp

    WhatsApp messaging is supported, allowing notifications and updates to be sent directly to users via WhatsApp Messenger.

  • Enable/Disable Toggle

    Use this toggle to enable or disable WhatsApp messaging services.

  • WhatsApp API Provider

    A list of supported WhatsApp API providers will be shown.

    To use this feature:

  • Choose a provider.

  • Purchase a WhatsApp API plan.

  • Set up the API key in appsettings.json

  • After setup, WhatsApp will be used to send updates and alerts.

  1. Records

The toggles switches provided in this section play a crucial role in the configuration and operation of the application. It is essential to understand the purpose and behaviour of each toggle, as they directly affect how features function—especially when generating reports or tracking data.

Before enabling or disabling any toggle, review its description carefully to understand its impact on reporting and system behaviour.

  • Record Approval:

Any record like quotation, tax invoice etc will need approval before being printed or send to customer / user.

  • Enable Price List and Discount List:

It will enable making Price Lists and Discount Lists. While making records (e.g.: quotation / invoice), you will have option to select a price list or discount list and prices and discount will be selected from the selected lists for the products and services in the quotation / invoice.

  • Enable Multi-Currency:

if disabled, default currency (as set in the General tab) will be used.

No other currencies will be available for selection in making records (e.g.: quotation / invoice).

You still need to enable various currencies in Administration >> Countries And Currencies.

  • Enable Expiry Date:

Some products have expiry date for use or warranty expiry date. Enable this will provide an option to define expiry date while making records (e.g.: quotation / invoice).

  • Allow Price Change:

If "Enable Price List and Discount List" is enabled, you can still allow price change.

  • Allow Discount Change:

If "Enable Price List and Discount List" is enabled, you can still allow discount change.

  • Records Default Format :

If you have license for Records Management, you will have option to attach records directly to tickets and ticket replies. This will allow users to view those records. The default format set here will be used to display the records (quotation, invoices etc.)

User Types

In any Business, there are many user that interact with company at different stages for their work. Application supports various user types like: Employee, Customer, Supplier, Dealer, Distributor, Agent etc.

You can enable of disable user types from the list. There are two options. Enable or disable from registering for login and enable or disable from creating an account. Note that account creating means allowing adding them in records (e.g.: quotation / invoice).

Note

You cannot create a custom user category on your own. If you require a new user type, you must submit a formal request. This is because changes to user categories impact the entire system design.

The "My Company" user type means the company which will issue a record (e.g.: quotation / invoice).

You can create multiple "My Company" Accounts of you are running multiple companies within same Application.

This is particularly useful when:

  • A single sales or marketing team handles inquiries for multiple group companies.
  • Customers often request products or services from various companies within the same group.
  • You need to issue quotations, purchase orders, or sales invoices from different companies under a shared management.

It’s important to understand the distinction between login users and accounts (ledgers):

  • A ledger represents a company or entity in the system (e.g., a supplier, customer, or distributor).
  • A login user is a person who can access the system with credentials.

Each ledger (account) can have multiple login users. For example:

  • A supplier may have two employees with separate login credentials.
  • Both users will access the same data tied to that supplier’s account.

This structure ensures secure and shared access to relevant information without data duplication.

Languages

The system allows you to enable multiple languages for user selection.

Important

To ensure proper functioning, Each language you want to support must have a corresponding YAML (.yml) file placed in the following directory: "wwwroot/Content/Resources".

Tip

To create a language file you should start by modifying the default en-US.yml file to match your preferred terminology and vocabulary. Use this link: https://akmultilanguages.azurewebsites.net/ to create YML for your selected language and place it in the directly stated above. You can edit the vocabulary used in the system before generating new language files. See the "Set Vocabulary" menu option for editing terms and phrases according to your business needs.

Set Vocabulary

The system provides flexibility to define your own vocabulary, allowing you to tailor terminology to suit your business or industry needs.

Custom vocabulary lets you replace default terms used in the system.

For example:

  • You can replace “User” with “Investor”, “Member”, or any term relevant to your organization.

This customization applies to all supported languages.

How to Modify Vocabulary

There are two methods to update vocabulary:

Option A: Manual Update via Interface

  • Navigate to the Vocabulary section in the system settings.
  • Update terms and labels one by one according to your preferences.
  • This method allows full control but can be time-consuming, as it involves editing hundreds of terms manually.

Option B: Bulk Edit via .yml File

  • Go to the server directory: wwwroot/Content/Resources
  • Download the .yml file for your preferred language (e.g., en-US.yml).
  • Open the file using any text editor (e.g., Notepad).
  • Modify the right side values after ":" as needed.
  • Upload the updated .yml file back to the same folder on the server.
Warning

Ensure correct YAML formatting when editing manually to avoid syntax errors.

Edit Site.css

The look and feel of the application—including colors, fonts, and layout styles—can be customized by editing the Site.css file.

The Site.css file controls the visual appearance of the application. It defines styles such as:

  • Background and text colors
  • Font types and sizes
  • Button and menu styles
  • Spacing and alignment of elements

By modifying this file, you can align the application’s appearance with your brand identity and visual preferences.

Warning

Only a style or CSS expert should modify the Site.css file. Improper changes may break the layout or severely affect the user interface of the entire application.