Girija shankar
12/02/2025, 9:46 AMAsk Inkeep
12/02/2025, 9:46 AMAsk Inkeep
12/02/2025, 9:46 AMbulkAssign(assignments: RoleAssignmentCreate[]) : Promise<BulkRoleAssignmentReport>;
bulkUnassign(unassignments: RoleAssignmentRemove[]) : Promise<BulkRoleUnAssignmentReport>;
(2)
*Java:*
BulkRoleAssignmentReport bulkAssign(List<RoleAssignmentCreate> assignments) throws IOException, PermitApiError, PermitContextError;
BulkRoleUnassignmentReport bulkUnassign(List<RoleAssignmentRemove> unassignments) throws IOException, PermitApiError, PermitContextError;
(3)
Alternative: SCIM Integration
For large-scale user provisioning, you might also consider using Permit's SCIM integration (4) , which allows seamless integration with identity providers like Entra ID, Okta, and others (1) . SCIM simplifies user management by automatically provisioning, updating, and de-provisioning users in Permit .
To help our engineers investigate your rate limiting issue further, could you please provide:
1. Which Workspace / Project / Env you are using
2. What calls you are performing (as SDK code or CURL)
3. Which PDP version you are running
4. Any relevant logs from your PDP
This information will help us understand your specific migration scenario and provide more targeted assistance.Ask Inkeep
12/02/2025, 9:46 AMAlon Boshi
12/02/2025, 9:49 AMGirija shankar
12/02/2025, 9:52 AMAlon Boshi
12/02/2025, 10:08 AMOr Weis
12/02/2025, 11:13 AMThe account data we are migrating is received from a third party through our API endpoint, and we synchronize each account individually by invoking the above-mentioned APIMy recommendation would be one of: 1. poll the data on your side and write it with the bulk API in chunks 2. handle a queue on your side flushing the queue at the pace of the rate-limit
Girija shankar
12/02/2025, 11:38 AMOr Weis
12/02/2025, 11:39 AMGirija shankar
12/02/2025, 11:49 AMOr Weis
12/02/2025, 11:50 AMOr Weis
12/02/2025, 11:51 AM