Previous versions (before 2.0) allowed for granular can_edit DAG permissions so that different user groups can trigger different DAGs and access control is more specific. Since 2.0 it seems that this does not work as expected.

How to reproduce:
Create a copy of the VIEWER role, try adding it can dag edit on a specific DAG. **Expected Result:** user can trigger said DAG. **Actual Result:** user access is denied.

It seems to be a new parameter was added: **can create on DAG runs** and without it the user cannot run DAGs, however, with it, the user can run all DAGs without limitations and I believe this is an unintended use.

tests/www/test_views.py
self.clear_table(models.Variable)
        super().tearDown()
    def test_can_handle_error_on_decrypt(self):
        
        self.client.post('/variable/add', data=self.variable, follow_redirects=True)
        
        Var = models.Variable  
        (
            self.session.query(Var)
            .filter(Var.key == self.variable['key'])
            .update({'val': 'failed_value_not_encrypted'}, synchronize_session=False)
        )
        self.session.commit()
        
        
        resp = self.client.get('/variable/list', follow_redirects=True)
        self.check_content_in_response('<span class="label label-danger">Invalid</span>', resp)
    def test_xss_prevention(self):
        xss = "/variable/list/<img%20src=''%20onerror='alert(1);'>"
        resp = self.client.get(
            xss,
            follow_redirects=True,
        )
        assert resp.status_code == 404
        assert "<img src='' onerror='alert(1);'>" not in resp.data.decode("utf-8")
    def test_import_variables_no_file(self):
        resp = self.client.post('/variable/varimport', follow_redirects=True)
        self.check_content_in_response('Missing file or syntax error.', resp)
    def test_import_variables_failed(self):