Adding a User

Creating Users

To add new users to your LogicMonitor account, navigate to Settings > User Access > Users and Roles > Users > Add Users Options > Add User. As discussed next, there are several settings that must be established in order to create user accounts. These settings determine credentials, some basic interface behavior, and a user’s level of permissions.

Note: Role Access view permissions and User Access manage permissions are required in order to provision user accounts.

API Only Access

If toggled on, this option will allow creation of a user only capable of API access. For such a user, only the Username, API Tokens, Roles, Status and Notes fields are relevant. API only users don’t have passwords or other user interface-specific fields, making them a more secure option if you are creating a dedicated user for an API-based integration.

Username

A name or email address to be used to log in to the account.

First Name and Last Name

Name fields to help identify the user.

Email

Primary email address for the user. This contact method will be used for email alert and report delivery.

The email verification link is sent to the users in the following two scenarios:

• When a new user is created
• When the existing user updates the email ID

The users must select the link provided in the email to complete the verification process and activate the account.

Password

The password to be used upon initial login.
The passwords must be a minimum of 12 characters and a maximum of 256 characters, the password must contain:

• At least one uppercase letter
• At least one lowercase letter
• At least one digit
• At least one of the following special characters: ~, !, $, %, ^, (, ), _, –, +, =, }, {, ], [, @, #, &, \, |, ;, :, < , >, . ,?, /

Force Password Change?

By default, this option is checked when creating a new user. It will cause the system to immediately prompt the new user for a password change upon their initial login.

The following two options are available:

• Immediately (force logout for this user): The user will immediately be forced logged out from the LogicMonitor portal. Also, the user will have to reset the password on the next login.
• Next login (requires users to reset the password on the next login): The user will be required to reset the password on the next login.

In both scenarios, the user will receive an email with a link to reset the password. 

Password changes can also be required of existing users at any time. If the user is logged in at the time this option is checked, they will receive a notification stating they will need to change their password the next time they log in. Once the user has completed the password change, the Force Password Change? option resets to unchecked.

Enable Two-Factor Authentication

If this option is selected, the user will be required to use two-factor authentication upon next login. For more information on LogicMonitor’s implementation of this additional security layer, see Two-Factor Authentication.

Phone

Not required. If entered, it is available as a contact method for voice alerts and native SMS alerts.

SMS Email address

Not required. If entered, this email address will be available as a contact method for email SMS alerts.

SMS Email Format

The format for email SMS alert notifications that the SMS email address will receive. Select “Full-text” to receive the entire alert message or “Short (160 chars)” to receive an abbreviated version.

Time Zone

The Time Zone field for all new users defaults to the time zone specified for the LogicMonitor account (as configured in the global portal settings). However, if a user is located in a different time zone, it can be selected from this field’s dropdown menu to allow the user to view and configure time-based data and settings relative to their local region.

When a user account is configured to a time zone other than the global LogicMonitor account, their UI will display time-based data (e.g. alerts, report output, one-time events, raw data, etc.) according to their chosen time zone. Users can easily toggle between their user-specific and account level time zones from the UI header, as shown next.

All events a user configures (e.g. SDT, Collector upgrades, report deliveries, SLA periods, etc.) will be configured, by default, in the user’s specific time zone. However, this can be overridden on a case-by-case basis using the Event time zone dropdown menu, shown next, that accompanies all time-related settings throughout the interface.

User Groups

In the User Groups area of user configurations, you can assign the user to one or more previously-configured user groups. If your organization doesn’t organize users by group, or if the group hasn’t yet been created, leave the table empty to assign the user to the default “Ungrouped” group. For more information on user groups, see the User Groups section of this support article.

API Tokens

The API tokens associated with the user. The API Tokens entered here can be used to authenticate REST API requests, and will assume the role(s) of the user. Make sure to save the Access Key to a secure location when you add an API Token, as that value will not be displayed again.

Roles

The roles assigned to this user. If a user is assigned multiple roles, the user’s privileges are a sum of the privileges of each of the assigned roles. For example, if one assigned role provides view only permissions to all resources, but another assigned role provides manage permissions to all resources, the user will have view and manage permissions for all resources. If yet another assigned role provides view permissions for all dashboards, but no permissions for resources, the user will maintain manage permissions for all resources and additionally gain view permissions for all dashboards. For more information on user roles, see Roles.

View Permission

The View Permission area of a user configuration determines the visibility of the pages on the LogicMonitor Portal. It is a user-level access and view permission. If a toggle for a page is not selected, the user does not have access to that page on the LogicMonitor Portal regardless of the permission levels provided to the user by the assigned role. For example, if a user does not have view permission to Logs, Traces, and Reports, then on the LogicMonitor Portal, the Logs, Traces, and Reports pages are not visible to that user.

However, if the same user has an Admin role with read and write permission to Logs, Traces, and Reports, then the user can access public APIs through tools such as Postman and send API requests for Logs, Traces, and Reports. Before making any API request, LogicMonitor checks for the permissions granted to the user’s role. 

Generally, select all the pages and let the user’s assigned role determine the visibility and access. However, there may be circumstances in which the user needs to be restricted from a particular page.

Status

Users are active by default. Suspended users will be unable to log in to the system.

Note

The user note is for reference. It does not display anywhere else in the interface.