Service Session Console Guide

This page provides a complete guide to using the Service Session section of the Namirasoft Account Console. It clarifies how Service Sessions link Service Users to active machine or automation connections.

What Is a Service Session?

A Service Session represents an active connection for a Service User. It includes information about the device, location, and time of access, and may provide a Token that allows machines to authenticate API requests securely.

Why Service Sessions Matter

Service Sessions enable secure, controlled access for automation tools and external systems. They ensure that each machine connection is authorized and monitored, reducing the risk of unauthorized access.

Overview of Service Session Fields and Options

This section describes the fields you’ll encounter when creating or editing a Service Session in the Console:

• ID (String): The unique identifier automatically assigned to each Service Session record. Used internally by Namirasoft to reference this specific session without confusion.

• User ID (Namirasoft Account’s ID): The unique identifier of the main user account that owns or manages the Service Session. This links the session to its associated primary Namirasoft account.

• Name (String): The display name given to the Service Session, helping to distinguish it from other sessions when viewing or managing multiple active connections.

• Service User (Enum): This is a selectable field where you choose from previously created Service Users to associate with this Service Session. This determines which automated machine account is tied to the session for API or background processing.

• OS (String): This is the operating system detected for the device or system where the Service Session originated (e.g., Windows, macOS, Linux). This is recorded automatically for security and session tracking purposes.

• IP (Integer): This is the public Internet Protocol address from which the Service Session originated. It allows you to verify if a login attempt came from an expected network or location. For security monitoring, this can help detect suspicious activity or unauthorized access attempts.

• Continent (String): This is the continent where the Service Session originated, determined by geolocation lookup of the IP address. It provides a high-level geographic context for the Service Session, which can be useful for global activity analysis.

• Country (String): This is the specific country where the Service Session originated, based on IP geolocation. It enables you to confirm if the login activity matches the Service User’s known location or expected travel patterns.

• City (String): This is the city associated with the Service Session’s IP address. It offers more precise location context to help verify legitimate activity or investigate anomalies in session records.

• Created At (DateTime): This is the exact date and time when the Service Session was initiated.

• Updated At (DateTime): This is the most recent date and time when the Service Session record was updated.