Some users have access given to them to specific pages, e.g. team pages, 1-to-1s, and so on. When we offboard someone, it's a common issue that these pages aren't properly transferred to the offboarder's replacement (where valid, of course), leaving the IT team responsible to go through 20+ pages in the IT space to try and find where the user has had access that the new person may need.
We were hoping to speed this process up with API, such as perhaps this command:
All we need is to find what restricted pages a specific user has access to. However, I am struggling to get it working for various reasons, both using curl and Python. I admit my relative coding inexperience may be showing here.
Has anyone engineered something like this, a (semi-)automated way of finding what locked-down pages someone has access to?
Hi @Lloyd Dorfmann and welcome to the Community.
Don't know about API but, on the space level, you can go to Space Settings > Manage Content > Restricted and you'll see the Permitted User/Group column in the table with details of the access type and page creator.
I know of that page, but it's exactly what we are hoping to avoid using - one of our Spaces has 20+ pages listing all the restricted content, and of course we have multiple Spaces. Going through them for each offboarder is a fairly tedious task.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.