Rule in policy.json to restrict access to user owned resources

asked 2015-05-26 23:00:03 -0500

nd gravatar image

I have observed that when there are multiple users in a tenant/project having say _member_ role, each user still has privilege to perform actions on instances created by other users in the same tenant/project. Is it possible to configure rules in policy.json to allow only the user who created an instance to say start/stop or delete it?

edit retag flag offensive close merge delete