Custom Role definition mismatch

Google Cloud Apigee
1

Hi there. Confusing situation with paid (Team Bundle) account.

Customer needs a “SystemDeveloper” role that allows APIs to be created etc, but must prevent deploy to production.

I created a new role, ticking all the boxes except deploy to production.

Users assigned that role are not even allowed to view anything related to APIs.

Suspect that has to do with the new “folder-based” permissions versus the old create-role screen that only has tick-boxes for feature access, not folders.

Any clues ? … should I add the role via the Management APIs and not via Edge UI ?

8182-sysdev.jpg
8182-sysdev.jpg843×554 51.3 KB

The example SystemDeveloper user

8183-sysdev2.jpg
8183-sysdev2.jpg212×256 11.4 KB

and the access the user has :frowning:

8184-sysdev3.jpg
8184-sysdev3.jpg963×227 16.7 KB

So we have resorted to making everyone Org Admin until I can sort this out !

2

Thanks for the post. Sorry about the delay.

This behavior seems surprising, and incorrect.

Let me look into it.

3

8238-role.jpg
8238-role.jpg883×887 51.9 KB

Hi @Robin Martin, I tried the same what you wanted and it works for me. I am attaching the screenshot for your reference. Thanks..

4

Howdy. I am really glad it works for you.

Now we need to find out why it doesn’t work for us, however.

Are you on a trial org, team-bundle, on-premise or something else ?