# Add-VaultRestriction

Adds a restriction to block the current operation.

## Syntax

```powershell
Add-VaultRestriction -EntityName <String> -Message<String> [<CommonParameters>]
```

## Parameters

| Type   | Name       | Description                                      | Optional |
|--------|------------|--------------------------------------------------|----------|
| String | EntityName | The title or affected object of the restriction. | no       |
| String | Message    | The message of the restriction.                  | no       |

## Return type

**empty**

## Remarks

- The Cmdlet makes it possible to block the executing Vault webservice call and upcoming *Pre*- or *Post* events.
- It is possible to add multiple restrictions with the same **EntityName**.
- If a Restriction event has multiple subscribers then the event actions of all subscribers are executed even though the first subscriber already sets a restriction.
- For Vault events which are raised only for a single entity (e.g [CheckoutFile](</code_reference/objects/event_mappings/file_events/checkoutfile>)...) , the EntityName is not displayed in the restriction Dialog by the Vault Client.

:::{note}
The Cmdlet is **only usable** in Vault **Restriction** events (e.g [AddFile_Restrictions](</code_reference/objects/event_mappings/file_events/addfile>), [UpdateFileStates_Restrictions](</code_reference/objects/event_mappings/file_events/updatefilestates>)...).
:::

## Examples

**Adds a restriction for files which state is trying to be changed to released**

```powershell
Register-VaultEvent -EventName UpdateFileStates_Restrictions -Action {
	param($files)
	foreach($file in $files)
	{
	        if($file._NewState -eq "Released") {
	                Add-VaultRestriction -EntityName $file.Name -Message "File state can't be set to released!"
	        }
	}
}
```