Set a role's subscriber-portal permissions

PUT /api/v1/roles/{id}/portal-permissions prm_roles_manage

The separate set that governs what a SUBSCRIBER may do in the self-service portal, not what a manager may do in the admin API. Different catalogue, different meaning.

These are not prm_* codes and they do not affect the admin API at all. Confusing the two sets is the usual cause of "I gave the role the permission and nothing changed".

At a glance

Authentication: Staff token or session
Requires permission: prm_roles_manage Manage roles & permissions
Rate limit: t_mutate

Parameters

Parameter	Description
`id`required path · integer	Role id.

Request

curl -X PUT "$BASE/api/v1/roles/{id}/portal-permissions" \
  -H "Authorization: Bearer $XR_TOKEN"

BASE is your tenant host: the same address you sign in on.

Try it on your own network.

50 subscribers for 7 days. You pay nothing.

Try it free Talk to us