Changes between Version 1 and Version 2 of Ticket #419, comment 4
- Timestamp:
- 09.03.2013 17:00:05 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #419, comment 4
v1 v2 1 1 Yes, a home workspace for every user is a good idea. And, as soon as the READ permission is implemented it could be a true private workspace. 2 2 3 Then, model-wise the question arises: how to control weather an user is allowed to join an arbitrary workspace .Instead of introducing different types of workspaces, this could be handled by terms of ACL as well. We could exploit the CREATE permission (for the moment it is applicable only for types) for that:3 Then, model-wise the question arises: how to control weather an user is allowed to join an arbitrary workspace? Instead of introducing different types of workspaces, this could be handled by terms of ACL as well. We could exploit the CREATE permission (for the moment it is applicable only for types) for that: 4 4 5 5 When a workspace's ACL contains a CREATE permission for the USER role, every (authenticated) user is allowed to join. If, on the other hand, that ACL entry is missing no one is allowed to join, what results in a home/private workspace.
