It is possible, and a valid state, that Toaster starts running with no information in the database. This happens commonly when setting it up as a service (not starting through normal scripts), or when importing information from the Layer Index or toaster config file fails (due to invalid config file, Layer Index being down, etc). We need to have proper page designs and implementation for this situation.
There should be empty states in place for all pages. That work was covered by bug 6755 (see the attached design document). This doesn't mean they cannot be improved. Maybe we can look into that during 2.1
The Toaster manager should insure that the database is populated before deploying to other users. We should not need extra actions.