How do you give granular permissions to scripts in v5?

PowerShell Universal
1 
Product: PowerShell Universal
Version: 5.0.15

Question

How do you give granular permissions to scripts in v5?

Problem description

Before purchasing PSU, i did a POC in v4.
There i tested if it was possible to manage who has access to what.

POWERSHELL UNIVERSAL v4

I came up with a setup where i could chose per script, who could see it and who could not.
I took some screenshots:

image
image2277×923 281 KB

I used a combination of these 3 items to manage access.

  • tags
  • roles
  • access controls

The users looked like this:

image
image1658×526 18.2 KB

This is what user r would see after login,:

image
image1875×442 21.5 KB

Perfect, only access to the script I want.
The way I had it recorded in my notes was as follows:

  • The role O365_R gave access to just automation/scripts
  • The Tag only allows the user to see only those that have the tag O365_R
  • In the Page ‘Access Controls’ is where you link these 2

POWERSHELL UNIVERSAL v5

In v5, Access Control was removed. This is clearly stated in the documentation.
Therefore I have been looking around for alternative approaches.

Another difference is that in v5, there is a portal. I don’t know that what i did in v4, is even possible (or still is the intended way to do it).

I tried to set up something similar:

image
image1805×1230 288 KB

Now i believe Access Control is now Permissions.
I tried to create a permission but in Identity you can only select a single user?

My next idea was to give my user, 2 roles.

image
image767×502 13.9 KB

However, i am confronted with:

image
image1342×274 23.7 KB

Closing question
How is it supposed to work? Is my intended purpose wrong?
Did PSU lose functionality compared to its previous version?

I hope someone can clear things up. I spent quite some time figuring this out but as you can see, I haven’t found the answer.

Thank you and have a nice weekend.

2

Anyone that has any answer to this? This is a frustrating issue to say the least :sweat_smile:.

3

So looking further into this: what I’ve gathered is:

  • Roles give permissions to the portal
  • Permissions give permissions to the admin console

It looks like it is a completely different approach.

What is not possible is to attach permissions to roles.
This is also mentioned in the documentation. The visibility is a lot less clear.

They way i currently understand it, you assign a role to a script or app. You can then assign the permissions to give each individual access to parts of the admin console.