@@ -154,10 +154,10 @@ definition workspace {
154
154
// The permissions come from the owning team roles, or individually granted
155
155
// permissions. The individual grants must still be apart of the team.
156
156
permission view =
157
- // Some perms require view as well
158
- edit + delete + select_template_version + ssh +
159
- // Give view permissons to any role that requires reading the workspace to conduct their actions.
160
- owner->view_workspaces + viewer
157
+ // Some perms require view as well
158
+ edit + delete + select_template_version + ssh +
159
+ // Give view permissons to any role that requires reading the workspace to conduct their actions.
160
+ owner->view_workspaces + viewer
161
161
permission edit = owner->edit_workspaces + editor
162
162
permission delete = owner->delete_workspaces + deletor
163
163
// TODO: Maybe a caveat to check if the selected version is the active template version, and if that is allowed.
@@ -216,7 +216,7 @@ definition template {
216
216
permission edit_pemissions = owner->manage_template_permissions
217
217
218
218
// Use is permitted by the owning team.
219
- permission use = owner
219
+ permission use = owner + owner->parent
220
220
}
221
221
222
222
definition template_version {
@@ -231,6 +231,8 @@ definition file {
231
231
permission view = template_version -> view
232
232
}
233
233
234
+ // TODO: How do we handle provisioners? Should we keep using tags?
235
+ // Add actual relations?
234
236
definition provisioner {
235
237
// owning team for pulling permissions through.
236
238
relation owner: team