Admin Users with Restricted Data Access

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Dave B
    Junior Member
    • Jul 2021
    • 15

    #1

    Admin Users with Restricted Data Access

    We would like to have one of our users act as a system admin with the privileges to make configuration changes - entities, fields, layouts, workflows etc. However in order to comply with GDPR regulations it is important that this user cannot have any access to certain data elements - for example an employee record that might contain personal information. So our request is to be able to limit the data access of an admin user (and not allow that user to change their own data access!)
  • yuri
    EspoCRM product developer
    • Mar 2014
    • 10084

    #2
    Hi Dave,

    Unfortunately, it is not feasible (at least without a super big overhaul). A user that can manage workflows, BPM, formula, etc., even if they were not admin, they can just make themselves admin using the available tools. Or just extract data using these tools. It would have been a bogus feature, that we would need to acknowledge as such otherwise, we would just get tons unfixable security reports.

    Comment


    • Dave B
      Dave B commented
      Editing a comment
      Yuri - I hear what you say, but I do think that this is a serious GDPR issue. Are there any other ways of hiding data from an admin user
  • yuri
    EspoCRM product developer
    • Mar 2014
    • 10084

    #3
    I do not think it is a 'serious' GDPR issue.

    If we ever implement this, that admin user would be very limited, so there will be minimal use of it other than configuring layouts and labels.

    Comment

    • yuri
      EspoCRM product developer
      • Mar 2014
      • 10084

      #4
      > Are there any other ways of hiding data from an admin user.

      It is possible to hide certain fields from ALL admin users.

      Example.

      custom/Espo/Custom/Resources/metadata/app/acl.json:
      Code:
      {
          "adminMandatory": {
              "scopeFieldLevel": {
                  "Account": {
                      "emailAddress": false
                  }
              }
          }
      }

      Comment

      Working...