Example 1: Use Object Permissions when setting up the database involving different departments so the Users of the related department can only book their Objects.
Example 2: Use in combination with other User Permissions, where e.g. a Finance User should be an Advanced User with Rates (to be able to generate Financial Reports) but should not be able to book Objects.
NOTE:
Since 6.6 SP1 it is also possible to add Web Users to Object Permissions and this way allow them to create bookings with the Global and Actual Status: Confirmed. See details in the last section of the article.
Since 7.1 it's also possible to add Object Permissions on Object Class Level or Division Level (if Division Module is licensed). Please see below!
Enable Object Permission
Click on the Object Permission button in Toolbox > Settings > Server Setup.
- Active: Click it to enable the use of Object Permissions.
- Always Allow: Click on the drop down menu to add those Advanced Users who will have Object Permissions on all Objects.
All other Advanced Users will only be able to create Bookings on the Objects in a Preliminary Object Status, unless they have been given specific Object Permission.
Once they book an Object they will get a conflict window stating: Insufficient Object's Permission.
Objects Permission on specific Users and Objects
Assigning Object Permissions on a specific Object or User will allow only certain Users to book it; open the Object or User, click on Advanced and add the allowed Users by clicking on the drop down arrow next to in the Object Permissions window.
This window will only appear if the Object Permission have been enabled.
Please note that the Users that were set to Always Allow in the Object Permissions window don’t have to be added again.
You can then also COPY the added Users and Paste to other Objects with same permissions.
Object Tree: Prel. Due To Object Permissions
With the Filter option in the Object Tree one can monitor easily all Bookings that were created with insufficient permissions.
This can be useful in specific workflows.
Task Users
When a Task User tries to make a Booking on an User or an Object a pop up: Insufficient Object Permission comes up.
This has nothing to do with the Object Permission setting above, since a Task User can't be given Object Permission to book anything else but himself on a Project Booking.
To book himself, the User Permission Can Book Self needs to be enabled. Task Users can do Task Bookings or Maintenance Bookings if the permission (Control Maintenance) is given.
Web Users
Since 6.6 SP1 it is possible to add Web Users to the Object Permissions, which was not an option before.
When Web Users are added to the Object Permissions, they can effectively create bookings that are confirmed, meaning: the booking gets Global Status Confirmed and Actual Status Confirmed.
Before they could only create a booking with "Actual Status: Preliminary" as they were missing Object Permissions to book certain Objects, when Object Permissions were enabled in the DB.
Apply Object Permissions by Class or Division (7.1)
Since 7.1 it's possible to apply Object Permissions by Object Class or Division. It allows to easily grant Object Permissions to book members of entire class (or multiple classes) or even the entire Division (if the Division module is licensed).
Classes or Divisions user has the permission for, need to be selected after clicking buttons under "If Division" or "If Object Class". Selecting the Class or Division allows the user to book all members of that Object Class or all members of the Division.
F.ex.
If the Editor class is selected it means Peter can book all members of that class.
If Picture Division is selected, it means Peter can book all members of that Division.
If no division or class is selected, user can book all objects (as it's added under "Always allow" section).
Use Dialog to Prevent Booking (7.1)
In 7.1 it's also possible to enable dialog, which then prevents the user from creating bookings completely.
If "Use Dialog to Prevent Booking" is DISABLED and the user does not have permission to book certain objects, they will still book it with Preliminary Object Status. The booking appears on the timeline.
If "Use Dialog to Prevent Booking" is ENABLED and the user does not have permission to book certain objects, the booking is not created at all. The user is presented with an "Insufficient Object Permission" Popup and the booking does not appear on the timeline.
