No, it is not a bug. As @tonyanshe mentioned, the "issue" is caused by the rights for IP Spaces not being included in the "Default Rights Bundle".
A right being part of a default role does not mean that right is automatically published to the tenant, to achieve that, the right must be added to the right bundle used to publish permissions to the organization (usually it is the default one, but it can be a different one).
Original Message:
Sent: Jun 09, 2024 12:32 PM
From: Alexey Koznov
Subject: IP Spaces menu missing using OrgAdmin User
I suppose that it is a bug, and default role should also have a permission to use IP spaces because out of the box Org Admin has these permissions, but Default role doesn't.
Original Message:
Sent: May 25, 2024 02:34 PM
From: tonyanshe
Subject: IP Spaces menu missing using OrgAdmin User
You need to add the rights to the Default Rights Bundle also in order for a Tenant to have them.
Original Message:
Sent: May 23, 2024 09:35 PM
From: Antonio Mercado
Subject: IP Spaces menu missing using OrgAdmin User
Hello everyone,
It is not possible to assign an IP or subnet in the IPSpace defined using a tenant user with Organization Administrator rol. In fact, the menu does not appear in the networking section.
Reviewing the global role of Organization Administrator, it does have the permissions to view/manage IP Spaces, but in the role at tenant level, the role does not have them.
Provider level:
Tenant level:
Are any special permissions or roles needed?
Any advice or help will be appreciated.