Since you seem to have at the heart of it, 2 types of activity I'd go with just 2 sites. One for the members, and one for the administrative functions while based on the user, they might only see a subset of the administration actions/views. If there's a 3rd type of activity, that doesn't really fall under the admin style, you might want a site for that.
On Friday, June 28, 2013 8:00:55 AM UTC-6, hbaragar wrote: > > Hello all, > > What are the decision points used to determine if one should be using a > subsite instead of just permissions? > > For example, an athletic might have the following kinds of users: > > - members > - receptionists, who can perform a restricted set of activities on > behalf of the members > - club professionals, who > - are member like in that they do the same things that members do > - administer members (including doing some actions on behalf of > members) > - set up and administer athletic program (e.g. leagues) > - club assistants, who have a subset of club pro functionality > - club administrators, who manage receptionists, club professionals > and assistants > - system administrators, who manage club configuration and club > administrators > > It doesn't make sense to set up a separate subsite for each kind of user > because there is a lot of common functionality for some kinds of users. > Should I separate subsite for major functional areas? Should I even use > subsites? > > Has anyone developed a hobo application with more than one subsite? If > so, are there any suggestions or lessons learned that you can pass on to me? > > Regards, > Henry > > -- > Henry Baragar > Instantiated Software Inc.http://www.instantiated.ca > > -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/groups/opt_out.
