Hi @Tamara Jones‚, I would say it depends on what type of security structure you want. We have portfolios set up by internal departments and a departmental head is assigned as the portfolio manager so they have ultimate control over what projects/work goes on in their portfolio. The Portfolio owners confer amongst themselves when a project needs to be transferred between portfolios. We have custom forms from there assigned to the projects to classify our customers across the different portfolios. We also share resources across the portfolios, but the control of the projects is a little more siloed, so this works for us.
So if you have a fairly strict structure with multiple departments like that, portfolio by department might make sense. However, if it's one department handling the work for multiple organizations/clients, or if your workflow is a little less siloed in regards, the portfolio by organization makes sense.
You can also do a hybrid by setting up portfolio by departments and programs by organizations; you definitely have options and a lot of it depends on how your workflow is now and how you want the work to be reported at the portfolio level (ie, by department or by client).
Hope that helps. Let me know if you have any other questions, hope i didn't throw too much at you at once!