Member Permissions

Webonizer has many built-in functions, and there are many types of websites; because not all people using a website should be able to use all functions, it is necessary to affix permission levels to those functions.

Administrators of a site decide what functions each member can use. Through the Webonizer Site Settings page, the owner of a site can choose what the default permissions of new members are. An administrator can also change individual users’ permissions through each member’s permission form.

Below is an explanation of all permissions. *Note that all permissions that have an asterisk are ones that should not be given out lightly.

*Administrator: This flag makes a member an administrator of the site. The member will have access to virtually every area of the site—with the exception of Site Logos and Site Settings (which can only be accessed by the site’s super administrator/owner account). This permission should be given out cautiously, and only to highly trusted people. A site administrator can edit front page content, delete user accounts and edit any user’s documents on the site. This flag should never be checked in the Site Settings default membership permissions.
*Site Pages: This flag allows a member to edit site pages without being a full-blown administrator. Generally speaking, this flag should only be checked for members that are trusted and who need to edit content on pages such as your front page. Click here to learn more about Site Pages.
*Topics: This flag allows a member to create new topics as well as edit old topics. You should only give this permission to trusted sources. Click here to learn more about topics.
*Files: This flag allows a member to edit non-core files that Webonizer uses, such as Style Sheets, Custom JavaScript and extension PHP files without being a full-blown administrator. Members who have this permission can drastically alter the look, layout and functionality of the site. As a rule, this permission should be given to trusted individuals who are responsible for web development.
*Meta: This flag currently only applies to members who also have the Articles permission (below). If checked, the member may edit the meta content of an article. For example, the member may add the following tags to a Meta field: <link>,<script> and <style>. Granting of this permission is not advised because there are certain privacy issues that can open up if members link to external files such as JavaScripts and Style Sheets. Further, it is possible to create security issues if your site is using SSL and the referenced files are not secure.
Articles: This flag allows the member to post articles. If the Meta flag (above) is also checked, the member will be able to post to the article’s meta field; if Images (below) is checked, the member will be able to post images and other files into the article.
Images & Media: This flag allows the member to post media files to the server. If this flag is checked and the Articles flag (above) is checked, the member may load media into articles; otherwise, the member may only post to his/her profile. Note that the type of media and amount of each type per page are set with the Per Document Limits (below).
News: This gives a member to post to topics belonging to the News site page. This flag was created to set a standard by which news providers can distinguish verified news in a community site.
Newsletter: This permission will allow a member to send out newsletters through the site. If set, the member will have access to HTML code that can be pasted in other sites to collect email addresses on the site. The member can then send out newsletter articles as newsletters. This flag does nothing if Newsletters are turned off in the Site Settings page.
Events: This permission allows members to post calendar events. Click here to learn more about calendars. This flag does nothing if Event Calendars are turned off in the Site Settings page.
Guestbook: This permission allows the member to maintain a guestbook. Articles this member posts will include a “Comment on This” link that will post to the guestbook and to the article comment section. This flag does nothing if Guestbooks are turned off in the Site Settings page.
Front Page: If this flag is set, the member’s articles and images are eligible to appear on the site’s front page when posted. Note that such members’ articles may not immediately post to a front page if the Site Settings has Review Settings set to “Show only reviewed posts”.
Links: If this permission is set, the member may create links to external web pages that are grouped by the site’s topics. These links will appear in the links panel (turned on in Site Settings) on pages that match the topic.
Products: This is an all-purpose flag that sets permission for product administration. Note that Webonizer has no built-in use for this flag, but has reserved it for shopping cart developers to use when creating Webonizer plugins (such as Sellonizer). You should not check this flag until you have read the documentation for a shopping plugin (if you have one).
Featured Member: This flag is not a permission so much as an indicator. It is set to allow webmasters to show off members that deserve notice.
Verified Email: This flag indicates that the email address this member is using on the site has been verified through an email verification link or manually by an administrator.
Bounced Email: This flag indicates that a member’s email has bounced back to the server. Future versions of Webonizer will keep track of how many times an email address has bounced so that more dynamic bounce policies can be enforced.

Per Document Limits

The “Per Document Limits” set the amount of files and associations an article (or other document) may have.

Files Per Doc: This field sets a numeric limit on the total number of files (photos, video, sound, etc) that a document (article, profile, etc) may have. For example, if this limit is set to 12, a page may have 12 photos or it may have 6 photos, 3 videos and 3 zip files—but it could not have 11 photos and 3 zip files because the limit is 12 and 11+3=14. Note that the following fields further control the number of files can be added to an article by their type.
Image Limit: This field sets the limit on how many photos and images (JPG, GIF) can be loaded into a document. Note that if this limit is higher than the Files Per Doc limit, the Files Per Doc limit takes precedence.
Audio Limit: This field sets the limit on how many sound files (mp3, etc) can be loaded into a document. Note that if this limit is higher than the Files Per Doc limit, the Files Per Doc limit takes precedence.
Video Limit: This field sets the limit on how many videos (MPEG, WMV) can be loaded into a document. Note that if this limit is higher than the Files Per Doc limit, the Files Per Doc limit takes precedence.
Flash Limit: This field sets the limit on how many flash files (SWF) can be loaded into a document. Note that if this limit is higher than the Files Per Doc limit, the Files Per Doc limit takes precedence.
Zip Limit: This field sets the limit on how many zip files (ZIP) can be loaded into a document. Note that if this limit is higher than the Files Per Doc limit, the Files Per Doc limit takes precedence.
PDF Limit: This field sets the limit on how many PDF documents (Adobe PDF Files) can be loaded into a document. Note that if this limit is higher than the Files Per Doc limit, the Files Per Doc limit takes precedence.
Topics Per Article: This value sets a limit on how many topics an article may have. All articles must be able to have one primary topic. By setting this to 3, for example a member’s articles may have two secondary topics beyond primary topics.