Community

wondering where in the "development process" this idea is. are we past "discovery"? ... View more

@korina_figueroa  It seems like it would be simpler to enable pronoun support, disable the ability for people to change it, and then send the pronoun information through a SIS import. This satisfies all of the conditions of your desired behavior. The minimal users.csv file has four fields required: user_id, login_id, pronouns, and status. You don't have to supply any other values, which will keep the existing values in Canvas. SIS imports can be automated through the API, but instead of making one call for each student that needs changed, you send one file with all of the changes. It's still through the API so it can be automated, it's just not through the Users API. What is happening with the API is that the same call is made whether it is an admin making the change or a user making a call. The wording on the selection is a bit misleading. It does prevent the user from changing their pronouns, so it is truthful, but it also prevents others from changing it through the Users API. It does not prevent others from changing it through a SIS import. Regularly users cannot do their own SIS imports, so the statement is still correct. Another approach would be to look at who is making the API call and if they have admin rights, let them go ahead and change the pronouns. That might involve some permissions as well and there is probably some reason not to do this that I'm not thinking of. Currently, the way that Canvas has for you to set pronouns that come from a SIS is to use a SIS import. ... View more