Handling sensitive data like Human Resources/Payroll

Hi - 

 

Has anyone added sensitive data, like human resources info, into Domo?   Looking for learnings around controls, data sharing, etc... (e.g. Is there a way to set this up so Domo Admins can't see the data)

 

Thanks,

 

Eli

Best Answer

  • Nick_Bertz
    Nick_Bertz 🟡
    Accepted Answer

    I was having some trouble still, but my most recent try seems to have allowed these links to work!

Answers

  • Hi all,

     

    Can anybody help @TheDataGuy out?

    Thanks!

  • All data is accessible to Owners and Admins in Domo. If you have users who should not have access to some data on the instance then they should not be an Admin. You can look for articles in the Help Center about Personalized Data Permissins (PDP) and Publication Groups. Both of these tools allow customized data restriction for users on different levels, but they will not restrict Admins or Owners of the data.

     

    http://knowledge.domo.com?cid=pdp

     

    http://knowledge.domo.com?cid=pubgroups

     

    http://knowledge.domo.com?cid=pdpvspubgroups

  • Hello,

     

    Are those links still valid?  I cannot reach the destination.  Can you point me to these documents?

     

    Thank you,

    Nick

  • Nick,

     

    The links should work but you will need to login to the help center with your Domo credentials.

     

    If it still doesn't work can you paste a screen shot of what you are seeing?

     

    Thanks!

     

  • Here are the screenshots as requested....

     

    pdp.PNGpubgroups.PNGpdpvs.PNG

  • Nick,

     

    Thanks for the screen shots.

     

    Can you access the main landpage of the Help Center? Are you prompted to enter your Domo login credentials?

     

    If you can access try to paste the url from one of the articles once you are there.

     

    If not then it's not clear what is going on as these are customer facing and we don't see any issues with the Help Center at the moment.

     

    Let us know!

     

     

  • Maybe there was some cahed data in your browser, I guess a good step for next time is clear your cache.

     

    Glad it worked!