Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-6206 Restrict report and dashboard creation to collections
  3. OPT-6333

Create new Optimize authorization for entity creation

XMLWordPrintable

    • Not defined

      Optimize users without entity editing permission should not be able to create entities such as reports/dashboards/collections. We should add interpretation of these permissions from the configuration file and expose them to the UI as an Optimize authorization, allowing the UI to hide options when the user is considered a READ-ONLY user

        This is the controller panel for Smart Panels app

            [OPT-6333] Create new Optimize authorization for entity creation

            Joshua Windels created issue -
            Joshua Windels made changes -
            Status Original: Open [ 1 ] New: Ready [ 10005 ]
            Joshua Windels made changes -
            Status Original: Ready [ 10005 ] New: In Development [ 10312 ]
            Joshua Windels made changes -
            Description Original: An Optimize user can be granted READ Application Authorization in the engine. In this scenario, Optimize users with such a permission should not be able to create entities such as reports/dashboards/collections. We should add interpretation of these permissions and expose them to the UI as an Optimize authorization, allowing the UI to hide options when the user is considered a READ-ONLY user New: An Optimize user can be granted ACCESS Application Authorization in the engine. In this scenario, Optimize users with such a permission should not be able to create entities such as reports/dashboards/collections. We should add interpretation of these permissions and expose them to the UI as an Optimize authorization, allowing the UI to hide options when the user is considered a READ-ONLY user
            Joshua Windels made changes -
            Assignee Original: Joshua Windels [ joshua.windels ] New: Helene Waechtler [ helene.waechtler ]
            Status Original: In Development [ 10312 ] New: In Review [ 10212 ]
            Helene Waechtler made changes -
            Assignee Original: Helene Waechtler [ helene.waechtler ] New: Joshua Windels [ joshua.windels ]
            Status Original: In Review [ 10212 ] New: Rework [ 11413 ]
            Sebastian Bathke made changes -
            Labels Original: SUPPORT current_release potential_for_3.9 New: SUPPORT potential_for_3.9
            Joshua Windels made changes -
            Status Original: Rework [ 11413 ] New: In Development [ 10312 ]
            Cigdem Ilhan made changes -
            Labels Original: SUPPORT current_release potential_for_3.9 New: SUPPORT potential_for_3.9
            Joshua Windels made changes -
            Description Original: An Optimize user can be granted ACCESS Application Authorization in the engine. In this scenario, Optimize users with such a permission should not be able to create entities such as reports/dashboards/collections. We should add interpretation of these permissions and expose them to the UI as an Optimize authorization, allowing the UI to hide options when the user is considered a READ-ONLY user New: Optimize users without entity editing permission should not be able to create entities such as reports/dashboards/collections. We should add interpretation of these permissions from the configuration file and expose them to the UI as an Optimize authorization, allowing the UI to hide options when the user is considered a READ-ONLY user

              Unassigned Unassigned
              joshua.windels Joshua Windels
              Joshua Windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: