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
On most forms that handle creating resources (e.g. metrics, SDK Connections, etc) when creating the resource we fetch a list of projects the user has readAccess to, but in some cases, while the user may have readAccess for that particular project, they don't have permission to create a resource in that project.
E.G.
A user with a global role of noaccess has project-roles for two projects. Project A they have an experimenter role and Project B they have an analyst role.
If the user goes to create an SDK Connection, in the Create SDK Connection form, we show both Project A and Project B in the projects dropdown, but the user only has canCreateSDKConnection for Project A.
If the user tries to add Project B to the SDK Connection, they'll receive a permission error.
The issue is, the permission error doesn't provide any context, so it's not clear to the user. So we can either filter the project list or we can provide a more contextual error message. E.G. "Permission Error: You don't have canCreateSDKConnection in project B".
Related Issues
The text was updated successfully, but these errors were encountered:
Description of Feature
On most forms that handle creating resources (e.g. metrics, SDK Connections, etc) when creating the resource we fetch a list of projects the user has readAccess to, but in some cases, while the user may have readAccess for that particular project, they don't have permission to create a resource in that project.
E.G.
A user with a global role of
noaccess
has project-roles for two projects. Project A they have anexperimenter
role and Project B they have ananalyst
role.If the user goes to create an SDK Connection, in the Create SDK Connection form, we show both Project A and Project B in the projects dropdown, but the user only has
canCreateSDKConnection
for Project A.If the user tries to add Project B to the SDK Connection, they'll receive a permission error.
The issue is, the permission error doesn't provide any context, so it's not clear to the user. So we can either filter the project list or we can provide a more contextual error message. E.G. "Permission Error: You don't have
canCreateSDKConnection
in project B".Related Issues
The text was updated successfully, but these errors were encountered: