Users

Overview

There are three types of users in Mura: Site Members, Administrative Users and Super Admins.

Super Admin

Super Admins have access to every site in a Mura install and have no restrictions whatsoever. The default Admin user that ships with Mura (username: admin, password: admin) is a Super Admin.

Administrative Users are users that are added to a Mura site using the "Administrative Users" manager in the Mura Admin. There are three basic types of Administrative Roles in Mura. All are determined by what group a user is part of and the rights given to that group on a specific node within the site. You can define these roles by editing a nodes "Permissions" (the "people" icon in the Site Manager). Permissions "cascade" down to all child nodes, so if you set permissions on the homepage, all site content will inherit those permissions until you redefine the permissions for a specific node.

It is also important to note that since permissions are group-based in Mura and can be extremely varied and granular, a user has no permissions or group memberships by default when they are initially created. They must be added to a group (admin or otherwise) to have any permissions (i.e. access to anything in the Mura Admin).

  • Admin - Making a user an admin is as easy as editing the user, clicking on the "Group Memberships" tab, and checking the "Admin" checkbox under "Administrative Groups." Admin Users have access to all Mura modules (Components, Email Broadcaster, Forms, etc.) and no restictions on a specific site within Mura (although you can share Administrative User Pools across sites)
  • Authors - This is not a default group within Mura, rather, it's a role that can be assigned to a group. A group that has "author" rights (as defined in a nodes "Permissions"), has the ability to create and edit content but cannot publish content.
  • Editors - Like Authors, Editors are a role in Mura but with one big difference: Editors can not only create and edit content, they can publish content.
    In addition, other permissions that Groups can be given on a node are "Inherit" (the default for all nodes), Read-Only (allows the viewing of content only), and Deny (simply denies access to the edit page).

Site Members

Site Members are public users of your site who have created a profile. This is often used for password protecting (which is also group based as opposed to user based like Administrative Users) sections of a site to provide access to additional functionality or specific content. Basically, anything you want to require some sort of User Registration for.

Comments

JP

documentation is lacking on how to (1) allow members to sign up (2) log in (3) secure content based on users....or groups.

this is a real high level overview of admin/authors/editors - users etc, but there is no detail on HOW TO - where do I find THAT information....

June 18, 2010, 12:54 PM
JP

let's put it this way - I'd almost expect a "user login / join" system content object - much like the 'allowcomment'....

June 18, 2010, 12:58 PM
Sean Schroeder

Turn on "extranet" in modules and "Allow Public Site Registration" on the "Extranet" tab. These can both be found in site settings. Then, restrict access to a page or section. Mura will pass in the login and registration form for you.

June 18, 2010, 1:07 PM
JP

Sean, thx, but that's not working....

I felt a little 'silly' as i actually logged out as ADMIN, to see what general user would see - and there was the 'log in' form - automatically appearing - i thought GREAT, idiot proof... BUT... I cant seem to make the site PUBLICLY ACCESSIBLE....

(Site Version 5.2.2421 )

Under Site Settings...

modules > Extranet (Password Protection) is set to OFF

June 18, 2010, 1:28 PM
Daniel

I have Administrative Users which has Admin rights, but it doesn't show him the File Manager. Is there a place where I can set permissions for file manager access. Thx.

June 24, 2010, 5:46 AM
Post a Comment
  1. Leave this field empty

Required Field