This chapter described the Member Role. Simply put, it is a set of classes to be used by an ASP.NET application to handle its sites membership base and communicate with the data store. You looked at some limitations uncovered in the Member Role implementation due to DotNetNuke's multiple portals within the same application and how DotNetNuke overcame these limitations. You learned how DotNetNuke extended its abstract membership, roles, and profile providers so the concrete providers could be more flexible, and saw how a developer could create his own custom concrete providers. Now that you have an understanding of how the membership base is handled, you can move on to the next chapter where you explore some of the latest trends in web site development using DotNetNuke's ClientAPI.