Locking of Events

Locking an event prevents it from being run or re-run. A locked event remains in a view-only state, providing an extra layer of security after signing or review.

Manual Locking & Unlocking

• Manual Locking (View Event Permission Required):

1. Navigate to your project's pipeline view
2. Click over the unlocked event you want to lock. A modal with information will pop up
3. Click on the Lock Icon located at the bottom left of the modal
4. Write a comment regarding the reason for locking the event
5. Click on the Lock button to lock the event

• Manual Unlocking (Edit Event Permission Required) :

1. Navigate to your project's pipeline view
2. Click over the locked event you want to unlock. A modal with information will pop up
3. Click on the Unlock Icon located at the bottom left of the modal
4. Write a comment regarding the reason for unlocking the event
5. Click on the Unlock button to lock the event

Automated Locking (Auto-Lock)

You can also configure an event to lock automatically upon signing.

To configure an event to auto-lock, follow these steps:

1. Navigate to you Pipeline
2. Click on the Edit pipeline button to enter Pipeline Editing
   
3. Locate the event you want to add auto-lock to and click on the Edit button
4. Scroll to the bottom of the modal that pops up. You will see an Auto lock option.
5. Click on On to activate autolock for this event
6. Click on Submit 
7. Approve a new version of the pipeline. Once approved these changes will take effect.

Special Considerations for QC Events

QC and standard events have a close relationship. Here are some things to have into mind when using autolock in conjunction with QC and Standard events.

• • Rejected QC events will not autolock
  • If a QC event is set to auto-lock and it's rejected, any standard events tied that also have autolock will be automatically unlocked.
  • If the QC event is set to auto-lock and it's rejected, any previously locked standard that do not have autolock enabled will remain locked.