Hide "Approver" and "Shared with" sections from the customer portal.

[Arooba Al Siyabi]

I want to hide the "Change manager approval" and "Shared with" sections from the customer portal:

 I am using the service management (could), Please If you have any segregation how to do it?  

[Marc - Devoteam]

Hi @Arooba Al Siyabi 

On the approval, if there is an approval required on a status, the options to approve or decline are visible on the portal, as the required approver or approvers can do this on the portal or via the email they receive.

This can't be removed.

The share with option can be removed, but this is related to the customer permissions on the project.

See share-with-button-differences-and-behaviors-on-jsm-portal 

[Jovin]

@Arooba Al Siyabi Great question! With regards to the approvers, it's not the intended use of the Approval step BUT you could:

1. Create a separate user picker field to store the actual approvers in (e.g. "Request Approvers")
2. In the actual approver field only add "Automation for Jira"
3. Create 2 transitions from "Awaiting Approval" (or whatever status it is) to itself (a loop) - one transition called "Approve" and one called "Reject"
4. Limit these transitions through a condition that requires the user to be in the new custom field
5. Add an automation that looks for that transition, and handle it accordingly based on the transition performed by the approver

You'll also need to have an automation rule that emails the people in that new custom field

that this ticket needs their approval, and add them as request participants as well.

On the portal the customer will only see "Automation for Jira" in the approver section, yet you can still achieve approvals or rejections accordingly.

The other method is to use Groups (they won't show on the portal), but this requires all approvers to be using Atlassian Accounts instead of Portal Only Customer Accounts.

---

For the "Share With" section, you can see this article that shows how to manage sharing: https://support.atlassian.com/jira-service-management-cloud/docs/change-project-customer-permissions/#Customer-sharing 

[Sara Beyer]

@Marc - Devoteam is it possible to have groups as approvers instead of individual users?

I am also looking for an answer to this same problem - I don't need customers to see what individuals in my organization approved changes, but if they could see that "Engineering" approved it, that's fine.

[Marc - Devoteam]

Hi @Sara Beyer 

Yes, use a group picker field as the source of your approval.

You will still see information on this, but the information shows that there is still an approval needed, but not baed on individuals