Super Admin

Introduction

The Super Admin tool emerged as a need from ANDMORE’s Customer Support team to manage access for potential buyers and sellers on ANDMORE’s online platform. Before Super Admin, these processes were coordinated with the development team.

Key Features

• Single sign on (SSO) using ANDMORE employees’ Microsoft work identity
• Role-based access to manage buyers, sellers, or both
• Ability to assign a Customer Service team member to a customer onboarding request
• Ability to approve/deny customer onboarding request
• Ability to view supporting documentation for onboarding request
• Activate, deactivate, or suspend customer access
• Consistent design with other admin tools via private component library

Technology Stack

My Role

Initially, my team was solely responsible for the Datasynq project at ANDMORE. However, when the need arose to develop the Super Admin tool, my team assumed this responsibility. I took on the role of the initial architect for the Super Admin front end, while also delegating certain features to other front-end developers during their downtime between implementing Datasynq features.

As we progressed with the development of the Super Admin front end, we observed that other teams were concurrently building different admin tools with similar designs and user interfaces. It became evident that sharing UI code would be advantageous to standardize the appearance and user experience across projects, as well as facilitate the reuse of components. To address this, I initiated a component library project aimed at meeting the current development needs of our teams. The Super Admin project served as the initial testing ground for the components in this library, which were developed simultaneously. Although this approach initially slowed down the development of the Super Admin tool, the long-term benefits were evident, resulting in time savings across various projects.