Why assign issue permission is mandatory for Service Space Customer - Portal Access

vidyashree MS

when I see default permission schemes, I see that  Service Space Customer - Portal Access, which is a security type and not a project role, have the Assign issue permission. when we add the assignee field to the request type it says its hidden and its default JSM configuration. Firstly, why would a customer be given this permission and also if its given the field is always hidden by default. When I REMOVE them from that permission, JSM automatically adds them when told to fix error. So I want to know why that permission is given and also is there any dependences internally, and thats why its causing it? 

Marc -Devoteam-

Hi @vidyashree MS 

Please show some screenshots.

BTW Service Space Customer - Portal Access is a default ootb setting in a permission scheme of a JSM project.

It grants a customer access to the project.

The assignee field can't be provided on the portal, in a request type it need to be set with a default. This can only be to a user who has a JSM license.

If you want to remove this setting, JSM will tell you there is an error on the permission scheme, but this can be ignored.

Not all permission apply, as a customer has no access to the system, only to the portal.