Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Are there any best practices or things to know when it comes to using and extending Umbraco's membership systems, and choosing which one to use?
I'm looking at using Umbraco's user/member auth system for an application that involves a bunch of portals/intranet type things that are managed by a customer.
Should these customers be "Users" in Umbraco (but have their CMS access disabled), or is it more accepted to use the "Members" system instead, for all cases that don't involve the backoffice?
Yes, generally you would use Members system if those members don't require any access to editing content in back-office. But if editing content via Umbraco interface is a requirement, then they'd have to be a User.
Just a word of caution - I had an application once that created around 2K Umbraco backend users, and it performed terribly. Members, however, performs much better.
Thanks Dan, sounds like members are the way to go.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted