b2evolution has a pretty powerful and deep permission management architecture but it is optional.

Simple permissions to start with

You will not need to worry about most of this if you are the only user of your system (because your the Admin and you can do anything).

Similarly, if you have multiple blogs, each under a single owner’s responsibility (with the Admin over them), you still may ignore most of the complex permissions.

Advanced permissions

If you want to have multiple editors per Blog/Collection, reviewers, moderators and maybe even different classes of users with different access permissions, then you might want to learn about leveraging b2evolution’s permission system.

b2evolution does *not* enforce specific groups and/or roles. Everything is configurable. Your groups and permissions can start very simple and grow as complex as you need them to be over time…

Overview of all possible permission layers

The permissions a User is entitled to derived from several things:

• The General application settings which may disable some features completely.
• The permissions of the User Group the user belongs to.
  • Some actions (for example when a User Moderator wants to delete another user) make use of the Group Level.
• The owner (defined here) of a collection has automatic permissions attached to his ownership.
• When turned on, the Advanced Permissions of the collection the user is trying to access. These allow to assign very granular permissions on the contents and settings to specific Users or (UserGroups)).
  • Some of the Advanced Permissions allow some Users to act on contents created by users of lower User Levels.
  • The Content Moderator role is derived from the granular permissions.