...
The primary feature change is that Unit Portal now leverages Microsoft AD to authenticate users logging into the application. When users attempt to sign into Unit Portal they will be redirected to a Microsoft login page where they can enter their Microsoft email and password. Once finished and authenticated, they will be re-directed back to the Unit Portal application which loads information based on the user’s authorized access.
...
A new Users module has been added to Unit Portal where those with the appropriate permissions “edit user” permission will be able to set configure permissions for other users of the system. By . A user’s ability to make changes in Unit Portal will be based on the permissions granted to them on the Users screen. By default, all users authenticated users via Active Directory will be able to see all Units and Matching information, but it will be read-only by default. Furthermore, the users users’ editing rights will be limited to their Division, Area Command, or Corps by using the information available within Active Directory. Territory users will have access to all Units. A user's ability to make changes in Unit Portal will be based on the permissions granted to them on the Users screen.
...
group membership in Active Directory. The list of group memberships for a user is read by Unit Portal and editing rights are determined for each user by the unit match defined between the AD match source and the unit in Unit Portal. Editing permissions apply to the matched unit and all descendants of that unit in the unit tree. For example, a user in a DHQ group matched to a DHQ unit in Unit Portal will be able to edit that unit and all units under the DHQ unit. The same applies to users in the THQ group – those users will have access to all units.
...
| Info |
|---|
When a user has access to a unit they also have access to any associated child units. |