roles

11 Topics

Ranks, Roles & Badges
Ranks, Role & Badges There are 3 main types of Community progression,Ranks, Roles & Badges. Ranks are determined by your interaction and engagement on Community. LogicMonitor Ranksbelow are to help you identify LM employees, the higher the number the more engagement, assistance and training an employee has had. LM Community Conqueror LM Community Champion LMer - LogicMonitor Employee Member Ranks below are achieved by engagement in the Community, the higher the number the more engagement, assistance and helpfulness a member has contributed. Below is how each of these rank, beginning with “New to the Community”, userwill progress up these ranks based on helpfulness, engagement and tenure. Level 1-3 are more challenging to receive! Quantum Professor - Top Community contributor Atomic Advisor Amplified Advocate Cobot Collaborator HypersonicEnthusiast ProcessorParticipant Cybernetic Observer Neophyte - New to the Community Roles Admin - Community Platform Administrator Community Manager - Manages Community Moderator - Manages posts Super User - Members with additional privileges Registered User - All other members of the Community Badges There are a wide range of badges you can earn, some are based on engagement, others are based on special groups you belong to. Engagement Badges We have manydifferent badges based on interaction and engagement. While we can’t tell you exactly what they are, because that would lead to “gaming the gamification”, we can tell you the more you like, comment, create, and answer the more badges you win! Below is the list of Engagement badges you can earn, each one rewards a special Robot Badge! Quantum You have incredible knowledge about all things LogicMonitor! Kinematic You are the forces which causes the motion! Cobot You are designed to help people Autonomous You have the power to make your own decisions Swarm You are distributing answers in a decentralized way! Servo Known for precision and performance efficiency B-Bots You are educating others with replies! Cybernetic Known for your communication and feedback! Bionic You are becoming a Bionic force! Mechatronic You are a multidisciplinary genius. Gravitational You are achieving equilibrium! Gadget You created your first topic, that's ingenious! FIRST For Inspiration and Recognition of Science and Technology Other Badges Holiday badges for logging in that day. LM Community Champion for LM staff trained on the Community Platform. LM Author to identify our LM content writers.
A11ey
2 years ago Place Welcome
189Views
13likes
0Comments
Permissions for Datasource, Alert, and Escalation Chain Groups
As we move towards a DevOps model, we increasingly have a need for small teams to have full admin access to the tools they use to manage their IT services. When it comes to LogicMonitor, this has proven difficult with the existing role permission model. DevOps pods would like to be able to manage their own datasources, alerts, and escalation chains but this isn't possible unless we give them broad access rights to those areas, which could cause significant harm to other groups of monitoring users. For example, an inexperienced DevOps user could inadvertently modify a datasource that applies to all Windows devices or they could create an alert rule that causes alerts not to be delivered to other users. To solve this problem, I'd propose that LogicMonitor offer alert groups, escalation chain groups, along with the existing datasource groups. Then, LogicMonitor could provide the ability to restrict roles to manage these specific groups. DevOps pods could be given the ability to manage their own custom subset of datasources and set up their own alerts in a rule range after the main set of rules.
stuart_vassey
7 years ago Place Archive
5Views
4likes
1Comment
Hide Disabled Datasources object
Please add option to hide the Disabled Datasources object in the Resources tree fromusers who do not have Manage or higher privileges.
Mosh
6 years ago Place Archive
6Views
1like
0Comments
Create role for API only user
Problem I havea 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 securityproblem 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
Jeffrey_McGover
8 years ago Place Archive
20Views
1like
3Comments
Allow Role Assignment to Nested Dashboards
I would like the option to assign view/manage role access to dashboards that exist within a dashboard group. We usewall 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 contactview 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.
gf1
9 years ago Place Archive
3Views
1like
0Comments
Expand role view permissions to include SDT
I would like to propose that there be an additionalcolumn added to both theDevices and Servicesuser permission selectionto allow a user role to manage Scheduled Downtime. Our organization would like to allow application ownersto manage their own SDTs without giving saidgroup management rights to those devices or services inthe logic monitor console.
Vatar
9 years ago Place Archive
4Views
1like
1Comment