
| 1. | Decide whether this user right group will be able to access events, and if so, whether they will be able to delete, assign, import/export and/or modify events. |
| 2. | If the user right group can Modify Events, choose whether they can modify All or Assigned Events Only. Note that you can only choose one. |
| 3. | Check the box if this group can Modify Event Setup. |
| 4. | You can also choose whether this user right group can access Attendees, Exhibitors or Attendee Online Functions (if you have purchased any or all of these separate modules), and if so, what they can modify within each heading. |
| 5. | Later, when you create events, you will be able to set the lock level for each of them. Use the checkboxes to indicate the Lock Levels to which the user right group can set an event and which lock levels they can modify. |
| a. | Open means the event has just been booked and details have not been confirmed. The event is still “open” to be worked on. |
| b. | Locked can be used to close an event to all staff members except those with the user rights to unlock it. The Locked level is used as a short-term way to prevent other users from modifying an event. |
| c. | A Finalized event has been approved by the client. All details have been confirmed and all contracts and deposits have been received. |
| d. | A Completed event is one that has taken place, and for which staff begin to finalize the charges. |
| e. | A Closed event has been invoiced and paid for, and is closed financially. If you want the event to be locked and archived for long-term, you set the lock level to Closed. |
| 6. | To prevent events from being tampered with, you can determine who has access to certain lock levels and who can change the lock levels of events. For example, you may not want just any user to be able to unlock locked events or re-open closed events. Therefore, you will want to limit who can set the lock level to Open and who can reopen closed events. |
| 7. | You may also want to create a hierarchy based on the ability to set lock levels. For example, a certain user right group may be able to set the event lock level to Finalized, but cannot set it forward to Completed or back to Open. The next user right group may be able to set the event lock level to Completed, but cannot set it back to Open or Finalized. You will probably also want to limit the number of users who can modify events once they are Finalized or Completed. |
| 8. | You could also create a hierarchy of rights based on the ability to alter events of certain lock levels. Perhaps the users who can set the lock level as Finalized cannot modify a finalized event. The users who can set the lock level to Completed can modify a finalized event, but once they set the event to Completed, they cannot make further modifications. In this way, you can ensure that events move through the chain of command without being in the care of several different groups of users at the same time. |
|