Skip to content

Version 1.1

Latest
Latest
Compare
Choose a tag to compare
@Paul-Borisov Paul-Borisov released this 03 Jul 15:30
· 47 commits to main since this release
v1.1
f9d195b

Supported features

All features of Version 1.0 with additions.

Version 1.1

  • Added three alternative ways to display user photos cached in the database:
    • Default: Redux Store + Query. It uses RTK hooks + a sync slice to save to store.
    • Redux Store with async thunk, the stardard way.
    • Previous logic with sessionStorage (the best performance in tests).
  • Added With... HOCS.
  • Optimized user photo rendering performance.
  • Fixed quirks in UI: nav blinks, Radix UI body shifts.

Version 1.0

  1. Full-size hierarchical and Organizational Charts with configurable levels.
  • They provide visual presentation of company's hierarchy based on selected attributes such as units, departments, teams, and manager-subordinate relations.
  • In order to generate Org Chart hierarchies using Entra ID data, the user has to be authenticated via the standard login URL of Microsoft 365.
    • While the user is not authenticated, mockup data is shown by default. This can be turned off in .env settings.
  • Hierarchies are configurable and printable.
  • The views support full and partial search by user's name.
  1. Creating a new user account in Entra ID or hybrid local AD at any level of the hierarchy under the supervision of a specific manager.
  • This option is available only for users that belong to global Entra ID roles of User Administrator or Global Administrator. Security checks are automatic so regular users cannot see this feature.
  • Required fields are minimal and include only First and Last name. The most of other attributes are optional or can be copied from the selected manager.
  • The creator can choose:
    • Account type being created - cloud-only (Entra ID only) or hybrid local AD with sync via AD Connect
    • Desired security groups to add the new user to. Default groups are taken from env-variables, more can be selected in UI.
    • User photo for the new account.
    • Sending a summary email to the manager after successfully creating the user.
  1. Two-stage offboarding for the leaving employee.
  • Stage 1 disables the existing employee in Azure AD or hybrid local AD, resets password, and removes group memberships. This stage is optional.
  • Stage 2 removes employee's account from Azure AD or hybrid local AD.
  1. Updating attributes of existing users in Entra ID or hybrid local AD.
  • This is an experimental feature, which currently supports changing EmployeeId. Mismatching EmployeeId was a frequent problem of my customer.
Assets 2
Loading