View Categories

Users Screen

Table of Contents

Last verified with: 10.8.6.0

Users are configured in Setup / Users & Accounts / Users / Users

Overview #

The Users screen is used to create and manage the internal users who can access LogiSense Billing. A user can be configured for standard AdminPortal access or as an API-only user, depending on how that person or integration should interact with the system.

This screen also provides access to user login history so administrators can review authentication activity, including whether login attempts were successful and where they originated.

Prerequisites #

  • Roles must be configured before users can be added.
  • SMTP settings must be configured if you want the system to send password setup or reset emails.

Users Panel #

The Users panel on the left lists the configured users. The list also displays the current status of each user, such as Enabled, Disabled, or Suspended. Select a user to view or edit their details in the panel on the right.w.

Actions #

IconDescription
Adds a new user

Edit User Panel #

In single-sign on environments users pushed from identity providers will be listed here. Most settings for these SSO users will be read-only in LogiSense Billing. User management for these users will occur in the identity provider portal and changes to the user will be pushed to LogiSense Billing.

If a user is pushed from an identity provider without a group set on that user then the user will be assigned the ‘Read Only Core’ role in LogiSense Billing until a group is assigned in the identity provider portal.

Fields #

  • User Name: Defines the user name used to sign in.
  • Display Name: Provides a more user-friendly name that can be shown elsewhere in the application.
  • First Name: Stores the user’s first name.
  • Last Name: Stores the user’s last name.
  • Email: Stores the email address used for user communication, including password-related emails when that workflow is available.
  • API Only User: Determines whether the user is limited to API access only. When this option is enabled, the user is configured for integration use rather than normal AdminPortal access.
  • Role: Determines the permissions assigned to the user.
  • Time Zone: Controls the time zone used for the user’s view of time-based data.
  • Locale: Determines how region-sensitive values such as dates are presented to the user.
  • Authentication Type: Defines how an API-only user authenticates. This field is shown when API Only User is enabled.
  • Generate API Key: Creates an API key for an API-only user when the selected authentication type supports client secret authentication.
  • User Status: Determines whether the user can access the system. This is typically used to enable, suspend, or disable access.
  • API Key: Displays the generated API key for an API-only user. The value is read-only and can be copied for use in an integration.
  • SAML: Stores the SAML user identifier when SAML-based authentication is used.
  • Send Reset Password Email: Sends a reset-password email to the selected user when that workflow is available for the user’s authentication type.

API-Only Users #

API-only users are typically created for integrations, automated processes, or external systems that need to interact with LogiSense Billing through the API without signing in to the Admin Portal interface. This allows organizations to separate system-to-system access from normal interactive user access.

When configuring an API-only user, the most important areas to review are:

  • API Only User: Enable this option to identify the user as an integration user rather than a standard Admin Portal user.
  • Role: Assign a role that grants only the permissions required by the integration.
  • Authentication Type: Select the authentication method the integration will use.
  • Generate API Key: Use this option when the selected authentication type requires a client secret or API key.
  • API Key: Copy and store the generated key securely so it can be used by the integration.
  • User Status: Confirm the user is in a status that allows the integration to authenticate successfully.

Because API-only users are often tied to production integrations, changes to their authentication settings, role, or status should be made carefully and coordinated with the teams responsible for the connected system.

Accounts Tab #

The Accounts tab can be used to review account relationships for the selected user. A Search Accounts field is available at the top of the tab to help narrow the account tree when that view is used.

Login History Tab #

The Login History tab displays the user’s login attempts.

Login History List #

  • Message: Describes the result of the login attempt.
  • Date: Displays when the login attempt occurred.
  • Source IP Address: Displays the IP address from which the login attempt originated.

Guides #

Adding Users #

  1. In the Users panel, click Add.
  2. Enter the user’s account details, including User Name, First Name, Last Name, Email, Role, Time Zone, Locale, and User Status.
  3. If the user should be API-only, select API Only User and complete the API-specific fields.
  4. Click Save.

Editing Users #

  1. In the Users panel, select the user you want to update.
  2. Update the user details as needed.
  3. If the user is configured as API-only, review the Authentication Type and API key details as part of the update.
  4. Click Save.

lsb-screen-help