Justification or Use Case for Access to Resources in Domo


Hello everyone!
I am beginning to build out better data governance policies for my instance and documenting them for all users to see. I'm specifically struggling with policy and documentation around a user explaining why they need access to a particular resource, so the applicable approvers can make an informed access decision. I want policy to require users to provide this information in their request, but I'm struggling to come up with a good name for it (business case, business justification, use case, business impact?) and explain it well enough to the user that we get the information we are looking for. We want them to explain how they will use it and what impact it will have on our business. If they don't have a good enough explanation or the impact isn't great enough or we determine these things to be outside of their role, the access request will be denied. Any help, ideas, thoughts here are very much appreciated! And I've been struggling to find resources online about this, so if you have some of those to point me in the right direction, that would be awesome. Thanks!
Was this comment helpful? Click Agree or Like below.
Did this comment solve your problem? Accept it as the solution!
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 306 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 112 SQL DataFlows
- 649 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 786 Beast Mode
- 78 App Studio
- 43 Variables
- 742 Automate
- 187 Apps
- 474 APIs & Domo Developer
- 67 Workflows
- 14 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 406 Distribute
- 117 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 139 Manage
- 136 Governance & Security
- 8 Domo Community Gallery
- 44 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive