building block user permissions not only from the parent
F
Fabian
currently there is the option to have
User Permissions
as input to a building block:Provides the user permissions from the parent meshObject (project or workspace) as a list of objects.
The limitation that it can only be the parent object causes problems for us currently. We have a tenant level building block, but we need to trigger this building block, when Workspace
owners
have changed. We only have the option of getting the project level user permissions.Could you make this user permissions input more flexible, so that we are not limited to the parent meshObject?
Regards,
Fabian
F
Fabian
this is relevant for us as workspace owners represent the main person responsible for the workspace and related resources. which means we have to set the workspace owner in various api calls for downstream systems.
having these as building block triggers would be an enormous help
J
Johannes Rudolph
Fabian Thanks for clarification. I gather you want essentially a choice to receive not only project user permissions (project role bindings) but also receive workspace user permissions.
At the moment I believe workspace level BBs receive those workspace permissions while tenant level BBs receive project permissions, but I do need to double check this.