Pondering the Security Model
Not sure where this is on the priority list, but adding here so others can add input.
As we add more users and can automate production forecasting and economic modeling, People are asking about ways to make their results official.
We want to use this for official purposes, we need to raise some fences so that people don’t step on each others toes and that we keep the auditors happy. In order to do thins we need to compose some kind of Hierarchy . The Project Tree. Right now this is not not a tree, its the wild west.
I would love to get input from all ComboCurve users and administrators about how they manage the tool, and from the devs at Inside Petroleum on what are the plans. Ill throw out a few of my ideas here too.
Security Access
The ability to access certain Areas of the hierarchy
As we add users we need to be able to control where they go. What are the plans to control this?
Can we use Azure AD to automate/synchronize user roles and security access?
Is there a configuration file ?
Role Access
The ability to use certain functions at different levels in the hierarchy.
We need to dictate what users do on different sides of the application.
With more users how do we control and manage how users can perform certain functions in specified areas. Can we use tags to manage this?
Locking things down
What are the plans to lock down certain forecasts in certain projects
Apply certain security roles to Forecasts within Projects
Apply security roles to tags
Lock down tags
Automating roles and security
What are the plans for an Administration Console
What goes into the console
Other config stuff.
Waiting for input.
-Lucas