Browse Products
Browse Categories
Support
Resources
Let users register their own accounts via Active Directory, without losing control of your portal.
Creating user accounts in SharePoint is an important task; it's also extremely tedious, often repetitive, and generally unavoidable. Although they're the best ones to provide most profile and contact information, individual users can't be allowed to determine things like security rights, leaving IT managers with the burdensome task of creating hundreds -- or thousands -- of user accounts as they're requested. This bottleneck keeps users from getting the access they're entitled to, and your IT managers stuck doing data entry instead of their jobs.
The SharePoint User Registration Accelerator solves this bottleneck, enabling IT managers to create a simple, automated self-registration system where users provide profile information and confirm their e-mail address, and an admin-controlled Web Part automatically assigns creates a corresponding AD user with proper security access and group membership based on the provided e-mail. Administrators can create their own series of rules and filters, review and audit account creation requests, and best of all, offload a time-consuming task without worrying about losing control over the account creation process.
The SharePoint User Registration Accelerator includes these features:
Here's what happens when a visitor to the site containing the User Registration Web Part makes an Account Request.
1. The email address submitted by the user is checked against the Configuration List. A. If it fails to match any of the rules there, the request is denied. B. If it matches a rule, the request procedure continues. If the account request is ultimately successful, the new account will be created according to the specifics of the matching rule. Note that these rules are checked in the order they are stored in the list, so that the supplied email address falls under multiple rules, it will use the earliest one listed. 2. Next, the email address is checked against the Pending Request list. A. If it doesn't match any of the addresses stored on the list, it is confirmed as an original request, and the request procedure continues. B. If it does match an existing address, the request is denied. 3. Once the system has determined the email address has not already been used to create an account, an email message is sent to the submitted address to confirm its authenticity. At this point, the request is "pending". 4. When the user clicks the link contained within the authentication email, the new account is created, based on the specifics contained in the Configuration list (determined in Step 2) 5. Finally, a confirmation message is sent to the account's email address, containing the new user name and password.
1. The email address submitted by the user is checked against the Configuration List.
A. If it fails to match any of the rules there, the request is denied. B. If it matches a rule, the request procedure continues. If the account request is ultimately successful, the new account will be created according to the specifics of the matching rule. Note that these rules are checked in the order they are stored in the list, so that the supplied email address falls under multiple rules, it will use the earliest one listed.
A. If it fails to match any of the rules there, the request is denied.
B. If it matches a rule, the request procedure continues. If the account request is ultimately successful, the new account will be created according to the specifics of the matching rule. Note that these rules are checked in the order they are stored in the list, so that the supplied email address falls under multiple rules, it will use the earliest one listed.
2. Next, the email address is checked against the Pending Request list.
A. If it doesn't match any of the addresses stored on the list, it is confirmed as an original request, and the request procedure continues. B. If it does match an existing address, the request is denied.
A. If it doesn't match any of the addresses stored on the list, it is confirmed as an original request, and the request procedure continues.
B. If it does match an existing address, the request is denied.
3. Once the system has determined the email address has not already been used to create an account, an email message is sent to the submitted address to confirm its authenticity. At this point, the request is "pending".
4. When the user clicks the link contained within the authentication email, the new account is created, based on the specifics contained in the Configuration list (determined in Step 2)
5. Finally, a confirmation message is sent to the account's email address, containing the new user name and password.
System Requirements:
SharePoint 2007:
SharePoint 2010:
*Note: Bamboo products are not supported in an IIS Web garden configuration.
Release Notes for SharePoint 2007:
Release Notes for SharePoint 2010:
