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
As our permission system gets more complicated, answering the question “what resources does this Flagsmith user have access to?” is becoming annoying. Users can now have permissions directly, through groups, through roles, or through roles attached to groups. This will allow an administrator to see which resulting permissions a user has from any of their methods of attaching them.
The text was updated successfully, but these errors were encountered:
I guess this will need some form of API, we'd want to return where the permission is coming from, something like
/api/v1/environments/{environment_api_key}/user-permissions/{id}/all
/api/v1/projects/{project_id}/user-permissions/{id}/all
{
"admin": boolean,
"permissions": {
"permission_key": string,
"tags": number[],
"derived_from": { // if both of these are undefined it means its a user permission
"group": number | undefined, // what group it came from if any
"role": number | undefined // what role it came from if any
}
}[]
}
As our permission system gets more complicated, answering the question “what resources does this Flagsmith user have access to?” is becoming annoying. Users can now have permissions directly, through groups, through roles, or through roles attached to groups. This will allow an administrator to see which resulting permissions a user has from any of their methods of attaching them.
The text was updated successfully, but these errors were encountered: