Configuration
Configuration in Oxari allows you to customize the application to meet your organization's specific requirements. After making selections or changes to the settings, it is necessary to click the “Save” button to approve the changes.
Settings section - location
Below is a description of the various settings in the location section.
1 | Languages available to the user - available are: Polish, English, German. |
2 | Default application language - selectable: Polish, English, German. |

Settings section - file storage
In this section we can configure whether the system should store files and in what location.
To do this, set the slider to “Enabled” and specify the location of the files on disk and the path.

Settings section - attachments
Below is a description of the various settings in the attachments section.
1 | Maximum number of attachments - This setting limits the number of attachments a user can attach to a single ticket or record. |
2 | Maximum attachment size [MB] - Specifies the maximum size of a single attachment that a user can upload. |
3 | Maximum size of all attachments [MB] - This setting defines the total maximum size of all attachments that a user can send within a single ticket. |
4 | Informational text after exceeding the limit - Allows you to define the message that will be displayed to users when an attempt to send an attachment exceeds the established limits. |

Settings section - license
This section allows administrators to manage licenses for various agents and system modules. The administrator must upload the appropriate license file using the “Select...” button. in the license field.
License Details - After uploading the license file, the “License Details” section displays information about various system agents, such as:
Oxari Servicedesk Agent
Oxari Management Agent
Oxari Android Agent
Oxari Windows Agent
For each agent, the current usage status and available limit is shown. For example, for Oxari Servicedesk Agent, there are 3 out of 999 possible instances available.
Modules: Shows which modules are active and how many of them are in use. Modules can include:
Resource management
CMDB
Servicedesk
Workflow
Document management
Mobile management
Limits and license expiration: Limits for specific functions are also shown, such as the number of resources and configuration items that can be managed under the license, as well as the license and support expiration dates for these modules.

Settings section - redmine
This section allows you to integrate your Oxari system with Redmine, a popular project and bug tracking tool.
Below is a description of the various settings in the redmine section.
1 | RedmineAdminApiKey - In this field, enter the Redmine administrator API key. This is a unique identifier that allows Oxari authorized access to Redmine functions. |
2 | RedmineApiBaseUrl - This is where you enter the primary URL of the Redmine API. This is the web address that Oxari uses to communicate with the Redmine server, allowing it to perform operations and queries. |

Settings section - jira
This section allows you to integrate Oxari with Jira, which is a project management and bug tracking tool.
The following is a description of the various settings in the jira section.
1 | Jira instance address - In this field, enter the URL to the JIRA instance with which Oxari is to integrate. |
2 | Username - The username used to log in to JIRA is entered, which will be used by Oxari for authentication in the JIRA system. |
3 | Api Key - An API key used to authorize connections between Oxari and JIRA. It is a security feature that allows secure connection and data exchange between the two applications. |

Settings section - remote connections
VNC in Oxari. VNC, or Virtual Network Computing, allows you to control your computer remotely. In this section, we can configure various aspects of VNC connections.
The following is a description of the various settings in the VNC section.
1 | VNC - client port - Here you enter the port number that will be used by VNC clients to establish a connection. The standard port is 5900. |
2 | VNC - client return port (mobile agents, devices outside the local network) - This field is for the port that will be used for callbacks from clients that are outside the local network, for example, by mobile agents. |
3 | VNC - write the base address for the callback (mobile agents, devices outside the local network) - In this field you enter the base URL that will be used to initiate VNC callbacks. |

Settings section - email filter
This section allows system administrators to configure email filtering.

User interface section - general
Below is a description of the various settings in the general section.
1 | Organization Logo - A place where you can upload and manage your company logo to be displayed in the application. |
2 | Menu logo - Option to upload a logo to be displayed in the application menu. |
3 | Menu title - A field for entering the title that will appear in the application's side menu. |
4 | Tab title - Ability to specify the text displayed as the tab title in the browser. |
5 | Application color style - Selects the color palette for the application, such as the default Oxari style. |
6 | Main menu color - Set the background color for the application's main menu, such as dark. |
7 | Favicon - Upload a site icon (favicon) that appears in the browser tab. |
8 | Customer Notification Panel - Checkbox that allows you to enable or disable the customer notification panel. |
9 | Authentication by Active Directory - An option to integrate the system with Active Directory services to manage user authentication. |
10 | Automatic authentication of domain accounts - Ability to automatically log users in based on their domain accounts. |
11 | Adding anonymous requests from the login screen - Checkbox that allows users who are not logged into the system to add requests. |
12 | URL WebConsole, URL WebAPI and URL Helix API - Fields to specify URLs for the web console and API. |

User interface section - anonymous portal
This section allows you to enable or disable access to the anonymous user portal. When the option is enabled (switch flipped to “ON”), users can access certain parts of the system without logging in, which can be useful for functions such as the bug report or request system, where user anonymity is desirable.

User management section - organizations
In this section, it is possible to add a GUS key, for automatic completion of contractor data in the User Management > Organizations tab.
You can get the key by contacting the Central Statistical Office. more information and instructions on the CSO API Portal website.

Document management section - document statuses
In this section we can add, edit and delete document statuses.
To add a new status, click the “New status” button. and then enter the name of the status, select the appropriate color and click the “Save” button.
Statuses can be edited or deleted using the following buttons.

Document management section - register of processing activities
In this section, we can configure a form for documenting personal data processing activities in the Oxari system. This is a typical component of systems for information management and compliance with data protection regulations, such as RODO (General Data Protection Regulation).
To set up a form, click the “New Activity” button.
The created form can be edited or deleted using the following buttons.
In the form, you can enter information such as:
Number and name of the processing activity.
The name of the data set to which the processing applies.
The purpose of the data processing.
Categories of personal data processed.
The source of the data.
Information about the data controller and its contact information.
Categories of recipients of the data.
Legal basis of data processing.
The planned date of deletion of the data.
Name of the data processor and contact information.
Name of the system or software used for data processing.
General description of technical and organizational security measures.
Information on data transfer to a third country or international organization.
Required documentation related to data processing, such as DIPA (Documentation of Impact Privacy Assessment) or documentation of appropriate safeguards.

Desktop agent - version section
This section relates to version management and agent installation on the Oxari system.
Below is a description of the various settings in the version section.
1 | Available agent versions - A list of downloadable versions of the Oxari system agent. This displays the specific version of the installer (e.g. Oxari.Agent.Desktop.Setup.1.32.msi) that can be downloaded and installed on client computers. |
2 | Installer - A section where you can select a specific version of the agent that is valid for system users. |

Agent desktop section - general
Below is a description of the various settings in the general section.
1 | User interface -.
|
2 | Run time -
|
3 | Hardware scan -
|
4 | Software scan -
|
5 | System process scan -
|
6 | ServiceDesk -
|
7 | Desktop preview -
|
8 | Remote Desktop (VNC) -
|
9 | Windows Remote Assistance (MSRA) -
|