MS Dynamics CRM Developer (2 roles)
Atlanta, GA | Contract
CLIENT’ s external user base consists of partners and contributors who assist CLIENT with ongoing initiatives or who are regulated by CLIENT and must meet various safety and compliance regulations. These users currently have the ability to log in through CLIENT’ s external website and request access to various applications and groups. Each access request is then vetted and either approved or rejected.
This functionality currently resides in three separate, interrelated, custom-built applications: MyAccount, UMP, and AppBroker.
* MyAccount is the internet-facing website which allows users to create accounts, log in, request access, and withdraw from CLIENT applications.
* UMP (User Management Program) is an internal application which allows CLIENT employees manage user accounts, distribution lists, and group memberships.
* AppBroker is an internal application that controls the applications to which external users can request access.
All three of these applications will be sunset and replaced with a new application which will be built on top of CLIENT’ s existing Dynamics CRM instance, leveraging the Adxstudio add-on to create the internet-facing customer portal.
The primary functionality of all three applications is business-critical to CLIENT and must be preserved. The existing functionality falls under two types of users: external users and internal vetters. External users must have the ability to manage their accounts; including creating accounts, resetting their passwords, updating their personal information, requesting access to applications, and withdrawing from applications. Vetters must have the ability to approve or reject access requests.
The applications available to external users fall into three primary categories: traditional applications, WebDAV folders, and groups. Access to traditional applications and WebDAV folders is controlled through AD groups. AD accounts for approved users are created in CLIENT’ s external domain (Client.net). Those accounts are then added to an AD group specific to the application requested.
The third primary type of application is a group. A group is a collection of users, not to be confused with AD groups. This collection of users is stored as a collection of email addresses in a Lyris list. They are used for distribution purposes including notifications, email blasts, and collaboration.