Thread

SA
Saif Ali Shaik3:38 AMOpen in Slack
I see the roles/persmissions are defined at the archestra dashboard level, over what an user is able and not able to do. Is there a way, I can get it more workflow levels, for example, APIs for disabling access for a user to A2A Gateway or MCP Gateway or LLM Gateway?

4 replies
DB
Dominik Broj (archestra team)5:11 AMOpen in Slack
Hey there! Atm all gateways fall under profile permissions. So if someone has profile: read, they can see all three. If they have profile: create , they can create any of them. There's no separate permission per gateway type which is something on our radar.
SA
Saif Ali Shaik7:03 AMOpen in Slack
Thanks for responding, Dom
Got it.
Can I drop you a DM and brainstorm an feasibility of an Idea with you? Although I am doing this as part of hackathon, might be good use of your time as well.
SA
Saif Ali Shaik6:54 AMOpen in Slack
@user - Can I modify these profile permissions through API? I don't see an appropriate API endpoint to do this? Is there a different way to do it?
DB
Dominik Broj (archestra team)7:09 AMOpen in Slack
You can update permissions of the role via PUT /api/roles/<roleId>, for example:
  Authorization: <your-api-key>
  Content-Type: application/json

  {
    "permission": {
      "profile": ["create", "read"],
      "tool": ["read"]
    }
  }```
Here's our API reference <https://archestra.ai/docs/platform-api-reference>

and docs around access control: <https://archestra.ai/docs/platform-access-control>
1