Skip to content
IFS Wire

Community · Question

Workflow permission grants in IFS Cloud 25R1 still return FndProjectionGrant.SRV_NOT_ACCESS: causes and workarounds

Asked by IFS Wire DeskEditorial · 3 Nov 2026 · 0 views

Type:
Technical
Product:
IFS Cloud
Version:
25R1

Sourced from IFS Community · original thread · dinelka, pdollk

0

IFS Cloud 25R1 introduced workflow-level permissions, intended to let users run a workflow that touches projections they cannot access directly. A test workflow reads from the SalesContractHandling projection, which the basic end user has no access to. The workflow was granted in a permission set with Internal access and then with Full access, but running it still fails with FndProjectionGrant.SRV_NOT_ACCESS. Other users report the same error on a cascaded workflow, as FndProjectionGrant.SRV_NOT_ACCESS: You cannot access the service JtTaskEntity, and on 25.2.3 with workflow grants placed on a functional-role permission set. What has to be in place for workflow-level grants to work?

Technical details IFS Cloud 25R1 and 25.2.3. Error: FndProjectionGrant.SRV_NOT_ACCESS; FndProjectionGrant.SRV_NOT_ACCESS: You cannot access the service JtTaskEntity. Objects: SalesContractHandling projection, JtTaskEntity entity service API, API Explorer, permission sets (Internal / External / Full access), Production Mode vs Troubleshoot Mode. Fix versions: 24.1.21, 24.2.15, 25.1.9, 25.2.3, 26.2E.0.

Any attachments are visible to signed-in members.

1 answer

0

✓ Accepted answer

Several separate causes were identified by IFS employees in the thread. Check each:

  1. Access level (confirmed): running a workflow from the Workflow command needs External or Full access. Internal access is not enough.
  2. Mode (stated by IFS): workflow-level permission sets only take effect in Production Mode. In Troubleshoot Mode the SRV_NOT_ACCESS error is expected.
  3. Grants through user groups (confirmed): at the time, a permission set granted via a user group did not pass on the workflow grant. Granting the permission set directly to the user worked. IFS said a fix for group-based grants would come in a following release.
  4. JtTaskEntity error (confirmed workaround): the failure happens before the workflow runs, in a step that resolves data types and opens an authorized connection through the JtTaskEntity entity service API. Workaround: activate the JtTaskEntity API from the API Explorer and grant it to the user. IFS listed the fix for 24.1.21 (24R1 SU21), 24.2.15 (24R2 SU15), 25.1.9 (25R1 SU9), 25.2.3 (25R2 SU3) and 26.2E.0 (26R2 EA).
  5. Functional-role permission sets (confirmed, likely limitation): when the workflow is granted on a functional-role permission set that is included in an end-user role, only the projection grant is inherited, not the workflow grant. Grant the workflow directly on the end-user permission set.

Prerequisites and limitations Thread is about a year old and not marked solved; fixes depend on service update level (see fix versions). The user-group fix was only promised for a later release, with no version stated. The functional-role inheritance behaviour was described as a likely limitation, not a bug with a fix. A later, unanswered follow-up about StatesHandling triggered from an assistant is not covered.

Sourced from IFS Community · original thread · dinelka, pdollk

Answered by IFS Wire DeskEditorial · 3 Nov 2026