-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tweaks for Organisation Units #1052
Comments
FlorisFokkinga
added a commit
that referenced
this issue
Nov 13, 2023
baszoetekouw
pushed a commit
that referenced
this issue
Nov 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should a Org manager with one or more Units enabled maybe be called a Unit Manager instead? That would make the distinction between an Org Manager with Units and an Org Manger without Units much more clear.--> voor nu ok, probably solved by other UI tweaks. Maybe adjust if pilot users find it confusing.In table of admins/managers, show units the manager is responsible for (or "all"/empty/*)Unclear that you can click on a manager to adjust unit roles"CO's to be managed" -> "Units to be managed" (??)fixed"All CO's" -> "All units" (??) etcfixedAuthorisations:unclear how this works: if a manager can only manage a specific unit, are they then allow to manage COs without unit?ah: seems that if a CO has no Unit, all managers can manage theat CO (regardless of Unit of Manager). If CO has a Unit, only Unit Managers can manage it.Is this what we expect? Shouldn't the default be that a manager can manage no Units rather than all Units?ArTe: I think unit managers should only see (and be able to manage) CO's belonging to their own unit(s). Not other units and thus also not CO's without a unitbug An org manager scoped on one ore more units, should only be able to see and edit COs of those units #1060make clear for Org Manager which Units they can manage.--> no quick fix, let's wait for questions from actual users.Should Unit Managers be able to see (read-only) COs of other Units? Currently, they can't, but that's confusing, because it is unclear to those managers that they don't have a full view of the Org.--> no, minimal disclosureAn Org Manager can create COs without units (shouldn't be possible)--> fixeduse – (fixed in 2dc8a5c–
) instead of - (hyphen or hyphen-minus) in title of CO to separate Org and UnitIn edit, move "Relevant unit" to below "Responsible Organisation"fixedIn edit, make clear that "Relevant Unit" is coupled to "Responsible Organisation"--> order is changedplsc/sync
endpoint --> Output Org Units in plsc output #1265{name,id}
. In/api/collaborations/v1/{co_identifier}
and in/api/organisations/v1
--> Specification of units in Org API #1264The text was updated successfully, but these errors were encountered: