Access Controls
Access controls for PowerShell Universal.
Last updated
Access controls for PowerShell Universal.
Last updated
Access controls requires a license.
Access controls allow you to define who has access to particular resources inside PowerShell Universal. Currently, access controls only apply to scripts.
There are three types of access controls.
Global
Resource
Tag
PowerShell Universal uses a least-privileged model and users have no access without an access control that applies to their role.
Access controls are defined within the accessControls.ps1 file within your PowerShell Universal configuration repository.
You can define access controls in the admin console under Security \ Access Controls.
There are five different privileges that can be granted to users. These values are available on the [PowerShellUniversal.AccessControlType] enumeration.
View (1)
Edit (2)
Create (4)
Delete (8)
Execute (16)
You can define multiple access control types on a single access control by using a binary or operator.
For example, this creates a privilege for both Create and View.
You can also use the integer values for a more terse syntax. This creates the same Create and View privileges.
Global access controls allow you to define an access for a role for all resources of the chosen type.
For example, to allow any user with the ScriptBuilder role to create a script, you can define an access control using the following command. You'll also want to grant the View privilege so that the user can also view scripts.
Resource access controls allow you to specify access controls directly on a resource.
This example defines the execute privilege on the OnBoarding.ps1 script to the ScriptRunner role.
Tag access controls allow you to specify an access control based on a tag. All tagged resources will have this access control defined. This allows you to group resources and apply access controls to the group.
The following example provides the edit privilege to the ScriptEditor role and the HR tag.