As designed Resource team permissions

[MJ0730]

Affected version

2.2

Not sure if this falls under bug or feature request but...
When trying to add a user to a resource team, if they don't have permission to create new resources, they can't be added as a team member. I think the expected behavior should be anyone is allowed to be added as a team member. Alternatively, split out a separate permission so it's not tied to be able to create new resource.

 

[Mike]

As it stands, this is intentional. Team members can take almost all of the actions that the resource owner can, so it's quite close to them creating the resource themselves and thus we apply this permission check to avoid the team system from effectively bypassing creation permission limits.

If this doesn't work for you, it's likely worth posting a suggestion, though I'd recommend posting some more details as to the "why" so we can understand the motivation.