More granular permissions

[w-le]

A current project utilises Zone.metadata as a store for application specific data
Non system admins using a non admin frontend app will be updating Zone.metadata.

1. Should we just find a new home for this kind of application specific (and often completely custom) persistent data? Or should it remain in places like zone/system metadata?

2. If we keep this data in zone/system metadata, then we want to allow specific users or groups to be able to edit that zone.metadata (ideally even specific zone.metadata KEYS), without granting them sys_admin access

[MrYuion]

@w-le, metadata is already standalone technically, though it is normally associated with a zone/system.

[caspiano]

Closed by #169

[caspiano]

@w-le We can now issue scopes based on controllers.
For this case, you can issue zones.read.

@tassja Interested in your thoughts on this.

[tassja]

It looks like they would need to edit? so zones.write ?