--- agentTools: projectIndex: https://docs.zushealth.com/llms.txt --- # New role: Builder Data Integration We've added a new managed role, **Builder Data Integration**, for App Clients that get access tokens on behalf of users in your organization, such as an EHR integration or a Zus app embedded in your own UI. These App Clients call the proxy-token endpoint (`POST /auth/users/proxy-token`). ### What's changing * Today, the Builder Admin role includes permission to call the proxy-token endpoint. On **Wednesday, October 14th**, we'll remove that permission from Builder Admin. * Builder Data Integration has every permission Builder Admin has today, including proxy-token. Nothing else your integrations can do will change. ### Why This change will strengthen Zus security by ensuring only App Clients can retrieve access tokens on behalf of other human users. ### Do I need to do anything? Most likely not. Before the change, Zus will move every App Client that currently calls proxy-token to Builder Data Integration. Your integrations should keep working without interruption. You only need to act if: * **You create a new integration App Client** after this change. Assign it Builder Data Integration instead of Builder Admin. * **A person, not an App Client, calls proxy-token directly.** After this change, users with Builder Admin can no longer call it. Contact us to talk through your use case. See [Roles and Permissions](https://docs.zushealth.com/docs/roles-and-permissions) for details. Questions? Reach out to your Zus contact or .