Hello. Have there been changes to the

Set permissions for the workspace

API call? Doesn't seem to work for me. The

PUT

call returns a 404 Not Found. traceid: ddcd929cddc90ee7bd524398d73bd609

Hi Filip, I’ve checked on my end and the Endpoint should work as normal. I would recommend double checking the workspace ID and ensuring that the endpoint is correct. Are you able to perform a GET to the same URI?

@Francisco Antunes I am able to get it other workspaces like

child_1_43

but not the one in pic

child_1_126

. I even deleted the workspace and recreated it and it still throws this error

How about the GET for the Layout of the workspace?

{{baseUrl}}/api/v1/layout/workspaces/:workspaceId

works but everything is empty

Thanks! I ran some tests on my end, and if the permissions endpoint is missing for the workspace, you can POST it to endpoint

{{baseUrl}}/api/v1/actions/workspaces/:workspaceId/managePermissions

, which is explained in this apiary entry.

@Francisco Antunes I get the api call, but I don't know what to send with the POST you mentioned. Here is what I want to run with my PUT:

{
  "hierarchyPermissions": [],
  "permissions": [
    {
      "assignee": {
        "id": "126",
        "type": "userGroup"
      },
      "name": "ANALYZE"
    },
    {
      "assignee": {
        "id": "126",
        "type": "userGroup"
      },
      "name": "EXPORT"
    },
    {
      "assignee": {
        "id": "126_share",
        "type": "userGroup"
      },
      "name": "VIEW"
    },
    {
      "assignee": {
        "id": "126_share",
        "type": "userGroup"
      },
      "name": "EXPORT"
    }
  ]
}

That’s pretty strange; Mind if I DM you for some extra details?

Sure

We found out that the issue was related to a lack of permissions. Filip fixed it by deleting the user that was causing the error 🙂