Inconsistency of Edge and API user permissions

Google Cloud Apigee
1

I noticed that in my Edge there is no role that has access to perform GET, PUT, POST and DELETE operations on /users

By Edge I can list, create, update and delete edge users, but I can not do the same thing for the API:

https://api.enterprise.apigee.com/v1/users

It gave me the following result:

HTTP/1.1 403 Forbidden

Date:
Mon, 06 Nov 2017 11:21:46 GMT
Content-Length:
0
Connection:
keep-alive
Server:
Apigee LB

Why is there such incoherence? Are Edge users only for that organization? Why can not I create a new role in Built-in Roles?

How can I have a user who has GET, PUT, POST and DELETE access permission on all APIs above the organization?

2

@Marcelo Barroso Roles within Apigee are at an organization level not at an enterprise “uber” level. That is how it is currently designed. For more details about roles and at what level you can create them please refer to : https://docs.apigee.com/api-services/content/edge-built-roles