How to separate request by staff vs non-staff?

[Mike Prill]

We are a non profit with many volunteers and a smaller number of staff. We have a number of request types we only want staff members to have access to, so volunteers shouldn't see them.

So far I've elected to have two portals (projects) within our site so that I can show the vols request types for them, and the staff members specific request types for staff.  

The only reason I have two portals was because I didn't see an easy way to restrict specific requests types so only staff see them. Is there an easy way to do this?

This is now causing problems because I need for customers to be able to just sign up without knowing who they are ahead of time, but I can't seem to enable that for a customer only portal while also locking down to the staff portal to specific users...

[Mikael Sandberg]

As you have discovered there is no way of restricting specific request types from being accessed from the portal. So your approach using two different projects would be the way to go. You can control who have access to the project by updating the customer permissions. For the one you want to restrict, set the channel access to restricted and you can then add your staff as service desk customers under people if they have Atlassian accounts or under Customers if they are JSM accounts only. For the other project you can set it as open and then allow customer to sign up.

[Uday Kiran Bhaviri]

You can set security level to the issues and configure the security levels in issue security scheme.

Security levels will enable to define who can see the issues.

https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Hope this will be helpful.