Force the use of a Portfolio | Community
Skip to main content
TravisGrogan1
TravisGrogan1
New Participant
April 14, 2023
Solved

Force the use of a Portfolio

  • April 14, 2023
  • 3 replies
  • 1048 views

Is there a way I can REQUIRE users to assign their projects to a Portfolio?

 

My only solution is to force them to use a Project Template and preassign the Portfolio there.

 

Any other solutions?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Kurt_Jones

Travis, this is the best practice standard and one of the many reasons for having users start projects via templates.  If you have Fusion you could use that to help update some of the information when a request is submitted.  There is a global setting where you can force users to create projects via templates and not allow any other options so you can guarantee this data is being populated correctly.

3 replies

Madalyn_Destafney
Madalyn_Destafney
New Participant
April 17, 2023

Team, correct me if I'm wrong but I think I heard the ability to put these native fields like Portfolio/Program in a custom form is coming? Would be awesome if true. 

If this helped you, please mark correct to help others : )
    RandyRoberts
    RandyRoberts
    New Participant
    April 17, 2023

    I've heard that as well. No timeline though.

    RandyRoberts
    RandyRoberts
    New Participant
    April 17, 2023

    The above suggestions are really good. I would also add, remove the "Projects" icon from the waffle menu via Layouts. Then the user has to go to the Portfolio level to create and view projects (the "create new project" button doesn't appear anywhere else). Any new projects will then be in the portfolio the user created the project from.

    Also, you can create a report for projects where the portfolio is blank to call out the offending projects.

    If you force portfolios via template, then you will need a template set for each portfolio. This could lead to a lot of duplicate templates as you could not use one template that could go in several different portfolios.

      Kurt_Jones
      Kurt_JonesAccepted solution
      New Participant
      April 15, 2023

      Travis, this is the best practice standard and one of the many reasons for having users start projects via templates.  If you have Fusion you could use that to help update some of the information when a request is submitted.  There is a global setting where you can force users to create projects via templates and not allow any other options so you can guarantee this data is being populated correctly.

      Lyndsy-Denk
      Lyndsy-Denk
      New Participant
      April 17, 2023

      I support @kurt_jones suggestion. I'm starting change management to shut down the ability to create projects from scratch. One thing that will help quiet the haters: A template with no tasks. I have a generic portfolio with a program called "Unfiled projects" set as the default, which will help with housekeeping.

        Terms & ConditionsAccessibility statement

        Loading footer...