New GraphQL Mutation to Revoke Request Visibility Granted by SLA

New GraphQL Mutation to Revoke Request Visibility Granted by SLA

We have introduced a new GraphQL mutation that allows account administrators to revoke request visibility when a Service Level Agreement (SLA) unintentionally grants access to another account. This can occur, for example, when a request is moved and becomes visible to additional customer or provider accounts through an SLA.

‍

With this mutation, administrators can remove visibility for affected request accounts to ensure requests are only accessible to the intended parties. Visibility changes are subject to the following conditions:

• Visibility cannot be changed for the request's originating account.
• An administrator may remove visibility from a customer account if they have the Account Administrator role in the related SLA account, and the customer and SLA accounts are different.
• An administrator may remove visibility from a provider (SLA) account if they have the Account Administrator role in the related customer account, and the customer and SLA accounts are different.

If a service change later results in a new SLA being created for an account whose visibility was previously removed, the request will automatically become visible again.

Full details are coming soon in the Xurrent developer documentation: https://developer.xurrent.com/graphql/mutation/requestupdatevisibility/.