We have a case where billing users need to have a user created for all of our locations.
We create a name specific user per location they have access to. This is quite cumbersome for our IT dept.
When I noticed the Open Dental API I was hoping to fix this problem.
Currently the only access through the api is GET/POST. I would love to see a PUT request so we can hide the user for all locations in a faster manner than we do currently.
A new method, Userods PUT, has been added. This method will allow you to update an existing userod. Fields that can be modified include EmployeeNum, ProviderNum, ClinicNum, and IsHidden. For more information, see https://www.opendental.com/site/apiuserods.html
This method is available as of beta version 22.4.20.
Hello there, I work with rdillman and we have another small addition that we would like to add to this PUT method. When hiding the users, we tend to like to change their group as well to a group that has no rights, however this is especially important for some of our groups that have the Setup permission and "admin" abilities. We are unable to mark those employees as hidden because you cannot mark an admin as hidden.
Can we add the ability to specify the UserGroupNum as well on the POST, like the PUT has available so that we can change the group as well as mark hidden at the same time?
Thank you for taking the time to look at this request!
rgibbons wrote: Thu Oct 10, 2024 10:12 am
Hello there, I work with rdillman and we have another small addition that we would like to add to this PUT method. When hiding the users, we tend to like to change their group as well to a group that has no rights, however this is especially important for some of our groups that have the Setup permission and "admin" abilities. We are unable to mark those employees as hidden because you cannot mark an admin as hidden.
Can we add the ability to specify the UserGroupNum as well on the POST, like the PUT has available so that we can change the group as well as mark hidden at the same time?
Thank you for taking the time to look at this request!
Good afternoon rgibbons,
It looks like you can currently specify the UserGroupNum in the POST, but cannot in the PUT. I think what you're asking for is an enhancement to the PUT, not the POST?
I will add looking into this enhancement for you, to our API development list. As you mentioned, there are a few rules when it comes to changing user groups and permissions. (You cannot hide the Admin, etc.)
Another part of this request, can you also add the ability to "check" the box with an API call (both PUT and POST) so that it prompts the users to reset their password on login? "Require Password Reset: Check to prompt the user to reset their password upon logging in."
rgibbons wrote: Wed Oct 23, 2024 12:37 pm
Hello again,
Another part of this request, can you also add the ability to "check" the box with an API call (both PUT and POST) so that it prompts the users to reset their password on login? "Require Password Reset: Check to prompt the user to reset their password upon logging in."
Good afternoon rgibbons,
I have added the ability to set userod.IsPasswordResetRequired to the API development list.
rgibbons wrote: Thu Oct 10, 2024 10:12 am
Hello there, I work with rdillman and we have another small addition that we would like to add to this PUT method. When hiding the users, we tend to like to change their group as well to a group that has no rights, however this is especially important for some of our groups that have the Setup permission and "admin" abilities. We are unable to mark those employees as hidden because you cannot mark an admin as hidden.
Can we add the ability to specify the UserGroupNum as well on the POST, like the PUT has available so that we can change the group as well as mark hidden at the same time?
Thank you for taking the time to look at this request!
Hello rgibbons,
The ability to update userGroupNums has been added to the userod PUT endpoint in version 25.1.10. This field is also returned in userods GET. For more information, see userods PUT.