Blocking a Widgets use

do you allow users to create blank projects? (projects without a template)

Hi, Tracy. I battle the same issue. There is no function that is going to nip the issue in the bud completely, so let me share what I’ve done for your consideration (TL;DR make it annoying for users to NOT file a project into a portfolio):

• Write it down. Our system governance says that all projects need to be in a portfolio. Whenever I train people or if anyone asks, I justify this decision as, “Your system administration requires all projects to be in a portfolio for security and permissions reasons. We configure portfolios to secure the work within to be visible only to those who are allowed. Similarly, we configure portfolios to grant blanket permissions to key groups so you don’t have to futz with the share permissions project-to-project.” (Historically, we had an API that relied on portfolios, so I had an actual technical reason for people to file things. Specifically, if projects weren’t in portfolios, it wouldn’t appear in a key third-party dashboard.)
• We turned off the ability to create a project without a template (see ​@skyehansen’s comment). Most of our templates define a portfolio. The least you can do is set the template’s default portfolio to a generic portfolio. Consider setting permissions on that portfolio in a way that makes it painful for people to do work if it’s in there. For example, if you have any reports that driving people’s work, you could filter out that portfolio.
• We have a report that looks for projects without portfolios. I monitor this report monthly to nag people. You could monitor more frequently until people get more into the habit. There is also the ability to send reports to email: “If you appear in this report, please file your projects into a portfolio.”

In my instance, we have at least one custom form that is on every single project template. On that form, there are two fields called ‘Company Name’ and ‘Portfolio Name’. They are both ‘Native field reference’ fields that link back to those objects. Both of those new fields are set to be required.

If the user fills out the stock Company or Portfolio fields in the overview section, the data simply copies itself to those fields and they never notice them. But if they try to create the project without filling in the native overview fields - then the required attribute of the new fields takes over and forces those to be filled out first.

That’s how we handled the need to ensure both of those fields were completed properly in the absence of being able to make stock fields required. I know that’s not quite what you were asking, but it’s an option if you have common project-level forms.