Board Thread:General Discussion/@comment-26395054-20150630070237/@comment-5454372-20150630103521

Hiya, there're a few points to address and respond to from your post:


 * 1) Preventing bad faith edits: as the founder, you should have sysop/admin rights. Those give you the ability to block people from creating or editing pages, as well as various other restrictions. However...
 * 2) Full wiki protection: under the Community Creation Policy, you'll find a section titled "Public editing", stating that there's no option to restrict editing across the whole wiki to a certain user group. While you've got the capability as an admin to manually protect every page, you'll very likely find a Staff member removing all those protections due to the above, and continued insistence on privatising the editing may well lead to your admin rights being stripped. Additionally, since this may come into play later...
 * 3) "Owner" of the wiki: under that same section above in "Public Editing", Wikia clearly states that the founders do not have ownership of the websites. This ties into the section about "Free Content", where all text placed on Wikia then falls under "Creative Commons" licensing -- basically, by writing anything on Wikia, you lose your claim to stop anyone from copying or modifying it (unless the person who originally added the text to the first wiki was already breaching someone else's copyright in doing so).

Just to ensure everything's neatly wrapped up: all of that, while it came from a "policy" page, is also linked to in their Terms of Use explicitly, so legally speaking, the room to argue against it just being a policy is quite limited. If you want a website where you have pure control and rights over the text, you're going to need another host instead of Wikia.

As an afterthought: turning all your pages into user blogs would probably have the same effect as what you originally wanted (only admins can edit another person's blogs), but I'm not too sure how Wikia Staff may respond to that, especially given that this line of thinking is clearly in relation to circumventing the "no protecting all pages on a wiki" policy.