Custom Role definition mismatch

[robinm]

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 ?

The example SystemDeveloper user

and the access the user has 😞

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

[dchiesa1]

Thanks for the post. Sorry about the delay.

This behavior seems surprising, and incorrect.

Let me look into it.

[#3]

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

[robinm]

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 ?