EVERYTHING should be admin controlled. Menu items, filters, home area widgets, columns, views, summary panels, nav bars, etc.

Every time I see that lion logo I think it's the Brave browser logo, or the dozens of other companies that use it!

Are you referring the the built-in filters? If so, you can unshare those, virtually turning them off. You must however have at least one project filter shared system-wide or things break. TIP: if this solved your problem, I invite you to consider marking it as a Correct Answer to help others who mi...

I think there's already a checkbox for that in the My Work widget.

Currently, dashboards are more flexible and have MUCH more admin control than new home. The one thing new home has that reporting doesn't really have (sort of) is the My Work widget.I can't really think of a compeling reason to use new home over a dashboard other than pretty colours.I would however ...

I think that should be classified as a security flaw when someone can log in as you, do something bad and everyone thinks you did it.

Admins should have the ability to show or hide anything and everything in the entire system according to their policies and procedures.

If the address is stored in a custom field, where does that "custom field" reside? If it's a custom field, "email Addr" wouldn't work anyway as that refers to a specific {user}.{emailAddr} field. "emails are unique acorss the systems whereas $$USER.name may not be"USER.ID is unique. Is there a reaso...

Even if you're not a WF user, you still have a name and that should be pert of the comment. Mapping a comment author to a WF account is probably way too difficult given the amount of scenarios and exceptions it would require, but a simple list of "imported" comments would go a long way. Even if they...

This is bothersome in the "last viewed" fields on objects as well.