Tech Support: Extracting PWA Security Group Usernames In Bulk
Background
It’s so helpful to have an Excel list of the username data contained in multiple PWA Security Groups. So, we thought we’d make a blog post with the solution! You can easily achieve this if you only have a handful of PWA Security Group Usernames. But, what if you have more than a few users? You may have noticed there is no nifty “Export to Excel” button in the ribbon to save you this time.
You’ll find the secret to extracting users from PWA Security Groups in the HTML source code. There are two ways we can go about locating the User list in HTML source code, but both require you to access your PWA Security Group. We’ll outline both ways below.
Prep Work
Firstly, you will need to access your PWA Security Group, and navigate to Manage Groups.
- Go into your PWA environment by right-clicking on the cog wheel located at the top right-hand corner.
- Select “PWA settings”, then Under Security section, click on “Manage Groups”
- On the Group Name in the “Users” section, select the PWA Security Group you would like to extract Username data from.
- While it might vary for your set up, we accessed our HTML under “Portfolio Managers”, where you’ll find this data located in a container labelled “Selected Users”.
Time Saver Approach to Extract PWA Security Group Usernames
- Once you’re inside your desired PWA Security Group, right click on the web page to for the pop-up window to pop up.
- Select and click on “View page source”.
- This will open a new browser window with all the HTML source code, which can be edited.
- Use the Find command (Control + F or Command + F) and type into the search bar:
IIR: Introduce, Integrate, Replace
Step 01
Introduce
You cannot run a portfolio on Excel and PowerPoint alone.
Project portfolio management is the discipline of seeing every project in one place, prioritising the work that matters, allocating people against demand, and governing delivery with real numbers. It is not optional at any serious scale. The moment you have more projects than one person can hold in their head, you need a single, current view of status, schedule, cost, resource and risk.
Excel and PowerPoint feel free because there is no licence conversation. The real cost is elsewhere. It is the hours spent maintaining workbooks, the version confusion, and the numbers that go stale the moment they are pasted.
A spreadsheet cannot tell you, on demand, which projects are at risk, where your people are over-committed next quarter, or how much of the portfolio budget is actually spent.
Introducing a proper PPM platform is the first step. Not to add another tool for its own sake, but to give the portfolio one place where the data lives together and stays live.
Step 02
Integrate
The instinct after buying a PPM platform is to make everyone move into it. That is the fastest way to fail. Project managers already have tools they trust, and finance already has systems of record. Force a migration on day one and you get resistance, shadow spreadsheets, and a dataset nobody believes.
Integrate first. Meet the data where it already is. Two directions matter.
Direction 01
Enterprise systems
Connect to the finance or ERP layer so actuals, commitments and budgets flow in automatically. Reporting stops being a monthly reconciliation and becomes a live view. Nobody rekeys a spend figure again.
Direction 02
The tools PMs already use
The direction most platforms neglect, and arguably the more important. The portfolio should read from the PM's own tools, not force people to abandon them.
The reason this matters is simple. That data is already there, and it is kept current by the person closest to it. When the portfolio reads directly from these sources, the status report updates itself. No chasing, no copy and paste, no reporting lag. The PM keeps working the way they always have, and the board gets a live picture as a side effect.
Step 03
Replace
Integration buys you two things: trust, and live data. Once both are in place, you look at what can go.
Every organisation carries tools and spreadsheets that either do not do the job well or carry a heavy maintenance overhead. The classic example is the resource spreadsheet. It is a workbook someone maintains by hand to track who is on what. It is always slightly out of date, owned by one person, and impossible to reconcile against real demand.
Replace it with the equivalent function in your PPM.
A proper demand management capability does what the spreadsheet was reaching for, with none of the overhead. It models demand against capacity across the whole portfolio, updates as projects shift, and needs no manual upkeep.
Replace deliberately, one function at a time, and only after the platform has earned it. The test is simple: if a spreadsheet is high overhead or low quality, and the platform does the same job natively, retire the spreadsheet.
The payoff
You stop producing reports and start reading them
Follow IIR and the nature of reporting changes. The status view is current because it is fed by the tools people already use and the systems that already hold the money. The overhead that used to consume the last week of every month disappears, because there is nothing to assemble.
That is the whole point of real-time reporting. Not a prettier deck, but a portfolio you can look at any day of the month and trust, at a fraction of the effort it takes today.
Built on Microsoft 365. Native ground for IIR.
pmo365 integrates with the tools your teams already run in, so the path from Introduce to Integrate to Replace is a natural progression rather than a rip and replace.