[LA-35296] Doc managerEmail on /api/v1/users#40
Merged
Conversation
1e0a37c to
007cbeb
Compare
pajw
approved these changes
Apr 30, 2026
007cbeb to
c3870d6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira
LA-35296
What
Documents the new
managerEmailparam on the public Grape v1 Users API, added in learnamp/learnamp#22667.managerEmail(String). Mutually exclusive withmanagerId.managerEmail must match an existing user email within your company(unknown / cross-tenant email).managerId, managerEmail are mutually exclusive(both sent together).Why
Third-party provisioning systems often know an employee by email but not by LA
user.id. The Teams API already acceptsmanagerEmailon team create — this brings parity to Users so callers don't need to look up the LA id first.