Activity Feed

My Posts

Hi Chris, The following: PUT https://myinstance.instructure.com/api/v1/users/:user_id?user[email]=newemail@institution.edu ...will create a
  • 4 Likes
  • 0 Replies
I have been in contact with Instructure about our difficulties modifying a user's email address.  Our issue was the misuse of the skip_confirmation pa
  • 4 Likes
  • 0 Replies
Thanks for the response Marlee, Did you consider updating the user's email address using SIS imports, as you did when creating new users?
  • 3 Likes
  • 2 Replies
Thanks Scott, It appears that email changes must be made via the communication_channels api.  Do you have a sample call for modifying a user's email a
  • 3 Likes
  • 4 Replies
I am seeing similar behavior to what Marlee is reporting.  Email changes set by csv file are immediately active, whereas changes made by the API resul
  • 2 Likes
  • 6 Replies
Hooray!  The solution was found in our Canvas root account permissions.  Setting this option: Users can delete their institution-assigned email addres
  • 3 Likes
  • 0 Replies
Thank you for replying Daniel, I can make this API call, and it appears to be syntactically correct, but the outcome is still the same: the user canno
  • 0 Likes
  • 1 Replies
I have found a way to update the default email address.  List the user's communication_channels, then update the default using this call: PUT http
  • 0 Likes
  • 3 Replies
Hi all. We at the University of Michigan are developing an integration between our Identity system and Canvas.  An important aspect to this is the
  • 2 Likes
  • 7 Replies