jason.chaw
07/20/2026, 5:02 AMAsk Inkeep
07/20/2026, 5:02 AMAsk Inkeep
07/20/2026, 5:03 AMrole_assignment is sent (1) .
The expected webhook payload for role assignment is:
{
user_id: str,
tenant_id: str,
role: str,
permission_level: str,
type: ElementsWebhookType = "role_assignment"
}
To troubleshoot why webhooks aren't being received in your new project, verify:
1. The webhook URL is correctly configured in your element settings
2. Your endpoint is responding with a 200 HTTP status code to acknowledge receipt
3. Your endpoint uses HTTPS for secure data transmission
4. If you're using a secret for validation, ensure it matches between your configuration and endpoint
To help investigate this issue further, could you provide:
1. Which Workspace / Project / Env you are using
2. What calls are you performing (as SDK code or CURL)
3. Which PDP version you are running
4. Relevant logs from your PDP
Additionally, check if your webhook endpoint is properly set up to receive POST requests and parse the JSON payload .Ask Inkeep
07/20/2026, 5:03 AMjason.chaw
07/20/2026, 5:05 AMAsk Inkeep
07/20/2026, 5:28 AMAsk Inkeep
07/20/2026, 5:28 AM{
user_id: str,
tenant_id: str,
role: str,
permission_level: str,
type: ElementsWebhookType = "role_assignment"
}
To help our engineers investigate this issue in your Production environment, please provide:
1. What calls are you performing (as SDK code or CURL) when changing roles
2. Which PDP version you are running
3. Relevant logs from your PDP showing the role assignment operations
4. Any error logs from your webhook endpoint (if available)
Also, can you confirm whether:
• Webhooks for other events (like user creation or invites) are working?
• This is specifically affecting only role assignment webhooks?
• You're seeing any errors in the Permit dashboard or browser console when making role changes?
This information will help pinpoint whether the issue is with the webhook configuration, the element setup, or something else in your environment.Ask Inkeep
07/20/2026, 5:29 AMjason.chaw
07/20/2026, 5:40 AMAsk Inkeep
07/20/2026, 5:41 AMAsk Inkeep
07/20/2026, 5:41 AMcreate_user or invite_user) firing correctly in this environment?
• Can you check your webhook endpoint logs to see if any requests are being received at all?
• Does the webhook work if you test it with other actions through the same Element?
This will help isolate whether the issue is specific to role_assignment webhooks or a broader webhook delivery problem in your Production environment.Ask Inkeep
07/20/2026, 5:41 AMjason.chaw
07/20/2026, 5:44 AMAsk Inkeep
07/20/2026, 5:44 AMAsk Inkeep
07/20/2026, 5:44 AMrole_assignment webhook isn't firing in your Production environment (1) .
Since you've confirmed the webhook configuration looks correct and role changes are successful, this points to a potential issue with webhook delivery specific to your environment setup.
*To help our engineers investigate this issue, please provide:*
1. Which Workspace / Project / Env you are using ✓ (You've provided: Changi Full Stack Solutions / Wildlife Management System / Production)
2. What calls are you performing - specifically the API calls visible in your browser's Network tab when you change a role through the User Management Element
3. Which PDP version you are running
4. Relevant logs from your PDP showing the role assignment operations
*Additional information that would help:*
• Are other webhook types (create_user, invite_user) firing correctly in this environment?
• Any error logs from your webhook endpoint
• The webhook URL and configuration from your Element settings (you can redact sensitive parts)
The expected webhook payload for role assignments should be :
{
user_id: str,
tenant_id: str,
role: str,
permission_level: str,
type: ElementsWebhookType = "role_assignment"
}
If you can share the screenshots via a different method or describe what they show, that would help narrow down the issue.Ask Inkeep
07/20/2026, 5:44 AMjason.chaw
07/20/2026, 5:44 AMjason.chaw
07/20/2026, 5:45 AMjason.chaw
07/20/2026, 5:45 AMAsk Inkeep
07/20/2026, 5:45 AMAsk Inkeep
07/20/2026, 5:45 AMAsk Inkeep
07/20/2026, 5:45 AM