Search the Community

Showing results for tags 'Users'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • LogicModule Exchange
    • LM Exchange
    • LM Staff Contributions
  • Product Announcements
    • LogicMonitor Notices
  • LogicMonitor Product Q&A
    • Feature Requests
    • Ask the Community
    • From the Front

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 5 results

  1. Please move the Manage gear icon to the left of the Users list view to be consistent with rest of UI. It also irritates and confuses our users when the icon is hidden when the list view overflows (due to items where the Roles column has mutiple items), because it's on the right hand side.
  2. Jeffrey McGovern

    Create role for API only user

    Problem I have a datasource that collects information from the LogicMonitor API. In order for this to work correctly I need a valid user on the LM platform with a valid API token. I can see two potential paths forward. Case 1 - Use my existing account as the datasource author with my API token. This has a big downside that if I have to leave the company for any number of reasons and my account gets disabled this datasource will stop working and is customer facing. This is probably not so good. Case 2 - Create a 'service account' inside LogicMonitor that can have its' own API token and if any one human needs to leave the company there really is not a big problem. The issue with this is that this user has a username and a password that can grant it access to the UI under all the permissions granted by the role but this account should/will never be used within the UI. This also generates a potential security problem because the password will most likely never be rotated because as long as the API user and token work this is simply going to sit there. Request Be able to create a new user type of 'API only' which will never have access to the UI and therefore you should not have to set any of the UI specific information for the account. This would remove the need for any of this information under that account: First/Last name/Email/Password/Force password change/2-factor/Phone/SMS/SMS Email format
  3. I would like the option to assign view/manage role access to dashboards that exist within a dashboard group. We use wall mounted displays that cycle dashboards in a group for various clients using the slideshow feature. These displays are used by our support team so that they can keep an eye on clients at a high-level. We also want to provide a key contact at some of these client companies with view access to their respective dashboards. I see two ways to accomplish this currently: 1. We can clone the dashboard within the client dashboard group, then assign our client contact view access to the cloned dashboard. This allows us to keep the functionality of the dashboard group for our support team, but requires several duplicate dashboards. 2. We can skip the dashboard group and assign access for our support team and client contacts on a per-dashboard basis. This omits duplicate dashboards, but requires additional management of role permissions when creating new dashboards. Adding the ability to assign role permissions to nested dashboards would allow for simple access management for the support team, providing access to all dashboards within the "Clients" group, while also allowing one-off access to individual dashboards for client contacts without having to manage multiple dashboards per client. A simple toggle arrow (as is used in the Devices tree) could be implemented as a UI element to add this basic access management.
  4. I would like to propose that there be an additional column added to both the Devices and Services user permission selection to allow a user role to manage Scheduled Downtime. Our organization would like to allow application owners to manage their own SDTs without giving said group management rights to those devices or services in the logic monitor console.
  5. We need to be able to grant a user to be able to see only select or tagged instances of a datasource. For example VM statics inside a vcenter. We have Instance Groups with the tags by group or client. Need to be able to link users to see those. or a new security Tag we can add.