On the “add user to a client” workflow: once a client is established, we would want to disable your native user-invite functionality within our environment. Instead, we need to manage user provisioning directly within our application, as access control in our system is not purely user-based but project-scoped (i.e., a simplified RBAC model tied to project-level permissions).
As a result, user creation and team management need to sit within our own workflow, where access can be assigned and governed appropriately. Conceptually, we are looking to replicate the core elements of your team management experience—user onboarding, invitations, and role assignment—while embedding our own access control layer and permissioning logic within our application.
Let me know if that aligns with how your system can be extended or integrated.