Alarm Engine Support Forum ElkConnect user-level restrictions

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #8622
    Keith Belt

      When logged into ElkConnect with a basic user-level account, most of the configurable settings are inaccessible.  For example, you can see all the zones and their status, but you can’t access the zone’s configuration parameters or add new sensors.  The only exception to that rule are User configurations, at least from what the client is telling me.

      But this commercial client does not want employees to be able to add or change users.  He’d prefer read-only access across the board.  That way employees that need to monitor the system (e.g., maintenance staff) can do so, as well as arm or disarm the system (e.g., security staff), but they can’t create new users.  Being able to create or access User configurations is actually a BIG security flaw in this situation.  The alternative is to not allow any of those staff to have ElkConnect, which creates its own inefficiency and inconvenience.  Maybe make only the Master User be able to add\change new users?

      Is there a way to make User data read-only like everything else?  Or is that feature already there and we can’t see it because we’re all looking with too-high permissions to be affected (Installer, Master)?

       

      #8623
      Michael Burrell

        Master users are the only users other than installer level users that can configure user settings.

        You or a master user needs to create a new User Group with the level of permissions the lower level user has access to. User Groups is how you control this. The new user group by default will have no ability to make setting changes to the system. If you chose, you can limit access to automations, arm, and disarm

        Once you have the User group created, assign the users you do not want to have user creation abilities to it

        only users assigned to the master or installer group can make edits to the user configuration.

         

        #8626
        Keith Belt

          Thanks!  I figured the problem was not configuring enough different User Groups to see different behavior.  The only people in the system so far, were all set as Master Users.

        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.
        Scroll to Top