You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the new admin permissions setup, if an API backend is composed of multiple unique URL prefixes, we had setup scopes for each one of those URL prefixes and granted permissions to those separate scopes. The intention was that any admin that had permissions for all the prefixes contained in an API backend would be able to administer those API backends. However, due to a bug in the permissions logic, this was note the case, and agencies that had API backends involving multiple, distinct URL prefixes were forbidden. I believe the only agency this affected was FDA.
The text was updated successfully, but these errors were encountered:
In the new admin permissions setup, if an API backend is composed of multiple unique URL prefixes, we had setup scopes for each one of those URL prefixes and granted permissions to those separate scopes. The intention was that any admin that had permissions for all the prefixes contained in an API backend would be able to administer those API backends. However, due to a bug in the permissions logic, this was note the case, and agencies that had API backends involving multiple, distinct URL prefixes were forbidden. I believe the only agency this affected was FDA.
The text was updated successfully, but these errors were encountered: