Stacy S added a comment - 04/May/2023 11:35 PM I added this same comment in JWMCLOUD-107 , as it is related to allowing users to submit a form without having specific project permissions, which is at least somewhat related to this issue above: Adding my comment here since it's at least somewhat related to this issue.  In short, JWMCLOUD-107 would partially solve a problem we're facing, but it doesn't entirely solve for it.  Currently, there is not a business team-managed project permission setting to restrict "View" access to only the user's submitted issues (similar to how other permissions options say "X their own X" (i.e. delete their own comments)).  Even granting the lowest level permission available that still enables a user to create tickets ("Create project issues") still grants the user the ability to view any and all issues submitted for a project.  Ideally, the "Create project issues" would solely relate to issue creation (via forms or "Create"), and two separate view permissions would be added, "View their own issues" and "View all project issues"). Decoupling forms submission from project permissions helps, as we'd still be able to collect submissions without requiring project access be granted,  but it's not clear from what you have above if/what visibility a user who submits a form would then have to be able to see the results and progress on their submitted form issues .  Separating create issues and view issues (and enabling limiting to just viewing their own) would be a powerful way to broaden project interactions without granting excessive access to those who don't need it.  For additional context, we're trying to manage security issue submissions, so limiting view access is important.  If there is a separate issue already started for Workforce granular permissions that you can point me to, I'd appreciate it, otherwise I'll look into submitting a new feature request.  Thank you for listening! I did see that Software team-managed projects also do not seem to support "Reporter" as a selectable group with which to grant access, but this would be INCREDIBLY powerful in enabling teams to be able to use team-managed projects.  The concept already exists in some form in that some permissions include the ability to restrict to just their own items (e.g. "delete their own attachments") - if you could just enable that granularity to issues and/or issue types, it would go a long way.  I assume you're soon going to have to solve for this as part of Service Management, so anything you can do to empower that level of granularity on Work Management team-managed projects would be incredible.