Permissions
Delete a role
Changed onDelete a role — only ever a company-authored or a global one.
The full matrix, and why nothing here is a confirmable 409, is in permissions_db.delete_platform_role_guarded. In short: a template deleted from here has no repair path through the product, a system copy comes back under a new id at the next invite, and deleting a HELD role is a company lockout rather than an escalation — get_effective_modules INNER JOINs Z_Roles, so the survivors resolve to the empty set.
delete/api/roles/{role_id}
Request
- Base URLhttps://api.multigest.pt (the document declares no server; this is the origin it was published from)
- URLhttps://api.multigest.pt/api/roles/{role_id}
- AuthAPI key in header x-api-token and API key in header x-origin-verify
Path parameters
role_idinteger required
Query parameters
delete_templateboolean
Confirma a eliminação de um MODELO de sistema com todas as cópias que as empresas têm dele. Sem isto, um modelo é recusado com 403.
Headers
x-api-tokenstring nullable
Response
Successful Response
unknown required
Changes
- info
added the new optional
queryrequest parameterdelete_template
- info