Skip to main content
Employee
April 12, 2024
4. Future Consideration

Add ability to allow Fresh Service Forms to be ingested even if group_visibility': 2

  • April 12, 2024
  • 3 replies
  • 57 views

Our docs say articles have to have the field group visibility set to 1: 'group_visibility': 1

I understand 1 denotes visibility to all requesters and 2 for restricted visibility. However, some organizations have set this up to stop users from different parts of the organization accessing the forms in the portal. Moreover, even though forms ingested here would need to have similar rules setup on the Moveworks side, it would be a better option than to drop the forms all together in the event that an org needed restricted visibility on their end and cannot change this field to 1.

3 replies

kyril.remillard
Community Manager
April 12, 2024

Thank you for submitting your Product Idea. We understand this is not currently supported and we appreciate your feedback. Please keep up to date with our latest release notes here.

We encourage other community members to thumbs up and comment on this idea. These signals help us determine what kind of features are popular amongst our users as we continue to build and improve our product.

kyril.remillard
Community Manager
April 12, 2024
1. New4. Future Consideration
New Participant
October 7, 2024

When a catalog item’s group_visibility is set to 2, the catalog item payload also includes these fields:

{
"service_item": {
// ...
"agent_workspace_visibilities_workspace_id": [
],
"group_visibilities_item_id": [
19001199901
],
"agent_group_visibilities": {
"group_id": []
},
"agent_workspace_visibilities": {
"workspace_ids": []
},
}
}

Freshservice has an API endpoint for listing the members of agent groups and requester groups:

If Moveworks ingests these groups and memberships, then it will know who should be able to see and fill each form.

If all forms are visible and fillable by anyone, that is a serious backdoor for Slack/Teams users to be able to fill out forms they shouldn’t have access to, e.g. “Terminate employee”.

Hopefully this helps the Moveworks development team.

Thanks