I think Kona and Valerie have covered off your first question perfectly, so I will throw in my two cents for the second one having done the install at our University.
We had some good advice from our Implementation guru at Instructure to take a step back and plan a little before we jumped too far in.
We tried to look at what we needed today, and where we thought the system could be in 12, 24, and 36 months time. We took into account the factors such as dissemination of permissions, segmenting data in 'test' sub accounts from 'production' sub accounts, and (for us) how we might map data back to our external systems (most specifically our other reporting systems).
What we learned from this process was, for our instance, having a sub-account specifically designated for 'testing' and course design, proved to be great to segment the data out from 'pre-production' courses, and those that were already running.
I think it largely depends on how many courses you are running, and as Kona and Valerie mentioned, whether or not you need to use some of the (rather awesome) features they provide.
Could you possibly tell us a little more about your environment and we might be able to give you some more targeted tips and thoughts?
Stuart
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.