Permissions - rapla/rapla GitHub Wiki
Groups and permissions are available since rapla 0.11.
Add new sub-categories to "user-groups" to create new groups. You can also create hierarchical groups. Children will inherit the permissions from their parents. Assign the groups to users by editing the user-entry.
You can set permissions for each resource/person by editing it (right click when admin). You can create n permissions for each resource/person. A permission is always assigned to either a user or group.
You can also specify more than one permission per user or group. Then if a user tries to get access, all permissions will be checked and if one permission matches the access specified, permission will be granted to the user: e.g. if one permission denies access for the user and another permission allows access, the user will get access.
There are different access-levels, you can define for each permission:
- can read
- can allocate
- can allocate and create conflicts
- administrator rights
If you choose ''can allocate'' or ''can allocate and create conflicts'' it is possible to specify absolute or relative booking-timeframes for the selected resource. You can, for example, prevent modifying appointments in the past, by setting the relative start-time to 0.
If you choose ''create conflicts'' all users that are matched by the permission, are allowed to create conflicts for the resource.
"permission 1": group "G" can book until the end of the year, but has to book at least 3 days before the resource is needed.
"permission 2": user "U" belonging to G is allowed to create conflicts (but only for the next year)
So user "U" can book in this year at least 3 days before the event, but isn't allowed to create a conflict. He can, however create a conflict for events in the next year.(enough time to resolve the conflict)
When a user creates or edits an event, the permissions for each resource he allocates
are checked against the username and the groups the user was assigned to. Only one permission needs to be fulfilled to successfully allocate a resource. A red "no-parking" sign will be visible left to the resource when the user isn't allowed to
allocate it.
When you edit an existing event, you aren't allowed to modify certain appointments or allocations that would violate any timeframe-constraints, e.g. you can't delete appointments in the past if the relative start-time constraint is set to 0.
See the page permission_modify
Note: you can edit rights in 'resources and persons' pane.
Create or edit existing resource then in resource properties edit proper rights to it.