You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it is not possible to add someone with a manager role through the API, so we've had to do this manually for TAs of a class.
There are two design issues to work out
Groups currently represent users of a Resource Allocation, whereas the Manager role is on the Project rather than Resource Allocations.
We're not exposing Projects through the API.
One possible solutions is to expose both memberships through the API as different groups:
Ex. /Groups/allocation-123 would return the users of Resource Allocation 123 (currently /Groups/123). /Groups/project-1234-users would return the users with a User role on Project 123. /Groups/project-1234-managers would return the users with a Manager role on Project 123.
The text was updated successfully, but these errors were encountered:
knikolla
changed the title
Expose Managers of Projects from Group API
Expose management of Managers of Projects from Group API
Jan 19, 2024
knikolla
changed the title
Expose management of Managers of Projects from Group API
Allow management of Managers of Projects from Group API
Jan 19, 2024
Currently it is not possible to add someone with a manager role through the API, so we've had to do this manually for TAs of a class.
There are two design issues to work out
One possible solutions is to expose both memberships through the API as different groups:
Ex.
/Groups/allocation-123
would return the users of Resource Allocation 123 (currently/Groups/123
)./Groups/project-1234-users
would return the users with a User role on Project 123./Groups/project-1234-managers
would return the users with a Manager role on Project 123.The text was updated successfully, but these errors were encountered: