Mura CMS Mura CMS Documentation is provided as is with no guarantee in accuracy. Introduction Credit:  Blueriver Mura is one of the easiest and most powerful Content Management and Digital Experience Platforms in the world. It frees content contributors to focus on what they do best — work with content and connect with users — in an intuitive, straightforward manner, without needing to call the IT team. In the Mura Content Manager's Guide, you'll learn how to harness the power of Mura so you can get done what you need to simply and easily. Basic Concepts Credit: Blueriver Logging In  There are a few of different ways to log in to Mura CMS as a content manager or administrator. The method you choose will depend primarily on what you're trying to do, as you'll see in the next steps. Log In From Back-End Administration View Go to your primary domain/URL and add "/admin/" to it. For example,  http://www.yourdomain.com/admin/ If you're not already logged in, you should be prompted with a "Login" screen Enter your Username and Password, then click the Login button Once logged in, you should be taken to the Content view Log In From The Front-End Public View Go to your primary domain/URL, and navigate to the page you wish to edit Now, press the Escape key and the lower case letter L (e.g., +l) You should be prompted with a "Please Log In" screen. Once logged in, you should now see the Front-End Toolbar appear at the top of the browser viewport, as highlighted below. Logging Out  There are a few different ways to log out of Mura CMS. The method you choose, will depend on where you're at while logged in to Mura. Log Out From Back-End Administration View Look to the top right part of your browser window, and on the the right of your name, click the down arrow, then select "Log Out" You should be logged out successfully and presented with a "Login" screen. Log Out From Front-End Public View On the Front-End Toolbar, look to the far right and locate the "Log Out" link. If you see the Mura logo at the top of your browser, but cannot see the Front-End Toolbar, simply click the Mura logo to toggle the visibility of the toolbar. Click the "Log Out" link, and you should be logged out successfully. Front-End Editing  With Mura CMS, most content managers tend to make content edits using the front-end editing options listed below. Inline Edit Inline editing is useful for content managers who wish to see how their content will appear in context to the rest of the page. As you'll see in another section, you can also add various display objects to different display regions using inline editing. For basic inline editing, follow the steps below. From the Front-End Toolbar, hover over the pencil icon, and select "inline edit" While in "inline edit" mode, a utility panel will open on the right hand side of your browser window. The utility panel contains several types of display objects that can be added to the various display regions throughout the page simply by dragging them into place and configuring them for how you'd like them to display. As you move your mouse around the browser window, the "Body" and other editable display regions will highlight. For example, if you hover over the "Body" region, a label will appear around it. If you double-click inside the "Body" region, the utility panel will change to "Editing Content" and a content formatting toolbar will appear above the content region. So, you can make a change and apply any desired formatting. When finished making your content change(s), move your mouse to the Front-End Toolbar, hover over "Save" and select your desired publishing option (e.g., "Publish").  Please note that "Publish" will only appear for groups that have been given "Editor" privileges. Congratulations! You've just edited content using "inline edit" mode. Full Edit When you need to edit something more than basic content and display objects, you will need to use "full edit" mode. In full edit mode, you have complete control over a vast number of attributes and options that will be discussed in future sections. However, let's at least get familiar with how to make a simple content edit in "full edit" mode. From the Front-End Toolbar, hover over the pencil icon, and select "full edit" The "Edit Content" modal window will appear. You'll see that it contains a number of tabs which are display across the top of the window that will be discussed later. However, if you scroll down, you should be able to located the "Content" region and a familiar formatting toolbar. From this window, you can simply click inside of it, make your change(s),  and apply your desired formatting. When you're done, you can select your desired publishing option (e.g., "Publish").  Please note that "Publish" will only appear for groups that have been given "Editor" privileges. Congratulations! You've just edited content using "full edit" mode. Basic Publishing  Content managers have a number of publishing options with Mura CMS. We've listed an overview of some of the various options below. However, we'll have a more in-depth look at publishing options and workflows in the  Groups, Users, and Access Control  section. Publishing options in "full edit" mode Publishing options in "inline edit" mode Save Draft "Save Draft" allows you to save a temporary, non-published version of content for later editing or approval. Draft versions are available for review by the user who created the item, or any site administrators Preview "Preview" does the same thing as "Save Draft" and then displays what the content would look like if it were published on the front end view. If using "Preview" from the back end administration area, it will attempt to launch a new window. Save to Change Set* "Save to Change Set" saves a version of the content in the desired "change set." A "Change Set" is like a virtual bucket where you can store any changes you want to make "live" at the same time. Change sets are managed via the Content Staging manager. We'll cover Content Staging in a future section.  Please note that this option will appear only if the Content Staging Manager module is enabled via Site Settings. Publish* "Publish" makes the content "live" and visible to the front end public view of your site. The content item's status will become "Published." This action will also remove any "Draft" versions of the content item. *Note:  "Save to Change Set" and "Publish" options will only appear for groups that have been granted "Editor" roles. They will not appear for groups with "Author" roles. Back-End Editing  While most content managers tend to make the majority of their content edits using one of the  front-end editing  options, content can also be edited from the back-end administration area. There are a couple of different ways to get to the back-end administration area. If you're already logged into the front-end public view of your site, you can simply click the "tree view" icon on the Front-End Toolbar, and you will be taken to a "zoomed-in" tree view of your content. Otherwise, you can access the back-end administration area by adding "/admin" to your domain name. For example, http://www.yourdomain.com/admin, and then log in. Once you've accessed the back-end administrator area, go to the "Content" view. Using either the "Tree View" or "List View" locate the content item you wish to edit, and select it. Now, you should see a familiar "Edit Content" screen. This is pretty much the same screen that you've seen before when using the "full edit" mode to edit content on the front-end public view. However, there are a few additional features, information, and options available from this view such as when the content item was last updated, it's "status" and a list of available "Actions" that we'll review in another section. From here, simply make your content edit(s) and select your desired publishing option just as you did before on the front-end. Restoring Deleted Content  Accidents can happen. Sometimes things get deleted, and we need to get them back—pronto. Not a problem. Mura's Trash Bin has every deleted item ready to be restored to its proper location. Access the Trash Bin Go to Site Settings > Trash Bin Search for the content you'd like to restore Click the "Edit" icon to see the metadata associated with the item you'd like to restore If you'd like to move the item to another location, use the "Select Parent" button to search for the item you'd like to move it underneath. Click "Restore" or "Restore All Items in the Delete Transaction" if multiple items were deleted at once, i.e. if the item has any child content that was deleted with it. The restored item will now be in its proper location with any children that were deleted with it if "Restore All Items" was selected. Summary  In this section, we covered the basic concepts of Mura CMS. You should now be able to log in to Mura, make simple content edits, and create new content. In the next section, we'll review Mura's content types and get to know the basics of creating/managing content. Basic Content Credit: Blueriver Content Types  In Mura CMS, it's important to understand that there are different types of content. For example, sometimes you may want to create a traditional "page" of content, where there's a body area of text and images. Other times, you may want to add a "file" such as a PDF document, image file, or a link to another website.  One very important distinction here is that each content type has several attributes and features such as the ability to use categories, tags, and control whether or not the item will display or not, or even restrict access to the information to specific group(s). Please take a moment and review each of the basic content types listed below. Page  Page content types are the website pages of your site. These are the most commonly used content types containing text, images, and links. Link  Link content types are simply URL links. They can be used to link to another section of your existing website, or to external websites. File  File content types are specifically any kind of file type that the system administrator has allowed Mura CMS to manage. File icons are used to denote most of the common file types such PDF, Word, Excel, Zip, and many others. Folder  Folder content types allow you to aggregate related content into a defined group. Folders are most often used for sections of the site that may contain "news" or "blog" type content. For example, folders typically display the "title" and "summary" fields of each content item that lives directly beneath it, and pagination occurs automatically. Folders are also configurable to display several other fields such as the content release date, categories, tags, how many items to display per page, and more. The folder’s “body” area will appear above the listing of content that lives beneath it. Calendar  Calendar content types allow you to display scheduled content in a traditional calendar format. Content placed directly under a "calendar" is scheduled by its "schedule" and has a number of configurable options such as whether or not the item should repeat, the frequency of when it should display, and more. Quick Upload  Quick Upload is not a content type. Rather, it's a way to upload multiple files, such as images and/or documents, all at once instead of having to upload each item individually. This is very useful when you wish to create a gallery of images, or even a library of documents. Custom Content Types  Custom Content Types may also be created by your website development team in order to accommodate unique data specific to your organizations requirements or needs. For example, maybe your organization hosts a large number of YouTube videos. In that case, a developer might use "class extensions" to create a special content type called "YouTube" which collects the URL to the video, and other important information about that video. Then, using custom code in your theme or via a plugin, the content may be displayed in a special way on the front end of your site. Admin Content View  There are many things you can do on the back-end administration view of Mura CMS that you cannot do on the front-end public view. Here, we'll explore the "Content" area of the "Admin View" and learn how to find content we might be looking for to edit.   Content Tree View  The "Tree View" is the default "Content" view in Mura CMS. The default Tree View button option is "Site" and is described in this section; the two other button options under Tree View (" Components " and " Forms ") are described elsewhere. From here, you can see all of the content in a hierarchical view, with the "Home" page being the topmost content item. We'll discuss  managing navigation menus  in another section. However, it's important to note that each row in the list of content is listed in the order it will appear in the navigation on the front-end public view of the site. So, all of the top level navigation, or the "Home" page, and it's immediate children will appear in the primary navigation of your site by default. You have several options for interacting with each row of content listed here. One option is clicking the vertical three dots on the far left of each row to reveal a menu of options. Zoom:  When a content item has children, selecting "Zoom" will drill into that section of the site. This often makes it easier to manage a specific section, or sub-section of a site without the clutter of viewing all of the siblings of a content item. You can keep track of where you are in context to the "Home" page by using the breadcrumbs found directly above the listing of content items. Edit:  Select this option to go to the "Edit Content" screen. Add Content:  Select this option to add a child content item.  Copy:  Select this option to copy the specific content item into memory. When you select this option, you can click the vertical three dots and a "Paste" option will appear so that you can paste the copied item. Copy All:  Similar to "Copy" except it copies both the selected item, and all of its children. View:  Launches a new browser window to see what the selected content item looks like on the front-end public view of your site. Version History:  Selecting this option will take you to the " Version History " screen where you can perform actions such as comparing versions, and edit old versions to re-publish them. Permissions:  Selecting this option will take you to the " Permissions " screen for the specified content item so that you can control who has "Editor" and "Author" permissions, or even explicitly deny a group access to content. Delete:  Selecting this option will generate an alert dialog to confirm whether or not you wish to delete the selected content item and all content nested beneath it. Another option are the icons on the far right of each row. Objects:  Objects can inherit or not inherit cascading, and they can also start a new cascade. Display:  The content is either displayed or hidden or controlled by a schedule; if hidden it can only be edited via the back-end administration area unless you know the URL to the page in order to edit via the front-end. Template:  The content can inherit the parent template, or use another template, and use an alternate child template for its children. Nav:  This option toggles whether or not a content item will appear in navigation generated by Mura. The navigation for the following page has been turned off: It does not appear in the News section below:   Updated:  The field indicates the date when the content was last changed. Components  The "Components" button is one of the options displayed under the "Tree View" tab within the "Content" section of the Mura CMS back-end administration area. From here, you can see all of the existing components as well as create and maintain components. For more information about Mura Components, visit the  Components  section. Forms  The "Forms" button is one of the options displayed under the "Tree View" tab within the "Content" section of the Mura CMS back-end administration area. From here, you can see all of the existing forms as well as create and maintain forms. For more information about Mura Forms, vist the  Forms  section. Content List View  By default, the Content "List View" displays all of the content as a listing of search results, sorted by the date each item was last updated.  From this view, you can apply a number of different filters to narrow your search as desired. For example, you can easily toggle between all site content, drafts you've been working on, any submissions or approvals that have been assigned to you, and more by clicking the area next to "Showing:" as illustrated below. You can also apply several other filters. For example, clicking on "Advanced Filters" opens up another set of form fields that you can use to enter keywords, narrow by content type, tags, and categories. Simply click the "Filter" button when finished, and Mura will return any results that match the filters you've applied. Basic Tab  When you select a content item to edit it, you're taken to the "Edit Content" screen. As you've probably already noticed, there are several tabs listed across the top of the screen. Note:  For information about the other tabs on this screen see the  Tabs  section. By default, the "Basic" tab is displayed. The "Basic" tab contains some of the most critical and commonly used form fields that are used for Mura CMS content. Also, it's important to note that this tab varies depending on the "Type" of content you are editing. For example, when you add a "File" content type, you won't see a "Content" field. Each of the form fields listed below apply to most content types though. Type:  This displays the content type selected when the content item was created. You have the option to change the content type here. Some content types aren't exactly compatible with others, which is why you may not see "File" as an option when the original content item was a "Page" or "Folder" content type. Title:  This is the most important field for any content item. It's also the  only  required form field by default. The text entered here typically appears as the page title, just above the content. The value entered here will be used to automatically create all other title fields, listed below, if they are left blank. Hence, when you change the value entered here, a prompt will be displayed asking if you wish to "Clear Additional Titles." Often times, you'll want to take advantage of this feature. Navigation Title (Optional):  The value entered here will be used for any navigation that's automatically generated by Mura. For example, it will be the text displayed on the primary or sub-navigation of your site. URL Title (Optional):  The value entered here will appear in the browser's address bar. For example, "About Us" would become "about-us" and when combined with the full domain, will appear as http://www.yourdomain.com/about-us/ HTML (Browser) Title (Optional):  The value entered here will appear on the browser's chrome or browser tab. Assign Associated Image:  This is a very special field where you can upload a primary image to be used along with the content item itself. The first is when the content item is a direct child of a "Folder" content type, the image is typically displayed along with the Title, Summary, and a few other fields in the Folder listing. Next, it will typically display on the content item itself. The size, and placement are determined by the layout and theme used. It can also be displayed on a "Folder" when it's a direct child of the Folder itself in the listing. You can either upload an image, enter a known URL of an image, or even select an existing associated by searching for one. The buttons above the image allow you to perform various actions. The crop marks button will direct you to the "Image Details" screen where you can adjust the image orientation, as well as create new crops for each of the defined image sizes. The info button will launch the "Edit Image Properties" window. Here, you can enter values into a number of various metadata fields. The download button will launch an alert asking if you wish to download the file. Select "OK" to download. Summary:  The text entered into this field is shown in special circumstances. The first is when the content item is a direct child of a "Folder" content type, the value from this field is typically displayed along with the Title, Associated Image, and a few other fields in the Folder listing. The other instance is when the content item has been restricted to public view, and the user attempting to view the content is not logged in. It will appear just above the log in screen. So, be careful to not enter any confidential information into this field unless your development team has instructed you that it's safe to do so because of some modification they've made to Mura CMS. Content:  This is the main body, or "content" of the content item. It's here that you will enter your primary text, images, and links.   Content Formatting  When editing the "Content" or "Summary" fields in Mura CMS, you're actually using a web text editor. The editor comes with a number of very powerful features. First of all, if you click the question mark found on the far right of the last row of tools, a dialog window will appear informing you that the web text editor was created by  CKEditor . While we'll cover some basics, you may find the  CKEditor User's Guide  a much more thorough resource. The Toolbar The first thing you'll notice when editing content with the web text editor is the toolbar that appears at the top of the editor window. A similar toolbar appears when you using "inline edit" mode on the front-end public view of your site as well. It contains menu buttons that give you access to various functions of the editor. All buttons are grouped according to their function and include both simple operations (like basic text  styling  or  formatting ) and more advanced features (like inserting media via a  dialog window ). The CKEditor toolbar buttons are illustrated with meaningful icons. If, however, you are not sure what functions they perform, hover the mouse cursor over the buttons to see a tooltip with the name of the function. Using the Toolbar In order to perform an operation assigned to a button, click the button once. In most cases it will either immediately perform some predefined action or open a dialog window with further configuration options for a feature. Remember that the toolbar can also be used with your keyboard. To enter the toolbar, use the Alt+F10 keyboard shortcut. To move to the next or previous button group, use the Tab and Shift+Tab keys, respectively. Within a button group, use the Left Arrow and Right Arrow keys to move between buttons of this group. To activate a selected toolbar button, press Enter or Space. Some of the buttons serve as placeholders giving you access to further options placed in a drop-down list. They are easily recognizable thanks to a small icon on their right. Clicking the name or the arrow icon of such button expands the list and lets you choose one of its options via the left mouse button. To select a drop-down list option you can also use the Tab or the Down Arrow key and then accept your choice by pressing Enter or Space on your keyboard. To hide the list, use the Esc key or click anywhere in the browser window. Collapsing and Restoring the Toolbar To save on screen estate, you can collapse the toolbar by pressing the   button or using the Alt+- (minus) keyboard shortcut. In order to return to the full toolbar view, press the same button or keyboard shortcut again. Uploading Images and Files Mura CMS uses  CKFinder  for its web file manager, which is maintained by the same organization that created  CKEditor . CKFinder is a file manager that can help you browse, upload, and manage files located on a web server - directly from your Internet browser and without the need to install anything on your computer. For complete documentation on how to use CKFinder, please visit  http://docs.cksource.com/CKFinder_2.x/Users_Guide . How to Create a Photo Gallery  As previously mentioned in the Folder section , Folders allow you to aggregate related content into a defined group. While they are typically used to keep content such as "news" or "blog" posts together, they may also be used to create photo galleries. In fact, there's nothing stopping you from creating a "folder of galleries" or "galleries of galleries".  To create a custom photo gallery, follow the steps outlined below. Navigate to the section of your site where you wish to add a photo gallery (or gallery of galleries, etc.), then add a "Folder" content item. In the " Title " field, enter the name of your gallery. For example, "My Photo Gallery". When finished, select your desired publishing option. Now that you've created a new Folder, you can add your images in a few different ways. First, keep in mind, this is just a Folder. So, you can add multiple "Pages", and just make sure you use the "Assign Associated Image" field to add your desired image for each page (this is essentially how "news" or "blog" posts are created. You could also add a "File" content type, and select an image as your file to upload. Or, you could use the " Quick Upload " feature to upload multiple images at the same time. Finally, you could select the "Folder" content type, and use the "Assign Associated Image" field for your image. In fact, using a specified image for the nested Folder is a great way to create "galleries of galleries".  The example below is using the Quick Upload feature to upload multiple images at the same time. When using this feature, keep in mind that you're able to modify the "Title" of the image before it's uploaded. After you've completed uploading all of your images as content items, whether it's Pages, Folders, Files, or you used the Quick Upload feature, you're ready to customize your Folder to make it function more like a traditional photo gallery, because your gallery will display just like any other Folder does by default. From the front-end view of your site, hover over the pencil icon, then select " Inline Edit ". Hover your mouse over the list of images in the body area, and click the pencil icon which should appear in the top-left corner of the region. The display object panel should now reveal the "Folder" configuration panel. From the "Folder" configuration panel, you may select your Layout, List Image Size, which Selected Fields you wish to display, Items Per Page, and more. For example, for the Layout, select "Grid", then select your desired "Grid Style" option and "List Image Size". You'll see the display automatically update as you make each selection, so you'll know what the gallery will look like for your site visitors. If you don't want the Title of each image to appear, select the " Edit " button beneath the " Selected Fields " label. The " Select Fields " dialog window should open. From here, you may click, drag and drop the field(s) you wish to display, or not display by moving them from one column, to the other. When finished selecting your desired fields, click  Update . The body area will update to reflect your updates. In addition, on the "Folder" configuration panel, make sure you set " View Images as Gallery " to " True " if you want a modal window to open when a user clicks on an image. You may also select the number of " Items Per Page ", and if your Folder contains more images than the number selected, Mura will auto-generate pagination for you. When finished, be sure to "Save" your changes by hovering over the " Save " button, and selecting your desired publishing option. Your new gallery should now be ready for viewing. If you set " View Images as Gallery " to "True", clicking an image will open the image in a modal window. If/when you wish to  reorder the images , you will need to do so via the back-end administration area, just as you would any other kind of content. Summary  In this section, we reviewed Mura's content types and got to know the basics of creating/managing content. In the next section, we'll look at structuring and organizing your content using built-in tools such as navigation menus, categories, tags, and more. Structure Credit: Blueriver Layout Templates With Mura CMS, you can alter the layout template of a content item very easily, and even set the default layout of the children of a particular section of your site. When it comes to selecting the default layout template for the children, think of this as laying out an outfit for a child to wear. The child could go ahead and wear it, or ignore your suggestion and go pick something else for themselves to wear. Setting Layout Templates There are a handful of ways to set and/or change layout templates. The options are listed below. Via Back-End Content Tree View From the back-end administration area of Mura, go to the "Content Tree View" area. Under the Template column, you can see whether or not a content item has its layout explicitly set or is inheriting the layout according to the parent. If the icon looks like a layout template  , then the layout template has been explicitly set for that content item. If the icon looks like a bullet, then it will honor whatever the parent has set as the "Alternate Child Template." If the Alternate Child Template is set to "none," then it will inherit from the "Layout Template" setting. To change the layout template, or view the layout template settings, simply click the icon in the corresponding row of the content item you wish to edit, and a balloon edit window should appear. Both the "Layout Template" and "Alternate Child Template" options will list all of the available layout options for your particular theme. When you've selected your desired settings, click "Submit" to save the new settings. Via Edit Content Item You can also edit the layout template settings by selecting your desired content item, then clicking the "Layout" tab. There, you should see the select menu options for both "Layout Template" and "Alternate Child Template." Make your desired changes, then "Publish" to save the new settings.   Default Layout Templates The default theme that ships with Mura CMS includes a handful of basic layout templates. However, the developers of your theme may have created their own, unique layout templates for use on the site you will actually be working on. So, template options listed below may be different than the options you see on your own site. Template Description blank.cfm This layout template will only output the page title and content. default.cfm This simply uses the two_column_SL.cfm layout template home.cfm This layout template is most often used specifically for the Home page one_column.cfm This layout template includes a Header area with primary navigation, a main body/content region, and a footer area three_column.cfm This layout template includes a Header area with primary navigation, a "left" column region, a "right" column region, a main body/content region, and a footer area two_column_SL.cfm The "SL" means "Sidebar Left." This layout template includes a Header area with primary navigation, a "left" column region, a main body/content region, and a footer area two_column_SR.cfm The "SR" means "Sidebar Right." This layout template includes a Header area with primary navigation, a "right" column region, a main body/content region, and a footer area Inline Edit Display Objects Display objects can be used to either enhance your layout or add functionality to your site. By default, Mura CMS includes a number of helpful display objects so you can quickly and easily add elements such as Collections , Components , Forms , and navigational aids. Developers may also create custom display objects, unique to your organization's needs such as a stock ticker, or even a full-blown application to be embedded within a single page or an entire section of your site. Accessing Display Objects To access inline edit display objects, from the front-end public view of your site, when you hover over the pencil icon located on the front-end toolbar, and select " Inline Edit " the inline edit panel appears on the right-hand portion of the browser. The inline edit panel contains a list of available display objects which can be applied to your layout. Inheritance Rules Display objects obey the Inheritance Rules applied to each content item. To edit Inheritance Rules, when editing a content item, select the Layout tab. The options for Inheritance Rules are outlined below: Inherit Cascade This is the default setting for new content items and "inherits" any display objects applied to the closest parent content item with a setting of "Start New Cascade." Start New Cascade This setting prevents any display objects applied to parent content items from displaying in the layout. Unless a child content item explicitly declares "Start New Cascade" or "Do Not Inherit Cascade," it will display any objects assigned to this specific content item. This setting is most often used on top-level sections of a site, so that display objects such as navigation will automatically appear in the same place throughout an entire section of the site. Do Not Inherit Cascade This is a very unique setting which prevents any display objects from appearing on the specified page, while allowing parental display objects to essentially flow through to its children. Display Object Types Visit each section below for an overview of the display objects that ship with Mura CMS. These objects are useful when you set up pages and forms as well as other areas of your site. Collection Collections  are essentially indexes of content based on pre-defined search criteria or filters. (Visit the Collections section to learn how to create and manage Mura Collections.) The " Collection " display object enables you to quickly and easily place these "indexes of content" throughout your site and layouts so visitors to your site may find additional information they may find interesting or useful to them. Follow the steps below to apply a Collection to a page or section of your site. From the front-end public view of your site, hover over the pencil icon on the front-end toolbar and select Inline Edit. The inline edit panel should appear on the right-hand portion of your browser. Select the Collection display object, and then drag it to your desired area, such as above the main content region. As you drag the display object, drop zone target areas will highlight with either a red dotted box or red dotted line. When you release the mouse button, the display object should appear on your screen, and the inline edit panel should display a form with configuration options. Additional options may appear depending on the selections made to various form elements. Content Source You will need to select a "Content Source" from one of the options listed below: Local Index Selecting the "Local Index" option will reveal the "Select Local Index" menu. Simply select your desired Local Index from the list, or click the "Create New" button to create a brand new Local Index Remote Feed Selecting the "Remote Feed" option will reveal the "Select Remote Feed" menu. Simply select your desired Remote Feed, or click the "Create New" button to create a brand new Remote Feed. You can also choose whether or not you wish to "Display Summaries on Content Object?" Related Content Selecting the "Related Content" option will reveal the "Select Related Content Set" menu. You can choose any defined Related Content Sets, or select "Custom" and then click the "Edit" button to build a custom Related Content Set specifically for this display. Layout The layouts listed below are merely the predefined options which ship with Mura CMS. Your options may vary if a developer has created additional options for your specific site. Default See "List" below Custom Displays content items based on a "custom" layout option created by a developer. This is just an example layout that ships with Mura CMS for developers to use as a starting point. Grid Displays content items as a "grid." You can also select the "Grid Style" by choosing anywhere from 1 Column through 9 Column options. List Displays content items as a "list" List Image Size You can select from the available options of small, medium, large, custom, or any other pre-defined image sizes to control the size of the image to be displayed in the listing of content, assuming " Image " is selected as one of the fields to display. Selected Fields This section of the form controls which elements of the content item will display in the listing. Click the " Edit " button to launch the " Select Fields " dialog window. Here, you can add and/or remove and rearrange fields you wish (or don't wish) to display in the listing. When finished making your selections. Click Update  to save your options. The selected fields will now appear on the form. Click and drag any of the fields in the list to reorder them as you wish. As you release the mouse click, the display object will dynamically update to reflect your changes. View Images as Gallery Options are True and False: True :  When a user clicks an image, a "Large" version of the image will open in a modal window. False : When a user clicks an image, it will be treated like a regular link and the user will be taken to the content item's URL. View All Link You can enter a custom URL for a user to be directed to when they click the "View All" link View All Label If you don't like the standard "View All" label for the "View All" link, you can enter your own here. Max Items This controls the maximum number of items to display. Items Per Page This controls the number of items to display before pagination kicks in. Label Enter the name for the new container. Alignment You may select an "Alignment" from one of the options listed below: Left Selecting the "Left" option will reveal the "Offset" and "Width" menus. Simply select your desired Offset and Width. Right Selecting the "Right" option will reveal the "Width" menu. Simply select your desired Width. Custom CSS Classes Enter the name of the custom CSS class. Select the Delete button to remove the Collection from the layout. When you're done making edits, select your desired publishing option to save your changes. Component Components are reusable content objects that can be shared across multiple pages or sections within your site. To learn more about Components, visit the Components section. Follow the steps below to apply a Component  as a display object to a page or section of your site. From the front-end public view of your site, hover over the pencil icon on the front-end toolbar and select Inline Edit. The inline edit panel should appear on the right-hand portion of your browser. Select the Component display object, and then drag it to your desired area, such as the right-hand column. As you drag the display object, drop zone target areas will highlight with either a red dotted box or red dotted line. When you release the mouse button, the display object should appear on your screen, and the inline edit panel should display a form with configuration options. Select Component You will need to select a "Component" from the options listed below: Simply select your desired Component from the list, or click the "Create New" button to create a brand new Component. Alignment You may select an "Alignment" from one of the options listed below: Left Selecting the "Left" option will reveal the "Offset" and "Width" menus. Simply select your desired Offset and Width. Right Selecting the "Right" option will reveal the "Width" menu. Simply select your desired Width. Custom CSS Classes Enter the name of the custom CSS class. Select the Delete button if you wish to remove the Component from the layout. When you're done making edits, select your desired publishing option to save your changes. Container A "Container" allows you to add a division (
) or section to a page or portion of your site to group additional display objects. Hence, you can then include additional display objects within the container itself. Follow the steps below to apply a Container to a page or section of your site. From the front-end public view of your site, hover over the pencil icon on the front-end toolbar and select Inline Edit. The inline edit panel should appear on the right-hand portion of your browser. Select the Container display object, and then drag it to your desired area, such as the right-hand column. As you drag the display object, drop zone target areas will highlight with either a red dotted box or red dotted line. When you release the mouse button, the display object should appear on your screen, and the inline edit panel should display a form with configuration options. Label Optionally enter a label to appear above the Container. Alignment You may select an "Alignment" from one of the options listed below: Left Selecting the "Left" option will reveal the "Offset" and "Width" menus. Simply select your desired Offset and Width. Right Selecting the "Right" option will reveal the "Width" menu. Simply select your desired Width. Custom CSS Classes Enter the name of the custom CSS class. Select the Delete button if you wish to remove the Container from the layout. When you're done making edits, select your desired publishing option to save your changes. Embed An "Embed" display object allows you to enter custom "embed" code into a page or section of your site. For example, maybe you want to "embed" a video from a third-party hosting service such as YouTube or Vimeo . Sites like these often allow you to copy "embed" code specifically for this purpose. However, videos aren't the only type of content you might want to "embed" into your site, as the options for embedding content from third-party sites is endless. Follow the steps below to apply an  Embed  display object to a page or section of your site. First, you will need to obtain the "embed" code from your desired third-party site. In this example, we'll use YouTube's "Share" and "Embed" options for a Mura CMS video: Be sure to copy the "Embed" code, and perform the following steps below. From the front-end public view of your site, hover over the pencil icon on the front-end toolbar and select Inline Edit. The inline edit panel should appear on the right-hand portion of your browser. Select the Embed display object, and then drag it to your desired area, such as above the main content area. As you drag the display object, drop zone target areas will highlight with either a red dotted box or red dotted line. When you release the mouse button, the display object configurator should appear on the right-hand portion of your screen, and the inline edit panel should display a form with configuration options. Paste the copied "embed" code Enter Embed Code Copy the "embed" code of the object such as a video and paste it into this field. Label Enter the name for the new container. Alignment You may select an "Alignment" from one of the options listed below: Left Selecting the "Left" option will reveal the "Offset" and "Width" menu options.  Simply select your desired Offset and Width. Right Selecting the "Right" option will reveal the "Width" menu options.  Simply select your desired Width. Custom CSS Classes Enter the name(s) of any desired custom CSS class(es). When you're done making edits, select your desired publishing option to save your changes. Below is an example using the "Share" and "Embed" code for an older Mura CMS YouTube video: Form You can easily add a Mura Form to a page or section of your site. To learn more about Mura Forms, visit the Forms section. Follow the steps below to apply a Mura Form as a display object. From the front-end public view of your site, hover over the pencil icon on the front-end toolbar and select Inline Edit. The inline edit panel should appear on the right-hand portion of your browser. Select the Form display object, and then drag it to your desired area, such as above the main content area. As you drag the display object, drop zone target areas will highlight with either a red dotted box or red dotted line.   When you release the mouse button, the display object should appear on your screen, and the inline edit panel should display a form with configuration options. Select Form Choose your  desired "Form" from the available menu options: Simply select your desired Form from the list, or click the "Create New" button to create a brand new Form. Alignment You may select an "Alignment" from one of the options listed below: Left Selecting the "Left" option will reveal the "Offset" and "Width" menus. Simply select your desired Offset and Width. Right Selecting the "Right" option will reveal the "Width" menu. Simply select your desired Width from the list of available options. Custom CSS Classes Enter the name of the custom CSS class. Select the Delete button if you wish to remove the Form from the layout. When you're done making edits, select your desired publishing option to save your changes. Navigation Mura offers a variety of Navigation display objects which can easily be added to a page or section of your site. Follow the steps below to apply a Navigation  display object. From the front-end public view of your site, hover over the pencil icon on the front-end toolbar and select Inline Edit. The inline edit panel should appear on the right-hand portion of your browser. Select the Navigation display object, and then drag it to your desired area, such as the left-hand column. As you drag the display object, drop zone target areas will highlight with either a red dotted box or red dotted line. When you release the mouse button, the display object should appear on your screen, and the inline edit panel should display a form with configuration options. Select Navigation Select your desired "Navigation" option: Simply select your desired Navigation option from the list. "Standard Navigation" is usually a safe bet when you're unsure. Alignment You may select an "Alignment" option: Left Selecting the "Left" option will reveal the "Offset" and "Width" menus. Simply select your desired Offset and Width. Right Selecting the "Right" option will reveal the "Width" menu. Simply select your desired Width. Custom CSS Classes Enter the name of the custom CSS class. Select the Delete button if you wish to delete the Navigation from the layout. When you're done making edits, select your desired publishing option to save your changes. System There are a variety of baked-in "System" display objects in Mura CMS including: Comment Form, Content Rater, Site Map, User Favorites, and User Tools. Follow the steps below to apply a System  display object to a page or section of your site. From the front-end public view of your site, hover over the pencil icon on the front-end toolbar and select Inline Edit. The inline edit panel should appear on the right-hand portion of your browser. Select the System display object, and then drag it to your desired area, such as the right-hand column. As you drag the display object, drop zone target areas will highlight with either a red dotted box or red dotted line. When you release the mouse button, the display object should appear on your screen, and the inline edit panel should display a form with configuration options. Select System Object Choose a "System Object" from the options listed below: Comment Form The "Comment Form" display object allows end users to add comments to content items within your site. This is especially useful for sections of your site such as "News" or "Blog" areas. If you apply Comment Form to a Folder content type, the form will not  appear on the Folder itself, and will only appear on the child content items within that section of the site. Note : If you don't see the "Comment Form" display object listed as an option, an administrator will have to review the Comments Permissions section . Content Rater A "Content Rater" allows end users to "rate" the content on a scale of five stars. Mura CMS tallies all ratings, and will display the "Average Rating" and total votes cast for the content item. Note : Content Raters are typically applied to a "Folder" content type so that the "rater" itself will appear on all of the children of the Folder. It will NOT display on the Folder itself, since these content types are typically used as "News" or "Blog" landing pages, and the landing pages (or Folders) aren't typically "rated" by users. This can be somewhat confusing because the Content Rater is "invisible" on the Folder when applied in this manner, yet "visible" on its children. Site Map Mura CMS can display an auto-generated listing of content items within your site in two different formats: Default and Tree View. Default The "Default" display format of the Site Map is essentially an unordered list, where child content is indented within the list. Tree View The "Tree View" display format of the Site Map attempts to show the content items in a hierarchical structured view.  User Favorites The "User Favorites" display object gives logged in users the ability to add content items to a list of their favorite pages so they can quickly and easily access these pages or areas of the site. Users also have an easy link to print the page they're currently viewing. If a user is not logged in, they will be prompted to log in to use the display object. User Tools The "User Tools" display object is nearly identical to the "User Favorites" display object, except it also includes links to "Edit Profile" and "Logout" along with a welcome message. Alignment You will need to select an "Alignment" from one of the options listed below: Left Selecting the "Left" option will reveal the "Offset" and "Width" menus. Simply select your desired Offset and Width. Right Selecting the "Right" option will reveal the "Width" menu. Simply select your desired Width. Custom CSS Classes Enter the name of the custom CSS class. Select the Delete button if you wish to to remove the System display object from the layout. When you're done making edits, select your desired publishing option to save your changes. Text You can add a text object very easily to a page or section of your site. Follow the steps below to apply a Text  display object. From the front-end public view of your site, hover over the pencil icon on the front-end toolbar and select Inline Edit. The inline edit panel should appear on the right-hand portion of your browser. Select the Text display object, and then drag it to your desired area, such as the right-hand column. As you drag the display object, drop zone target areas will highlight with either a red dotted box or red dotted line.   When you release the mouse button, the display object should appear on your screen, and the inline edit panel should display a form with configuration options. Select Content Source There are two options for "Content Source": Custom, and Bound Attribute. Custom Select "Custom" and click "Edit" You should now see an "Edit Text" window which contains a simplified HTML editor toolbar for basic formatting of your text. Simply enter your text, style it, and click "Update" to save. Bound Attribute Selecting "Bound Attribute" will reveal an additional menu option titled "Select Bound Attribute." Options include: Navigation Title, Title, Credits, Summary, and any custom fields created through Mura's Class Extension module. When you select an attribute, the value will simply display on the layout wherever you've applied the display object. Label You may optionally enter text for a label which would appear above the text. Alignment You may select an "Alignment" from one of the options listed below: Left Selecting the "Left" option will reveal the "Offset" and "Width" menus. Simply select your desired Offset and Width. Right Selecting the "Right" option will reveal the "Width" menu. Simply select your desired Width. Custom CSS Classes Enter the name of the custom CSS class. Select the Delete button to remove the Text display object from the layout. When you're done making edits, select your desired publishing option to save your changes. Managing Navigation Menus Mura CMS auto-generates hierarchical navigational elements based on the way content is structured, and sorted in the back-end administration area's  Content Tree View . For example, content items located immediately below the "Home" page may have a link auto-generated to it in the "Primary Navigation" area of the public-facing site. Only content items with " Nav (Display in Navigation) " set to " Yes " and " Display " set to " Yes " or if the current date falls within the schedule set under " Per Schedule " will be displayed to end users. In the above photo, you'll notice a link to "Site Map" and some of the other content items listed in the prior image don't appear in the primary navigation because the content items have either the " Nav " or " Display " options set to " No ." This concept applies anywhere navigational elements are generated by Mura CMS. In this section, you'll learn how to add navigational elements such as sub-navigation, to a specific region on the page, reorganize content items, as well as how to edit the navigation and menu items. Adding Navigation to Content Mura CMS includes several different types of navigational aids which can be applied to your site. The general concepts on applying navigational elements to your layout are covered under the Navigation section of Layout Manager Modules section.   Reorganizing Content Items This section covers the sorting and ordering options for navigational elements, including how to manually re-order content items within the back-end administration area. Sorting Content Items As mentioned in the Managing Navigation Menus section, Mura CMS auto-generates hierarchical navigation based on the way content is structured, and sorted in the back-end administration area's Content Tree View .  For example, content items located immediately below the "Home" page may have a link auto-generated to it in the "Primary Navigation" area of the public-facing site. Only content items with " Nav (Display in Navigation) " set to " Yes " and " Display " set to " Yes " or if the current date falls within the schedule set under " Per Schedule " will be displayed to end users. In the above photo, you'll notice a link to "Site Map" and some of the other content items listed in the prior image don't appear in the primary navigation because the content items have either the "Nav" or "Display" options set to "No." This concept applies anywhere navigational elements are generated by Mura CMS. Modify View From the Content Tree View, just above, and to the right of the content listing area, you should see a "Modify View" button. Clicking this button will reveal a number options which vary based on which section of the site you're currently "zoomed" in to. For example, if you're completely zoomed out to the "Home" view, clicking the "Modify View" button will only reveal an option to change the number of rows display. Note : For larger sites, Administrators may change the default number of rows to display (from 20) by going to Site Settings > Edit Site , and updating the " Default Rows (in Site Manager) " field. Content managers will have to log out, and log back in for the new setting to take effect. The only way to sort "top level" content items, located directly beneath the "Home" content item, is manually using the " Drag and Drop " method. To learn how to manually sort content items, please visit the Manually Sorting Content with Drag & Drop section. Once "zoomed" into a specific section of the site, by clicking the three-dot menu icon and selecting "Zoom," "Sort Navigation" options will appear on the Modify View menu. Sort Navigation Options Listed below are the various options for sorting content items located below the "top level" content items. Please note these sorting options only apply to the direct children of the section you are applying the sort options to. For example, if you sort by "Menu Title" in the "About Us" section, and you create a new section beneath that which contains its own child content, the new section will default to sorting "Manually" and have its own sorting options and capabilities. Manual: Sort the content items manually. This is the default setting. See Manually Sorting Content with Drag & Drop for more information on sorting content manually. Official Release Date: Sort the content items by the Official Release Date field, located the content item's  Publishing tab. Last Updated: Sort by the date the content items were last updated. Created: Sort by the date content items were created. Menu Title: Sort content items by their Navigation Title , as found on the "Basic" tab, and selecting "Show Additional Titles." Long Title: Sort content items by their Title field, as found on the "Basic" tab. Rating: Sort content items by the " Content Rating " the content item has received from end users. To have higher rated content appear first, select "Descending" for the Sort Order. Comments: Sort content items by the number of comments the content item has received from end users. Extended Attributes: If your site has any custom class extensions, their extended attributes may also appear as potential sort options. Once you have selected the sort criteria, you may choose to display the content items in either " Ascending ", or " Descending " order. Manually Sorting Content with Drag & Drop The default Sort Navigation option for content items in Mura CMS is " Manual ." In fact, top-level content, or content located immediately below the "Home" page, can only be sorted manually. Before attempting to sort content items manually, be sure the Sort Navigation is set to "Manual." Follow the steps below to manually sort content items. First, you must use the Content Tree View to sort content items manually. Next, select the content item you wish to move by using a click, drag, and drop method. We recommend clicking between the three-dot menu and the content item title, then dragging it up or down, then releasing the mouse click when the item has reached its intended target area. It's important to understand that to manually reorder "children" of a specific section, you must first "zoom" into that specific section. In the prior example above, you'll notice that moving the "About" content item selects all of its children as well, and moves along with it. The same would occur if you attempt to select a child of the About section while zoomed out to the "Home" top-level view. Once you've finished manually re-ordering the content items, you must select the "Update" button from the notice that appears above the content listing to save the new sort order.The new sort order should now be reflected in your navigation menus on the front-end public-facing site. Selecting New Parent When you wish to move a content item to a new section of the site, you can quickly, and easily select a new "parent" for the content item. Follow the steps below to change a content item's parent, and move it to a completely different section of the site. Select a content item to edit. Note, if you're editing from the front-end public-facing view, be sure to select "Full Edit" option. Select the Basic  tab from right-side menu on the Edit Content screen. Click the Select New Parent button to reveal a search box and Search button. Enter text into the search box and click the Search button to obtain a listing of content options. The first option in the list with the radio button selected is the current content parent. Simply select your newly desired option, and select your desired publishing option to save the new content parent. The content item, and all of its children, if any, should now be located under the new content parent. Editing Navigation/Menu Titles Sometimes, when you create a content item, you might want the text which appears for a link to be different than the actual title of the page. For example, you might have a page "Title" of "About Us." However, you would prefer any links to this page to simply output as "About" instead. Mura CMS offers a convenient and easy method to accomplish this. Follow the steps below to edit a content item's title fields. Select a content item to edit. If editing content on the front-end public-facing view of your site, you will need to use "Full Edit" mode. Open the  Basic  tab on the right-side menu. There are several title options: Title:  The actual title of the page you are editing. The page title will display as the headline or title on a given page. Navigation Title (optional):  You may enter an optional, shorter, or completely different title to be used wherever Mura generates navigational links to this content item. If this field is left blank, Mura will auto-generate the text based on the information entered in the "Title" field. URL Title (optional): Text entered here will display in the browser's address bar. If you choose to customize this field, be sure to use URL-friendly characters (e.g., use only alpha-numeric characters, etc.). If this field is left blank, Mura will auto-generate the text based on the information entered in the "Title" field, in a URL-friendly manner by replacing spaces and punctuation with hyphens, etc. HTML (Browser) Title (Optional):  Text entered here will appear in the browser's "chrome" or "tab" typically located above the address bar. If this field is left blank, Mura will auto-generate the text based on the information entered in the "Title" field. If you wish to update the "Title", if you press the spacebar while in the Title field, a notice with a button to "Clear Additional Titles" should appear.If you would like Mura to regenerate all of the additional title fields based on the new text entered, simply click the "Clear Additional Titles" button, and Mura will wipe out the old values, and then update those fields once you publish the content item. After making your desired changes, select your preferred publishing option to save your changes. Mobile Navigation You can control the display of a link generated by Mura based on whether or not a visitor is accessing the site from a "mobile" device. This is quite useful when you might want to display mobile-specific content, which may not necessarily apply to someone accessing your site from a non-mobile device, and vice versa. Note : Mura does not consider tablets, such as iPads, as mobile devices since they typically have screen real estate and resolution capabilities on par with most desktop and laptop computers. Follow the steps below to control the display of a link to a specific content item when a user is accessing the site from a mobile or non-mobile device. Select a content item to edit. If editing content on the front-end public-facing view of your site, you will need to use the "Full Edit" mode. Select the Publishing tab from the Edit Content screen. Scroll down to the Mobile Navigation section. Include for all: A link will be generated by Mura regardless of which device type the visitor is using. Include for Mobile Only: If a visitor is accessing the site from a mobile device, Mura will generate a link to this content item. Otherwise, it will not appear in any Mura generated navigational elements. Exclude from Mobile: If a visitor is accessing the site from a non-mobile device (e.g., tablet, desktop, laptop, etc.), Mura will generate a link to this content item. Otherwise, it will not appear in any Mura generated navigational elements. After you've chosen your desired option, simply select your preferred publishing option to save your changes. Note : Just because a link is not generated by Mura doesn't mean the content is not "visible" per se. If a visitor knows the URL to the content item, they could still technically enter that URL in their address bar to see the content. If you wish to completely hide content item altogether, use the "Display" filed located on the same tab. Taxonomy Mura CMS allows you to "categorize" and/or "tag" content in order to classify content so that users are able to search and/or filter content that's relevant to their own interests. Please refer to the sections below for details on the differences between the two options. Categories Mura CMS enables you to create a hierarchy of categories, and then assign content items to one or more of those categories. By categorizing content, you can create unique indexes, or collections, of content items that you can use throughout various sections of your site to highlight content. In addition, Mura CMS offers a built-in category filter as a display object that site visitors can use to drill down to content that might be of interest to them. Creating Categories To create categories, you need to go to the Categories section of the back-end administrator and follow the instructions below. From the Categories section, select "Add Category" You should now see the "Add Content Category" screen Name : This will be the name of the category URL Title : Leave this blank to have Mura automatically generate your category a URL title based on the name you chose. Or, feel free to enter your own unique URL title. Parent Category : The select menu will display all existing categories. If you prefer the category be assigned as a subcategory, simply select the desired parent category. Otherwise, select "Primary." Is this an interest group? : Select "Yes" to allow Site Members to choose it when completing/editing their profile. Allow Content Assignments? : If "Yes" then content can be assigned. If "No," it will simply show as a heading on the Categorization tab under "Available Categories. This is useful when you want to group some categories together, but not necessarily allow content to be categorized as such. For example, you might have a category called "News Categories" that contains several subcategories, and you wouldn't really want someone to assign content to this specific category. Allow Content Features? : If "Yes" the content can be featured under the specified category. Active? : If "Yes" then the category will appear as an option for content managers to assign content to, otherwise it will be hidden. Restrict ability to assign content to this category? : If utilized, only the group(s) selected will be allowed to assign content to this specific category. Notes : Enter any notes pertinent to the category, if desired. It's not used for any display purposes. Complete the fields as desired, then click "Add" to create your desired category. Categorizing Content Once you've created one or more categories, you can categorize your content by following the steps below. Select a content item to edit. Select the "Categories" tab. Select one or more options from the list of available categories. Select your desired publishing option. Repeat these steps for any other content items you wish to categorize. Congratulations! You've successfully categorized content. Feature Categorized Content Sometimes, you'll want to feature one or more content items within one or more categories. Under the "Feature" column, click the icon to open the Feature quick edit popup. Select "No" and the content item will not be featured within the specified category. Select "Yes" and the content item will be included in a content collection/local index that is looking for "featured" content within that category. Selecting "Scheduled Feature" is the same as "Yes," except the content item will only be featured during the specified period of time.   Category Summary Display Object The Category Summary display object is a listing of categories used throughout the site, where each category listed contains a count of categorized content items and is hyperlinked to a search results page to display content items associated with the selected category. Displaying a Category Summary Category Summary display objects are typically applied to Mura Folder content types so that the display object will also appear on child content items, such as a "News" or "Blog section of a site. To display a Category Summary, follow the steps below. From the front-end public view of your site, select a content item to edit such as the "News" section, and from the front-end toolbar, hover over the pencil icon and select Inline Edit . The inline edit panel should appear on the right-hand portion of the browser. Select the Navigation display object, and then drag it to your desired area, such as the right-hand column. As you drag the display object, drop zone target areas will highlight with either a red dotted box or red dotted line. When you release the mouse button, the display object should appear on your screen, and the inline edit panel should display a form with configuration options. Select "Category Summary" from the Select Navigation menu. When you're done making edits, select your desired publishing option to save your changes. Tags Mura CMS allows you to add free-form "tags" to content. A "tag" is a non-hierarchical keyword or term assigned to a piece of information. Tags are usually single words. This kind of metadata helps describe the item and allows it to be found again by browsing or searching. If a tagged content item is child of a Mura Folder, each tag may display, along with other summary information, and would be hyperlinked to other content items associated with that tag. Tagging Content Follow the steps below to add/edit content tags. Select a content item to edit. If you're editing content from the front-end public view, use "Full Edit" mode. Select the "Tags" tab. If the content item you've selected has already been tagged, they will appear below the text box. If you want to delete/remove one of the existing tags, simply click the circle with an "x" in the middle of it just to the right of the existing tag. If you want to add/create a tag, type the word into the text box, and hit "Enter" or "Return" on your keyboard. As you type, Mura will display a list of tags that have already been used before that match the letters you're typing. So, for example, if you type a "k" into the text box, any tags that contain a "k" in it will appear below. Also, if you click the down arrow in the empty text box, a full listing of tags that have already been used will appear. If your desired tag appears in the list, simply click on it, and it will be added. When you're finished tagging your content, select your desired publishing option to save the content. Depending on how your layout templates were created, your tags may appear with your content. Visit the Tag Cloud Display Object section for more information. Tag Groups Tag Groups offer a way to apply tags to individual sections, such as "News Tags" or "Blog Tags." This will also allow for the ability to display a specific grouping of tags that only apply to a specific region of a site, for example. Creating Tag Groups To create tag groups, follow the steps below. Go to the back-end administration area Select  Site Settings > Edit Settings On the Basic tab, scroll down to locate the Custom Tag Groups form field Enter your desired tag group names, separated by a carat ( ^ ) in between each group name Click Save Settings That's it! Using Tag Groups To use tag groups, follow the steps from  Tagging Content to apply tags to content items, using the desired specific tag group(s). For example, in the illustration below, the tags " california " and " wine " have been applied to the " News Tags " tag group. When finished applying your tags, select your desired publishing option to save your content. Tag Cloud Display Object The Tag Cloud display object is a visual representation of text data, used to depict keyword metadata (tags). Tags are usually single words, and font size is used to indicate how frequently each tag has been used. Each tag is hyperlinked to a search results page containing a listing of associated content items. Displaying a Tag Cloud As a display object, Tag Clouds can be applied to most any area of a site or layout. Typically, Tag Clouds are used on Mura Folder content types so that the display object will continue to appear on child content items, such as a "News" or "Blog" section of a site. To display a Tag Cloud, follow the steps below. From the front-end public view of your site, select a content item to edit such as the "News" section, and from the front-end toolbar, hover over the pencil icon and select Inline Edit . The inline edit panel should appear on the right-hand portion of the browser. Select the Navigation display object, and then drag it to your desired area, such as the right-hand column. As you drag the display object, drop zone target areas will highlight with either a red dotted box or red dotted line. When you release the mouse button, the display object should appear on your screen, and the inline edit panel should display a form with configuration options. Select " Tag Cloud " from the Select Navigation menu, and then select your desired tag group from the Select Tag Group menu. Once you do, the display object will dynamically update to reflect your configured options. When you're done making edits, select your desired publishing option to save your changes. Summary In this section, we covered how to manage navigation menus, layout templates, categories, and tags. We also reviewed some of the display objects that are available in Mura CMS and how to apply them to your various layouts. In the next section, we'll dive deeper into content editing, and learn more about the various fields that are available to use. Advanced Content Credit:  Blueriver Tabs  When editing content via the back-end administration area of Mura, or using the "Full Edit" feature from the front-end public-facing view of your site, the various fields that are available for content items are grouped together within tabs. You can think of the Edit Content screen as simply one, giant form, because that's essentially all it is. The " Basic Tab " is covered under the " Basic Content " section. In this section, we'll cover the other tabs available to you when editing content. If you see a down arrow on the far right of the listing of tabs, simply click the arrow to view the additional tabs. This occurs when the browser is too narrow to display them all within the browser's viewport. Note : If you don't see one of the tabs specified in this section, the group(s) you belong to may not have been granted access to those tabs. Your site may also include tabs not identified in this section of the site. If so, your instance of Mura CMS is most likely using a custom plugin used specifically to create custom tabs and fields unique to your organization's needs. Publishing  The  Publishing  tab is where you manage a content item's publishing-related fields such as Credits, Meta Description, Meta Keywords, Restrict Access to Specific Group(s), whether or not to Include in Site Navigation, whether or not to Display the content item, etc. Credits This field is much like a "byline" in a newspaper article, where you may enter the name(s) of the writer(s) of the the content. Information entered here may appear on the parent content item, if the parent is a  Folder  content type. This is especially useful when the content item itself is being used as a traditional "news" or "blog" item. Meta Description Information entered here is used for the description attribute within the   tag for the specific content item. See  https://support.google.com/webmasters/answer/35624?hl=en#1  for information on creating good meta descriptions. Meta Keywords Information entered here is used for the keywords attribute within the   tag for the specific content item. In the early days of web sites, this field was used by search engines in their web search ranking algorithms. However, information entered here is mostly ignored by search engines these days, as in 2009  Google officially announced they do  not  use the keywords in their web ranking . Restrict Access to Specific Group(s)? Use this field to limit which group(s) are allowed to view the "Body" of the specific content item. You may  + click  (via PC) or  + click  (via Mac) to select more than one group. Note:  This field will only appear if  Extranet (Password Protection)  is enabled via the  Site Settings > Edit Settings > Modules  tab. Include in Site Navigation If "checked" or enabled, anywhere Mura auto-generates navigational links, the specific content item should be listed, unless the item is not on display. If "un-checked" or disabled, Mura will not generate a link to the specific content item, however, if the content item is set to display and a user knows the URL of the content item, the content will display. This is useful when you wish to create content items such as landing pages from Google AdWords, or wish to have a Site Map, or other informational type page available to users, and don't wish to include a link in the primary navigation or sub-navigation. Mobile Navigation Mura CMS checks a browser's user agent string to determine whether or not the visitor is accessing the site from a mobile/handheld device. You may choose to show or hide links to content based on this information. Note : Mura does not recognize tablets (e.g., iPad, Fire tablet, etc.) as mobile devices, since they typically have plenty of screen real estate to accommodate most traditional websites. Include for all  (default) Links to the specific content item will be generated by Mura, regardless of which type of device the visitor is accessing the site from. Include for Mobile Only Links to the specific content item will only be generated by Mura if the visitor is accessing the site from a mobile/handheld device. Exclude from Mobile Links to the specific content item will not be generated by Mura if the visitor is accessing the site from a mobile/handheld device. In other words, links will only appear when accessing from a laptop/desktop computer or tablet. Open in New Browser Window If enabled, when a user clicks a Mura-generated link to the content item, it will open a new tab or browser window. Exclude from Site Search If enabled, the content item will not be included in search results when using Mura's search capabilities. Note:  This does  not  control whether or not links to the content item will appear on search engines such as Google, Yahoo!, Bing, etc. If you wish to exclude the content item from commercial search engines, you could password protect the content by using the  Restrict Access to Specific Group(s)  setting. For more information on controlling website crawlers and search engine indexing, visit   https://developers.google.com/webmasters/control-crawl-index/ Official Release Date (Optional-Informational Only) The date and time you enter/select here is meta-data only. It is  not  used for scheduling purposes, and is informational only. If you wish to schedule content to appear on a specific date, use the  Display  field. Information entered here may appear on the parent content item, if the parent is a  Folder  content type. This is especially useful when the content item is being used as a traditional "news" or "blog" item. You may also  sort content items  by this field in specific sections of your site. Display This field controls whether or not the content item will be visible to users via the public, front-end view of your site. Yes If Yes, then the content item  will  be visible to users via the public, front-end view of your site. No If No, the content item  will not  be visible to users via the public, front-end view of your site, and links to the content item will not be generated, even when "Include in Navigation" is enabled. If a user lands on the specified content item when set to "no," they will see a screen with the default title of "Content Off-Line" and text of "We're sorry, this page is currently unavailable." Per Schedule You may specify a schedule for the content item to display, including the frequency of the display such as daily, weekly, monthly, etc. and when the content item should stop displaying, if ever. Content Parent You may use this field to move a content item to a new section of the site. See the  Selecting New Parent  section for more details and instructions. Content Expiration Entering a date/time in this field will simply flag the content item as "expired" and that it needs to be reviewed. It does  not  control whether or not the content item is on display. If you want a content item to stop displaying on or after a specific date/time, please use the  Display  field. Assign Content Expiration Notifications This field is useful when you wish to notify user(s) when a content item has expired according to the date/time entered under  Content Expiration . If enabled, a Select users menu appears. Select users Select one or more users to be notified when a content item has expired, according to the date/time entered under  Content Expiration . They will receive an email notification, and may also locate expired content via the  List View tab of the Content view . Feature in this section? This field is a meta data field used to determine whether or not you wish the content item to be featured within the section is resides. This is useful when creating  Collections , and you wish to highlight the specific content item. For example, a "Featured News" Collection might scan through all content items within the "News" section, and only pull out content items that have this field set to "Yes" or the date falls within the range specified under "Per Schedule." No  (default) If selected, the content item  will not  be flagged as featured. Yes If selected, the content item  will  be flagged as featured. Per Schedule If the current date falls within the specified range, the content item will be flagged as featured. Otherwise, it will not be flagged as featured. Notify For Review When enabled,  Send to  and  Message  fields will appear. Send to You may select one or more users to receive an email notification after saving or publishing the content item. To select more than one person, use  + click  (on a PC) or  + click  (on a Mac). Message Text entered here will accompany a link to view the content item in the email notification. Add Notes This field allows you to enter informational notes which can be shared amongst content managers, without it appearing anywhere on the public, front-end view of the site. Layout  The  Layout  tab is where you can manage  Layout Templates , and  Inheritance Rules  for display objects. Layout Template Controls which layout template to use for the content item you're currently editing. Alternate Child Layout Template Optionally select an alternate layout template to use by default for any children of this content item. If "none" is selected, child content items will use the selection from the "Layout Template" by default. Inheritance Rules Inherit Cascade This default option allows the content to inherit any display objects assigned to parent content items. Start Cascade ??????? This option will prevent any display objects that have been assigned to parent content items from appearing, and begin a new cascade of display objects. This option is most commonly used when creating  a top level section of the site such as News, or Blog sections, etc. Do Not Inherit Cascade This option will prevent any display objects assigned to the parent from displaying, yet allow those display objects to pass through to its children. Content Objects Since display objects are managed via the front-end public-facing view of the site, a link is provided to take you to that view in order to manage any content display objects.               Categories  The  Categories  tab is where you manage a content item's Categories. To learn more about  Categories , including how to create/manage categories, and categorize content, visit the  Categories  section. Tags  The  Tags  tab is where you manage a content item's Tags. Visit the  Tags  section to learn more about Mura Tags. Related Content  The  Related Content  tab is where you manage a content item's Related Content. The content can exist either on the same site as the content item itself, or on a completely different website altogether. The information collected here is used when outputting the "Collection" display object, if the content source is set to "Related Content." See the  Collection  section for information on how to output the a listing of Related Content. Where is the Related Content? You may select content from either "In this site" or enter a link to content located "On another site." In this site Enter text into the search field, then click the spyglass to obtain a listing of search results. Optionally, select the "Advanced" button to filter your search results to specific Content Types, Official Release Date Ranges, and Categories. On another site Title Text entered in the "Title" field will appear wherever a link is generated or displayed by Mura CMS. URL The "URL" entered here will be the link used to direct a user if/when they click the "Title" entered above. Click the plus sign located next to the URL to generate a list of "Available URLs" How to assign an item to Related Content Set Once you've either located content you wish to use as "Related Content" via "In this site" or "On another site," you can either click, drag, and drop the item to your desired Related Content Set, or click the plus sign located to the left of the item, and then click the checkbox next to your desired Related Content Set to assign it as related content. How to sort items in a Related Content Set You can also control the sort order of the related content items by dragging and dropping the items into your desired order. How to remove an item from a Related Content Set To remove an assignment, locate the item you wish to delete under the Related Content Set, and click the circle with the "x" at the far right of the item's row. Select your desired publishing option to save your changes. Note : Relationships created using this method are one-way by default. This means that if "Content Item A" is related to "Content Item B," then "Content Item B" is not necessarily related to "Content Item A." If you want to make the relationship both ways, you'll need to edit the other content item, and repeat the process to complete the two-way relationship. Extended Attributes  The  Extended Attributes  tab will appear if your site is using Class Extensions, and you're editing content with custom attributes/fields that have been explicitly assigned to this tab. Please consult your organization's documentation for details about any custom fields located here. Advanced  The  Advanced  tab contains some information about the content item, and includes a few optional fields as described below. Content ID This is a unique identifier for the content item. Current Filename This is the unique filename for the content item. The information located here is used by Mura as the unique URL path to the content item, and will be displayed in the URL when viewing the content from the front-end view of your site. SSL SSL (Secure Sockets Layer) is a cryptographic protocol that provides communications security over a computer network. SSL is used to secure all communications between the servers and web browsers. Note : Before using this feature, please check with your Site Administrator to ensure you have a proper SSL certificate installed for your website. Make this Page secure via SSL? If enabled, when a visitor attempts to access the content item, Mura will check to make sure the URL is being accessed via the " https:// " secure protocol vs. the unsecured " http:// " protocol. Note : If you wish to secure the entire site under SSL, go to  Site Settings > Edit Settings , and set  Use SSL (Sitewide)  to " Yes ". Locking Mura offers the ability to "lock" content items so they will not be accidentally deleted by content managers. Lock Node If enabled, content managers will not be able to delete the content item. Remote Information (Optional) These fields are primarily used by developers and can usually be ignored by most content managers. Developers often use these fields when importing or associating the specific content item to content which exists on an external website, database, or network system. Remote ID This field typically stores the unique ID of content from an external website, database, or network system. However, this field does  not  have to be unique in Mura. Remote URL This field typically stores the unique URL of content from an external website or network system. Remote Publication Date This field typically stores the publication date of content imported or associated to content from an external website, database, or network system. Remote Source This field typically stores the name of the remote source for content. Remote Source URL This field typically stores the primary domain of the remote source for content.   Publishing Options  Content managers have a number of publishing options with Mura CMS. You can learn about some of the basic publishing options by visiting the  Basic Publishing  section. In this section, you can learn about version histories, comparing different versions of content, inspecting audit trails, and how to import and export content. Version History  Each time a content item is saved, a new version of that content is created. If the content item was published, the previously published version is archived. Each version of the content is available for preview, editing, and publishing through the  Version History  menu. To access Version History for content, you can follow these steps: From the  Tree View  or  List View  tabs, click on the   three-dotted menu located next to the content item you wish to view. This should reveal a menu of options to select from. Or, from the "Edit Content" screen, click the Actions button to reveal a menu of options. Select the  Version History  option from the menu of options. Or, from the front-end editing view, select the Version History icon button from the front-end toolbar. The  Version History  screen should appear. From the  Version History  screen, select the three-dot menu next to a specific version of content to Edit, Preview, Delete, or view the Audit Trail. From the  Version History  screen, you can also click the Actions button to reveal options to Clear Version History, Delete the content item altogether, and edit the Permissions of the content item.   Compare Versions  With Mura CMS, you can compare different versions of a content item, to visually see what has changed to various fields. You can compare versions of content from either the  Version History  screen, or the  Audit Trail  screen. Follow the steps below to compare different versions of a content item. On both the  Version History  and  Audit Trail  screens, there are two columns of radio buttons located under a  Compare  button. Select a radio button in one column to indicate the version you want to compare to, and another radio button in the other column to indicate the version you wish to compare from. It really doesn't matter which column you select for either one, as long as the radio buttons in each column are selecting different content versions, Mura will be able to display the differences between the two selected versions. Next, click the Compare button above the two columns of radio buttons. The  Version History Comparison: Code & Attribute Diff  screen should now appear, revealing which fields have been changed. The newer version of content will be highlighted in light-green and underlined, while old information will be highlighted in pink with a strikethrough. Roll Back to a Prior Version  Using the  Version History  feature of Mura CMS, you can roll back content items to a prior version quickly and easily. How to Roll Back to a Prior Version Go to the  Version History  screen of the content item you wish to roll back. Select the specific version of the content item you wish to re-publish. At this point, you can optionally choose to make any desired to edits to the content item. When ready, select your desired publishing option (e.g., Publish, Save to Change Set, etc.) You have now created a brand new version of the content item, and successfully rolled back to a prior version. Please keep in mind Mura will still maintain the original version of the content item you wished to roll back to, as well as the newly published content item, as you could have made some additional changes prior to publishing it. Audit Trail  An  Audit Trail  reveals the individual history of each specific version of content. While similar in nature to the Version History, the primary difference is that content managers can determine which version was used as its source. To view an Audit Trail, go to the  Version History  of your desired content item, and follow the steps below. From the  Version History  screen, select the three-dot menu icon next to the content version you wish to investigate. A menu of options should appear, including an option labelled  Audit Trail . If you  hover  (don't click!) over the  Audit Trail  label, the specific version of content you're hovering over will be highlighted, as well as the versions that it derived from. In the example below, hovering over Audit Trail of the most recent draft reveals the version from 02/10/2017 was used as its source, and the version before that was used at  its  source, and so on. If you click on the  Audit Trail  menu option, you should be taken to the  Audit Trail  screen, revealing the specific history of that particular version of content you're currently working with, thus eliminating any unrelated versions from view. Export Content  Mura CMS offers the capability to export content from your website. You can choose to export your entire site, a section of your site, or even just a page. This is useful for creating a simple backup of a small section of your site, or if you want to move/copy a section of your website to a completely different Mura CMS website. How to Export Content Log in to the back-end administration area of the website. Select the content item representing either the page or section you wish to export, and edit the content item. From the  Edit Content  screen, click the  Actions  button, and select  Export . If the content item you've selected has any children (sub-pages, files, etc.), you should be presented with the  Export Content  screen. If you're exporting a single content item without children, this screen will not appear. You may choose to export either the  Children Only , or  This Content Item and Children . When making your selection, you may wish to consider how you will be using the content you are exporting. For example, if you want to include the "News" landing page in addition to its children, then select "This Content Item and Children." Once you've made your selection, click  Export Content . From the Alert dialog window, click  Yes  to confirm your selection. Once Mura CMS bundles the content together for you, a prompt to save the export file as a .ZIP document will appear. You can choose to save it wherever you wish. The exported file is now ready for archival and/or ready to be imported into another Mura CMS site. Import Content  Mura CMS offers the ability to import content that has been exported from Mura CMS, quickly and easily. Please review the steps from the  Export Content  section before proceeding. How to Import Content From the back-end administration area of Mura, select a content item to edit, where you would like to import the new content. For example, if you would like to import the entire "News" section, you could choose to edit the "Home" page. From the  Edit Content  screen, go to  Actions > Import . You should be taken to the  Import Content  screen. Click  Choose File  or Browse to select the Mura CMS created/exported .ZIP file you wish to import. Select your desired  Content Status  for the imported content. Published The content will be visible by users visiting the front-end, public facing view of your website. Draft The content will not display on the front-end, public facing view of your website. Save to Change Set When you select  Save to Change Set , the  Change Set Name  field will appear. Simply enter your desired Change Set Name. Click  Import . Once completed, the imported content should now appear. Components  Components are reusable content objects that can be shared across multiple pages or sections within your site. For example, maybe you have an announcement you want to share across your website such as "Closed for Holidays." Without components, you would most likely have to contact a developer, then give the developer a listing of areas you want the notice to appear. However, in this scenario, you most likely would not be able to edit the content of the notice or control whether or not it is on display, etc. Utilizing components shifts that control back to the content manager. You could create a notice, and choose which page(s) and/or section(s) of the site you would like it to appear, all using a single interface. This means that although the content may span several pages or sections of the site, you can simply edit the component once and it will update  all  instances throughout the entire site.  Another function of components is to use them as content templates so that non-technical users can recreate a visual style for a specific type of content without having to start from scratch. How to Create a Component From the back-end administration area, go to the  Content  section, select the  Tree View  tab, then select the  Components  button. Click the three-dotted menu beside  Components  and select  Add Content . The  Select Content Type  dialog window should appear.  Component The  Component  option is the most common selection used. Using this option will take you to the Create Component screen, as identified in the next step. Folder The  Folder  option is available so that you can create groupings of Components. This is useful for grouping components logically and also for keeping components used by similar groups of users together so you only need to set permissions on the Folder, versus having to modify permissions for each and every component. The  Create Component  screen should appear. Basic Tab Title (required) Enter a title for the component. Content Enter your desired content/body. Where would you like to use this Component? Content If enabled, the component will appear on the CKEditor's "Insert Component" options list when editing Content. Components If enabled, the component will appear on the CKEditor's "Insert Component" option list when editing Components. Forms If enabled, the component will appear on the CKEditor's "Insert Component" option list when editing Forms. Publishing Tab   Display This field controls whether or not the component will be visible to users via the public, front-end view of your site. Yes If Yes, then the component will be visible to users via the public, front-end view of your site. No If No, the component will not be visible to users via the public, front-end view of your site. Per Schedule You may specify a schedule for the component to display, including the frequency of the display such as daily, weekly, monthly, etc. and when the component should stop displaying, if ever. Content Parent You may use this field to move a component to be grouped under another component or Folder of components. See the  Selecting New Parent  section for more details and instructions. Notify For Review When enabled,  Send to  and  Message  fields will appear. Send to You may select one or more users to receive an email notification after saving or publishing the component. To select more than one person, use  + click  (on a PC) or  + click  (on a Mac). Message Text entered here will accompany a link to view the component in the email notification. Add Notes This field allows you to enter informational notes which can be shared amongst content managers, without it appearing anywhere on the public, front-end view of the site. Categories Tab The Categories tab is where you manage a component's Categories. To learn more about  Categories , including how to create/manage categories, and categorize content, visit the  Categories  section. Tags Tab The  Tags  tab is where you manage a component's Tags. Visit the  Tags  section to learn more about Mura Tags. Advanced Tab Content ID This is a unique identifier of the component and typically used by developers. Layout Template You may optionally apply a layout template to your component by selecting it from the list of available options. Locking Mura offers the ability to "lock" components so they will not be accidentally deleted by content managers. Lock Node If enabled, content managers will not be able to delete the component. After completing the form, select your desired publishing option to save your component. To add the component to a page or section of your site, please visit the  Component Display Object Type  section. Forms  Forms allow you to collect information from visitors to your website for various purposes. For example, you could create a "Contact Us" form, or a form to collect data when someone wants to attend an event you might be hosting. In addition to collecting and storing form data, Mura can also send email notifications to your desired email address(es). How to Create/Edit a Form  From the back-end administration area, go to the  Content  section, select the  Tree View  tab, then select the  Forms  button. Click the three-dotted menu beside  Forms  and select  Add Content . The  Select Content Type  dialog window should appear. Form The  Form  option is the most common selection used. Using this option will offer you the ability to create a form using a special user interface, specifically designed with form creation in mind. Simple Form The  Simple Form  option is typically used by developers so they have a way to include their own custom designed form, and yet allow the data to be collected and managed by Mura. Folder The  Folder  option is available so that you can create groupings of Forms. This is useful for grouping forms logically and also for keeping forms used by similar groups of users together so you only need to set permissions on the Folder, versus having to modify permissions for each and every form. The  Create Form  screen should appear. Basic Tab Title (required) Enter a title for the form. Content Toolbar This is where the actual content of the form is created. Across the top of the Content User Interface (UI) is a  toolbar  which allows you to add/create form elements. To rearrange form elements, simply click, drag, and then drop to your desired order. Form Button You may optionally click the " Form " button to enter specific information used when the form data is emailed to any addresses listed under "Send data to email address". You can also change the label of the Submit button, if desired here. Section Button If you select the " Section " button, it will create a grouping for form fields to belong to. Any fields listed directly below it will appear in that section. For developers, this merely creates a HTML "fieldset" element. Click on the " New Section " element itself to reveal options in the main window. Any text entered in the  Label  field will automatically update the information elsewhere. For example, if you enter "Your Information" into the Label field, "Your Information" will also appear at the top of the section, and in the column of form fields. Text Field The Text Field is a commonly used form field used to collect simple data such as names, email addresses, phone numbers, etc. Click the " New Text Field " element itself in the left column to reveal options in the main window. Any text you enter in the Label field will automatically update the name and other attributes just as it did in the previous "Section" button. This feature applies to all other form field types as well.  Basic Tab Label Data entered here will appear with the form field so end-users know what to enter into the form field. Name This field is primarily for developers, and the text here will become the "name" attribute of the form field itself. Value You may enter a default value to be displayed when the form renders. Advanced Tab Size Primarily used by developers, data entered here will be used for the form field's "size" attribute. CSS ID Primarily used by developers, data entered here will be used for the "ID" attribute of the form field. CSS Class Primarily used by developers, you may enter a CSS class to be applied to the "class" attribute of the form field. Wrapper Class Primarily used by developers, you may enter a CSS class to be applied to the container in which the form field is placed within. Placeholder Data entered here will appear inside the form field, but is only "temporary" and will not be used if the form is submitted. For developers, this is the "placeholder" attribute of the form field. Tool Tip Data entered here will be applied to the "title" attribute of the form field. Validation Tab Validation Type None No validation will be applied to the form field. Numeric Validates the data entered in the form field is numeric. If it does not validate, an error message will be displayed. Date Validates the data entered in the form field is a valid date format. If it does not validate, an error message will be displayed. Email Validates the data entered in the form field is a valid email address format. It does not verify whether or not the email address actually exists. If it does not validate, an error message will be displayed. Regex This field is reserved for experienced developers. Enter a JavaScript regular expression that should be invoked when validating the form field here. If it does not validate, an error message will be displayed. Validation Regex If the  Validation Type  is set to " Regex ", enter a JavaScript regular express to be used here. Validate Message Text entered here will be displayed to end-users if the form field is required, or does not pass validation rules. Required? If enabled, the  Validate Message  will be displayed to end-users who do not complete the form field. Text Area The  Text Area  form field represents a multi-line plain-text editing control. Hidden Field The  Hidden  form field does not show on the page. This field is typically used by developers to capture additional, or dynamic data such as the name of the page the form is being used on. Radio Button Group The  Radio Button Group  is a listing of many choices, where end-users may only select one. Source Tab Source Select Menu Create New Selecting  Create New , and clicking the " Update " button will create a new  List  tab. For each option, enter a  Label  to be displayed to the end-user, and a  Value  to be stored in the database to indicate which option the user selected. To indicate a default selection, click the radio button next to your desired default row. Custom Display Object Primarily used by developers, you may enter the name of a Custom Display Object to use as the source for options. Custom Object Primarily used by developers, you may enter the name of a Custom Object to use as the source for options.  Code example > Remote Source Primarily used by developers, you may enter a Remote Source to use as the source for options.  Code example > Checkboxes A  Checkbox  allows you to select a single value for submission in a form (or not). Source Tab See the  Source Tab  section in the  Radio Button Groups  section above. Dropdown Menu The  Dropdown Menu  allows you to create a select menu of options for end-users pick from. Source Tab See the  Source Tab  section in the  Radio Button Groups  section above. File Upload Field The  File Upload Field  creates a form field to enable end-users the ability to attach files to their form submission. Note:  Allowing the general public to upload files to your website may introduce a security risk. Please consult an experienced and qualified developer before using this feature. Block of Static Text The  Block of Static Text  button allows you to add text within the form itself. This is especially useful when you need to add instructions within the form. Nested Form The Nest Form button enables you to nest another Mura form within the form itself. This is useful when you have multiple forms that may contain duplicate information to be collected such as First Name, Last Name, Email, etc. You could create a separate form with only those fields, and then insert the form into the other forms requiring that data. Page In the far left column of the Content UI, you can create and/or delete additional "pages" of form fields. This is useful for long forms, and when you wish to display only a subset of form fields to your end-users to reduce the anxiety of completing a long form all at once. Click the Plus sign to add a new page. To delete a page, select the page you wish to delete, then click the circle with an "x" in the middle of it to remove the page. Confirmation Message Text entered here will appear for users after they successfully complete and submit the form. This is a great place to add information such as your organization's phone number, business hours, etc. Send data to email address (Separate multiple email addresses by comma) Enter a comma-delimited list of email addresses of where you would like email notifications sent to. Many organizations use a group email address of some kind for this field such as sales@yourdomain.com instead of entering individual's email addresses here. Publishing Tab Display This field controls whether or not the form will be visible to users via the public, front-end view of your site. Yes If Yes, then the form will be visible to users via the public, front-end view of your site. No If No, the form will not be visible to users via the public, front-end view of your site. Per Schedule You may specify a schedule for the form to display, including the frequency of the display such as daily, weekly, monthly, etc. and when the form should stop displaying, if ever. Content Parent You may use this field to move a form to be grouped under another form or Folder of forms. See the  Selecting New Parent  section for more details and instructions. Notify For Review When enabled,  Send to  and  Message  fields will appear. Send to You may select one or more users to receive an email notification after saving or publishing the form. To select more than one person, use  + click  (on a PC) or  + click  (on a Mac). Message Text entered here will accompany a link to view the form in the email notification. Add Notes This field allows you to enter informational notes which can be shared amongst content managers, without it appearing anywhere on the public, front-end view of the site. Categories Tab The Categories tab is where you manage a form's Categories. To learn more about  Categories , including how to create/manage categories, and categorize content, visit the  Categories  section. Tags Tab The  Tags  tab is where you manage a forms's Tags. Visit the  Tags  section to learn more about Mura Tags. Advanced Tab Content ID This is a unique identifier of the form and typically used by developers. Caching Mura uses "caching" to store data in memory, so future requests for that data can be served faster. Exclude from Site Cache If enabled, Mura will  not  include the form in Mura's data cache. Locking Mura offers the ability to "lock" forms so they will not be accidentally deleted by content managers. Lock Node If enabled, content managers will not be able to delete the form. After completing the form, select your desired publishing option to save your form. To add the form to a page or section of your site, please visit the  Form Display Object Type  section. Managing Form Data  Whenever a Mura-created form has been submitted, the information is captured and stored in Mura's database. With Mura, you can view form data, and even export the data for archival purposes and/or to import it into a third-party system such as a Customer Relationship Management (CRM) system. How to View and/or Download Form Data From the back-end administration area, go to  Content , select the  Tree View  tab, click the  Forms  button. Click the three-dot menu next to the row of the form you wish to view/download data for, and select  Form Data. Or,  select the form you wish to view/download data for. Then, click the  Form Data  button. You should see the  Form Data  Screen. From the  Form Data  screen, you can see the  Total Records Available  at the top of the screen. By default, the From field is pre-populated with the oldest form submission stored in the database, and the To field is pre-populated with the most recent form submission stored in the database. You may change these to your desired time range to limit the results to be returned. You can also choose which form field you would like to sort the results by and the sort direction. You may also perform a  Keyword Search  of form submissions by specific form fields. To view the data on the screen, click the  View Data  button. The form data results should now appear on the screen. You can edit and/or view more details of each result by clicking the three-dot menu and selecting Edit. From the form detail screen, you can make edits to your desired form fields, then Update or even Delete the form entry entirely. To download for results, from the  Form Data  screen, click the  Download  button. You should be prompted to save the file. The data will be exported as a .CSV (comm-separated values) file. This makes it easy to open in popular spreadsheet software programs, and even import the data into a third-party system such as a Customer Relationship Management (CRM) tool. You can also choose which form fields to display and/or export. To do so, click the  Edit Display  button at the top of the Form Data screen. You should now see a screen with a number of configuration options. Under the  Available Fields  menu, you can select a field you wish to display, then click the double right arrows pointing to the  Summary Display Fields , or if you wish to modify the display of the "form detail" screen, you can select the double right arrows under the  Detail Display Fields . To remove a form field from the display, simply click the form item in the display, and then click the double left arrows and it will be removed. You can also control the order of the display fields by selecting a field, and then clicking the  Up  or  Down  button, as desired. If you leave the Summary Display Fields empty or blank, by default, Mura will display and/or export all form fields. Once you've made your desired changes, click  Update  to save the new displays. Next time you either View Data or Download, you will only see the form fields selected, plus the default "Date/Time Entered" form field, which is created by Mura for all form entries. Collections  Collections are essentially indexes of Mura CMS content items based on pre-defined search criteria and/or filters. For example, Mura CMS can create an index of content items which have been flagged as "Featured" and categorized as "Domestic News" where the content resides under either the Blog or News sections of your site. You can control the maximum number of items you wish to display and more. You can also choose to broadcast Collections as RSS feeds ( http://en.wikipedia.org/wiki/RSS ), making it easy for visitors, or even other web sites, to consume information from your site and bring visitors back for details. In addition to creating Collections of Mura content items, Mura CMS can also consume  external  RSS feeds and display pieces of that information on your site using the  Collection display object , and "Remote Feed" as the Content Source. Local Indexes  A  Local Index  is essentially a collection of content which has been indexed and aggregated from either the entire site, or specified areas of the site, based on desired filter criteria. Once created, these Local Indexes can be used as  Collection display objects  in one or more areas of the site. These built-in, customizable  Collection display objects  are generally a listing of content items which typically include the title, associated image, summary text, official release date, author, and a hyperlink to the full version of the page. Mura CMS also gives you the ability to publish a Local Index as a RSS feed ( http://en.wikipedia.org/wiki/RSS ) to syndicate content automatically. Collections are managed via the back-end administration area of Mura CMS. From the admin navigation menu, select  Collections  to view the  Collections  screen. How to Create a Local Index From the Collections screen, click the  Add Local Index  button. The  Create Local Index  screen should appear. Take a look at the default settings. These are the default "filters" that control which content items get indexed. Basic Tab Name (required) Enter a name for the Collection. Sections Pulled From You may optionally select zero, one, or more section(s) to narrow down where you want content items to be searched for. If you leave this blank, Mura CMS will automatically search the entire site. Follow the steps below to apply one or more section(s) to the Local Index: Click the "Select Section" button to review a search box. Enter your desired section title (e.g., "News"), then click the spyglass button. Results will be displayed below the search box. Click the plus sign next to the section you would like to include in the Local Index. Once you click the plus sign icon, the selected section should then appear under the  Section  area. If you select the wrong section, click the trash can icon to remove it. Repeat these steps for each section you would like to include in the Local Index. Sort By You can sort your Local Index by a variety of fields, or explicitly "Do Not Apply Sort". Last Update Official Release Date Start Date/Time (e.g., Calendar) Navigation Title Long Title Rating Created Local Manual Order Random Do Not Apply Sort Sort Direction Once you choose your  Sort By  option, you can choose to sort the Local Index by  Ascending  or  Descending . Max Items Limit the number of content items returned by making a selection here. Items Per Page Limit the number of content items to be displayed on the page at a time. If more content items are returned than the number selected here, pagination will display. Include features only? If Yes, Mura will only include content items where the "Feature in this section" field has been enabled. If No (default), Mura will ignore this field. Include navigation items only? If Yes, Mura will only include content items where the "Include in Site Navigation" field has been enabled. If No (default), Mura will ignore this field. Include items that have been excluded from site search? If Yes, Mura will include items that have "Exclude from Site Search" enabled on the Publishing tab. If No (default), Mura will not include items that have "Exclude from Site Search" enabled on the Publishing tab. Lock name? If Yes, Mura will prevent the "Name" of the Collection from being changed, rendering the field as a read-only field. This is useful for developers who reference the specific Collection via code. If No (default), the "Name" of the Collection is editable. Categories Tab Category Filters Select any desired categories you wish content items to match in order to be included in the Collection. Match All Selected Category Filters If  Yes , then content items must be categorized as all selected/applied Category Filters to be included in the Collection. If  No , then content items can be categorized as any of the selected/applied Category Filters to be included in the Collection. Advanced Filters Tab Choose Advanced Filters This section allows you to apply filters based on various form fields, including custom attributes created using Class Extensions. You can then filter based on a number of options pertaining to that field and criteria. For example, whether or not a field such as Credits "Contains" a particular value, as shown in the example above. RSS Tab Most information on this tab is used by experienced developers and/or site administrators. Description Text entered here will be included in the description node of the XML file automatically created by Mura CMS so RSS parsers can display the information to their users. Allow HTML in item descriptions? If Yes, HTML will be allowed in the item descriptions. If No, HTML will not be allowed in the item descriptions, and will be parsed out when being broadcast. Is this a Public Feed? If Yes, a link to the collection's RSS feed can be included in the layout templates by your developers. If No, a public link will not be generated. Version Select your desired format to broadcast the RSS feed in. Options include  RSS 2.0 , and  RSS 0.920 . Language You may choose to enter a specific language and country code to be included in the RSS feed. Access: Restrict Access to Specific Site Member Group(s)? If enabled, you can choose which group(s) you wish to allow access. Once you have applied all of your desired filters and criteria, click  Add  to save the new Local Index. Your Local Index should appear in the list of available  Local Indexes . Whenever you create or edit a Local Index, you should click the three-dot menu to the left of your Local Index, and select  View RSS  and examine the results. Depending on your browser's capabilities, you should be able to view either an XML output or nicely formatted output of the Local Index displaying the content items which match your desired filters. If you don't see any items listed, it doesn't mean you did anything wrong, it only means there are no content items which match all of the selected filters you've applied when creating/editing your Local Index. Remote Feeds  A  Remote Feed  is essentially a collection of content from an external website. This works by using an external website's  RSS feed . You can also choose to import the content directly into Mura, and then make modifications to the content items as you wish. How to Create a Remote Feed From the Collections screen, click the  Add Remote Feed  button. The  Create Remote Feed  screen should appear. Basic Tab Name (required) Enter a name for the Collection. URL (required) Enter the URL of the RSS feed from the external website. For example,  http://feeds.bbci.co.uk/news/world/rss.xml Is this Feed Active? If Yes, the feed will appear as an option for content managers when creating Collection display objects. If No, the feed will not appear as an option for content managers when creating Collection display objects. Is this a Public Feed? If Yes, a link to the RSS feed can be included in the layout templates by your developers. If No, a public link will not be generated. Max Items Select the default number of items you wish to consume/import. Version In order to properly consume the content, it's extremely helpful to indicate the external RSS feed's version/format. Options include RSS 0.920, RSS 2.0, and Atom. Categories Tab Category Filters Select any desired categories you wish content items to match in order to be included in the Collection. Import Location Tab Import Location You may optionally choose to import the external content items into your own website. Select the desired section of the site you wish the content items to be imported to. Auto Import If Yes, Mura will periodically check the external feed for new content items and import them if found. If No, Mura will not import new content items automatically. If you wish to import new content items, you can select the three-dot menu of the Remote Feed, and select "Import" when you wish to do so. Click the  Add  button when finished to save the new Remote Feed. Your Remote Feed should appear in the list of available Remote Feeds. Whenever you create or edit a Remote Feed, you should click the three-dot menu to the left of your Remote Feed, and select  View Feed  and examine the results. Depending on your browser's capabilities, you should be able to view either an XML output or nicely formatted output of the Remote Feed displaying the content items which match your settings. If you don't see any items listed, you may want to verify your settings are entered correctly, and that content items match your desired categories, if selected.   Managing Comments  As you have seen in the  Display Object Types > System  section, Mura offers a convenient way for content managers to collect comments from visitors to their site on various pages and sections of your site. However, the more popular your site and content become, the more comments will begin pouring in. The Comments Manager is the place to go to manage comments submitted on your site. If your organization does not allow comments to be posted without approval, you'll be able to approve or unapprove comments. In addition to that, you can delete comments and even flag comments as spam. These actions can also be done in bulk, meaning that you can delete or approve multiple comments at once. This is extremely useful for those times a spammer or bot targets your site and manages to get several comments submitted, in spite of the safeguards to combat them. Just in case you're wondering, even though Mura includes some anti-spam measures, and your development team may have even tweaked some of those settings, spam can, and will get through. To learn how to enable and/or disable the Comment Manager, force comments to go through an approval process, or apply permission to the Comments Manager, please visit the  Comments Permissions section . How to Manage Comments via the Front-End, Public Facing Side of Your Site Navigate to a content item where comments have been submitted, and scroll to the comments section. For example, a blog or news article. Mura offers the ability for visitors to your site to help identify spam by including a "Flag as Spam" link. When logged into Mura, additional options will appear to assist in managing each comment. For example, you should be able to see additional buttons that appear in the top right area of each comment. If you do not allow comments to be posted without approval, comments pending approval will appear with a red-tinted background, and an additional button to approve the comment. If you are logged out, comments pending approval will not appear. If you wish to delete a comment, simply click the delete button next to any comment, then click "OK" on the confirm dialog box when it appears. How to Manage Comments via the Back-End Administration Area Managing comments from the back-end administration area is much easier on sites that receive a fair number of comments. As you'll see in the steps below, you can perform bulk operations on comments such as approving, deleting, or flagging them as spam. From the back-end administration area of Mura, click  Comments  on the main navigation. From the  Comments  screen, you can search comments by using the  Search for Comments  field. You can also filter comments by using the  Comment Status  select menu, then clicking the spyglass next to Search for Comments. Or, you can filter comments by selecting your desired  Comment Date Range , then clicking the spyglass next to Search for Comments. You may also filter comments based on  Available Categories , then clicking the spyglass next to Search for Comments. Click the three-dot menu next to a comment in the list, to reveal a menu of options. Comments Select this option to open a dialog window to delete, approve, unapprove, or flag the comment as spam. If you flag the comment as spam, it will not appear on the front-end, public facing side of your site. Click the icon next to the title of the content item that was commented on, and a new tab should open, with the URL of the content item as seen from the front-end, public facing view of your site. If comments preceded the comment you're currently viewing, a button will appear to provide you a way to view the preceding comments. Conversely, if any comments have been posted after the comment you're currently viewing, another button will appear below the currently viewed comment to view additional comments. View If the "View" option appears, it will link to the URL the user entered when submitting their comment. For example, many commenters enter the URL of their personal or business website. Email Select this option to launch your default email program to send an email to the submitter. If you click the Date, Time, User, or Comment itself, the behavior is the same as clicking the three-dot menu next to the comment, and selecting the Comments option, as described above. To perform bulk operations such as Approve, Spam, Delete, select the checkbox next to each comment you wish to include in the operation. You may also click the checkmark at the top of the column to "select all" or "deselect all." Then, click the " Mark As " button, and select your desired operation. Lastly, comments that have been "deleted" will still appear in the back-end administrator. If you wish to permanently delete comments that have been marked as deleted, you may use the  Purge Deleted Comments  button to do so. Summary  In this section, we covered many of Mura's advanced features such as the fields of each of the available Tabs when editing content items, Publishing Options, Components, Forms, and Collections. From creating categories, tags, and related content, to creating forms and managing data, you should be well prepared to handle working with the more advanced content features of Mura.v Groups, Users, and Access Control Credit:  Blueriver Permissions  When it comes to permissions in Mura CMS, the most important thing to keep in mind is that all permissions are "group-based." So, instead of thinking about individual users, it's better to think in terms of groups. This concept applies whether we are talking about restricting access to a specific section of your site, or we are talking about "editing" privileges for various groups throughout your website. As you'll see, you can always create a group with only one individual assigned to it, if you really need to only allow one person access to something in particular. That said, Mura CMS has included some very powerful features to assist you in setting up your desired permissions for various sections of the administration area, including the rights and privileges each group has when it comes to creating and managing content, or even accessing different areas of the front-end, public-facing side of your site.   Author vs. Editor Roles  Before you begin creating and granting/limiting "editing" privileges to any groups, it is important to understand the differences between the two primary "roles" within Mura CMS:  Editor  and  Author . Editor Groups granted " Editor " permissions are able to " write " content,  as well as  " publish " content. This means they can create new content items, update existing content items, delete content items, and even publish content items (or, make them "live"), but only within the section(s) of the site where they have been granted these privileges. Author Groups granted " Author " permissions can  only  " write " content. This means they can create new content items, and update existing content items. However, they are unable to publish or delete content items. In addition to these primary roles, you can also grant " Read Only " access, or even explicitly " Deny " access to any group(s) throughout the administration area. You should keep these roles in mind when creating your groups. For example, you may have a section of your site where you want members of your "Marketing" group to be able to edit the content. However, you may not want everyone in the Marketing department to be able to have "Editor" permissions. So, instead of having a group called "Marketing", you could have a group of "Marketing Editors" and a group of "Marketing Authors", so you can segment your department to accommodate your needs.   Creating & Managing Groups  All permissions in Mura are group-based. As such, it's important to take time to think about the structure of your site, and how you wish to enable and/or restrict access throughout it. Also, as discussed in the " Author vs. Editor Roles " section, you should consider these roles/privileges when creating your groups. There are two main "pools" of groups within Mura:  System Groups , and  Member Groups . The key difference between these pools of groups is System Groups  have access  to the back-end administration area of Mura, and Member Groups  do not . This doesn't mean Member Groups cannot edit content, it simply means users of Member Groups cannot log in to the back-end administration area, unless they are also a member of a System Group. This may sound somewhat confusing if you're new to managing groups and users. However, be patient, read through this entire section, and you will find Mura can accommodate some of the most complicated scenarios you can think of with ease. How to Access Users & Groups From the back-end administration area of Mura, click  Users  from the primary navigation to reveal an additional set of menu items. To manage users, select  Users . To manage groups, select  Groups . You can also select  Add User  to add a new user, or  Add Group , to add a new group. To  delete  a group, from the  Users & Groups  screen, select the three-dot menu on the row of the group you wish to delete, and click  Delete . You should be prompted with an  Alert  dialog box. To confirm, select  OK . To cancel, click  Cancel . System Groups  All  System Groups  have access to the back-end administration area of Mura. So, if you need to allow a user access to the back-end administration area, they must be a member of a System Group. How to Access System Groups From the back-end administration area of Mura, select  Users  from the main navigation, then  Groups , and click the  System Groups  tab. By default, there is a single  System Group  labeled  Admin . This group is required and cannot be deleted. Admin System Group  The  Admin   System Group  is created when Mura is first installed. You can't change the name, or delete it. Any users who are members of this group will automatically be granted the ability to: Create and Manage System Groups and Member Groups Create and Manage Users Manage Permissions Write and Publish Content Access most areas of the administrator within the site And more! So, as you can see, members of the Admin System Group have quite a bit of access and privileges. Only users who have been granted " Super Admin User " privileges have more power than members of the Admin System Group. We'll discuss  "Super Admin Users" in another section . How to Create/Manage a System Group  You will most likely want to create a number of System Groups to accommodate your organization's desires for enabling and/or restricting access to specific sections of your site.  Before creating any groups, it is a good idea of to have a clear picture of the sections and/or pages each group will be responsible for, and the permissions and roles you wish to grant them. Try not to think of the individual users themselves. Instead, think in terms of the group, even if the group may only contain one user. Follow the steps below to create/manage a System Group. From the back-end administration area of Mura, select  Users  from the main navigation, then click  Add Group . Complete the information on the  Group Maintenance Form : Group Type Select  System Group Group Name Enter a name for the group. For example, "Marketing". Group Email If your organization has an email address that includes all users of the group, you may enter it here. For example, "marketing@yourdomain.com". Content UI Assignments You may optionally restrict which tab(s) the group has access to when editing content. To select more than one tab assignment, + Click on a PC, or + Click on a Mac. Click the  Add  or  Update  button when finished to save your changes. Your new/updated group should be visible in the listing of  System Groups . Repeat these steps for each System Group you wish to add. Member Groups  Member Groups do not have access to the back-end administration area of Mura. The primary use of Member Groups is to provide segmented access to specific areas of your site. In addition to restricting access to specific areas of your site to certain Member Groups, you can also grant editing privileges to one or more Member Groups. This would allow those users the ability to only edit content from the front-end, public facing side of your site. How to Access Member Groups From the back-end administration area of Mura, select  Users  from the main navigation, then  Groups , and click the  Member Groups  tab. There are no  Member Groups  created for you by default. How to Create/Manage a Member Group From the back-end administration area of Mura, select  Users  from the main navigation, then click  Add Group . Complete the information on the  Group Maintenance Form : Group Type Select  Member Group Group Name Enter a name for the group. For example, "Employees" or "Board Members". Group Email If your organization has an email address that includes all users of the group, you may enter it here. For example, "employees@yourdomain.com". Content UI Assignments You may optionally restrict which tab(s) the group would have access to, if you are going to allow the group editing permissions. To select more than one tab assignment, + Click on a PC, or + Click on a Mac. Click the  Add  or  Update  button when finished to save your changes. Your new/updated group should be visible in the listing of  Member Groups . Repeat these steps for each  Member Group  you wish to add. How to Restrict Access to Content One of the primary uses of Member Groups is to have a way to restrict access to various sections of your site to specific groups. For example, you might have a "Members Only" section of your site, where all users are required to log in. Then, from there, you could have additional sections of the site restricted to very specific groups, such as an "intranet" area for employees, and a "board member" area for board members. Restricting access to a page, or section of your site, only hides the "body" area of your page. If a user is not logged in, by default, Mura will display the "Summary" field and a login screen. Hence, we do not recommend entering any sensitive information in the "Summary" field, unless you have been instructed to do so due to modifications made to Mura by your development team. To restrict access to your entire site, a content item, or a specific section of your site, and follow the steps below. Navigate to the page or section of your site where you wish to restrict access to, and edit it. Select the  Publishing  tab. Scroll to the field labeled " Restrict Access to Specific Group(s)? " Note : This field will only appear if  Extranet (Password Protection)  is enabled via the  Site Settings  >  Edit Settings  >  Modules  tab. You may  + click  (via PC) or  + click  (via Mac) to select more than one group. Note : A commonly asked question is whether or not it is possible to hide navigational links to "restricted" pages if a user is not logged in. The short answer is no. However, only the top-most link would be visible, and no links to child content would be generated. This is why we typically recommend creating a "Members Only" section of your site, and then enforcing more specific restrictions to content beneath that. Managing Group Members  To manage a group's members, follow the steps below. From the back-end administration area of Mura, click  Users  from the primary navigation to reveal an additional set of menu items, then select  Groups . From the  Users & Groups  screen, select the three-dot menu in the row of your desired group, and click  Members . You should be taken to the  Group Maintenance Form  screen, and see a listing of the group's users/members. If you click the three-dot menu in the row of any user you wish to modify, you will be presented with a menu of options to  Edit  the user,  Remove User From Group , or even  Delete  the user entirely. To assign a member to a group, see the  Add/Edit a User section , and review the  Group Memberships Tab  information. Creating & Managing Users  The first thing to keep in mind when working with users in Mura is all permissions in Mura are group-based. So, if you haven't already done so, please be sure to read the section on  Creating & Managing Groups  before continuing. Once you've  created your desired groups , you're ready to begin adding users and assigning them to the various groups you've established. Users may belong to as many groups as you wish, and may belong to both  System Groups  and  Member Groups  under the same user account. In other words, you shouldn't have to create multiple user accounts for the same individual. How to Access & Find Users From the back-end administration area of Mura, select  Users  from the main navigation, then  Users . The  Site Members  tab is enabled by default and lists users who belong to the  Site Members  pool of users.  Site Members  do not have access the back-end administration area of Mura. Click the  System Users  tab to view users who belong to the  System Users  pool of users. In a default installation of Mura, there is one user, created automatically, named " Admin User ." However, during the installation process, the name and email address could have been changed to something else. From either tab, you have the ability to  Download  a list of users in .CSV format, by clicking the  Download  button above the listing of users. From either tab, you also have the ability to view a listing of users who have not been assigned to any specific group, by clicking the  View Unassigned Only  button. You can also easily identify "unassigned users" by the exclamation mark ("!") located directly to the left of the user's name. A "star" next to a user's name indicates they are a  Super User . See the  Super User section  for more information. Search  for users using the search box, located above the tabbed menu. Click the  Advanced  button, located next to the search box, to view the  Advanced User Search  screen. On the  Advanced User Search  screen, you can narrow your search by applying additional filters such as selecting a specific field, and desired criteria, then clicking the  Search  button. Results appear below the form, and are tabbed so you can locate both Site Members and System Users who match your desired search criteria.   Add/Edit a User  Follow the steps below to add/edit a User in Mura. From the back-end administration area of Mura, select  Users , then  Add User . Or, select an existing user from your list of users to edit. You should be taken to the User Maintenance Form. Basic Tab First Name (required) Enter the user's First Name. Last Name (required) Enter the user's Last Name Company Enter the user's Company Job Title Enter the user's Job Title Email (required) Enter the user's Email address Mobile Phone Enter the user's Mobile Phone number Username (required) Enter a Username for the user to use when they log into Mura Password (required) Enter a Password for the user to use when they log into Mura. They will be able to change it after they log in. Confirm Password (required) Re-enter the Password entered in the previous form field Profile Image You may optionally upload a profile photo to use for the user. If you wish to delete a  Profile Image  (if one exists), select the  Delete  checkbox, then click  Update . Click the image (if one exists), and you will be taken to the Image Details screen where you can Adjust Image Orientation, and adjust the crop areas of any predefined image sizes. Address Information Tab Street Address 1 You may enter a Street Address for the location Street Address 2 Some addresses require a second line, and if so, you may enter that information here City You may enter a City for the location State You may enter a State for the location Zip You may enter a Zip Code for the location Country You may enter a Country for the location Phone You may enter a Phone number for the location Fax You may enter a Fax number for the location Website (Including HTTP://) You may enter a URL for the location Email You may enter a valid Email address for the location Hours You may enter the hours for the location If editing an existing User, you may edit any existing address(es), or add additional addresses. Group Memberships Tab User Type Site Member If  Site Member  is selected, the User will not be able to log in to the back-end administration area of Mura.  Site Members  may only belong to " Member Groups ." System User If  System User  is selected, the User will be able to log in to the back-end administration area of Mura. System Users may belong to both " Member Groups " and " System Groups ." System Groups If  User Type  is set to  System User , a listing of available  System Groups  will appear. You may assign the User to your desired groups here. Member Groups This section contains a listing of available  Member Groups . You may assign the User to any desired groups here. Interests Tab You may optionally select any Categories that have been enabled for Interest Groups. Advanced Tab Super Admin Account If  Yes , the User will have all of the rights and privileges of a  Super User . If  No , the User will  not  be a Super User. See the  Super User section  for more information on Super Users. Active If  Yes , the User will be able to log in, and use Mura within the permissions established. If  No , the User will be unable to log in, and is unable to use Mura. Site You may reassign a User to a different  Site Pool  here. Tags You may enter a comma-delimited list of  Tags  here. This meta-data is useful for grouping users. Remote ID This field is primarily used by developers and is typically tied to a primary identifying field on a third-party system. When finished, click the  Add  or  Update  button to save your changes. The Super Admin User Account  Users designated as a " Super Admin Account " have the highest authority, rights, and control in Mura. These " Super Admin Users " can: Create more Super Admin Users Create & manage System Groups and Member Groups for any site Create & manage System Users and Site Members for any site Add new sites Update the Site Settings of existing sites Access and use features included under Global Settings Full access to the File Manager Ability to install, manage, and delete plugins Create, publish, and modify content for any site And much more! In short, Super Admin Users can do pretty much anything and everything Mura offers. As noted in the first bullet,  only Super Admin Users have the ability to designate other Super Admin Users . Also, Super Admin Users may, but don't necessarily have to, belong to any user group(s). Yes, Super Admin Users have great power, and as the old saying goes, " With great power, comes great responsibility. " Obviously, anyone you choose to designate as a Super Admin User must be someone you can trust. How to Designate a Super Admin User Account First and foremost,  only Super Admin Users have the ability to designate other Super Admin Users . So, you must be logged in under a Super Admin User Account to perform these steps. From the back-end administration area of Mura, select  Users  from the main navigation, then  Users . Locate and select the user you wish to designate under either the Site Members tab, or the System Users tab. From the  User Maintenance Form , select the  Advanced  tab. Under  Super Admin Account , select the  Yes  radio button. Click  Update  to save the change. The user account is now a Super Admin User. The user should now have a star icon next to their name in the System Users listing. Managing Permissions  Before you begin the process of setting up permissions, you need to ensure you have  created the groups  you will be working with in Mura. If you haven't already done so, please visit the  Creating and Managing Groups section  before proceeding. Once you have established the groups your organization desires, you can begin the process of enabling and/or restricting permissions for each group, throughout the various content sections of your site. You will also want to determine which group(s) have access, or do not have access, to various modules within Mura such as the Content Staging area, Categories, Collections, and so forth. Here are the general steps in setting up permissions in Mura: Create Groups Create Users  and  assign them to groups Optionally share  User Pools  across various sites Let Mura know which group(s) are allowed to access to  each specific site Let Mura know the roles/permissions each group has for  Content ,  Components ,  Categories ,  Users , and  Plugins Let Mura know the roles/permissions each group has for various Modules (e.g.,  Staging ,  Collections ,  Comments , and  Forms )   User Pools  Mura allows for the possibility of having multiple websites under the same installation. In other words, out of the box, Mura is "multi-sited." Each website could have its own, unique domain name, subdomain name, or any combinations of unique domains and subdomains. Because of this, Mura allows you to share resources, including  Member User Pools  and  System User Pools . This is important to understand, because you could theoretically have all of your  User Pools  under one site, and share them across some, or even all, of the websites managed by Mura. Another reason this is important is, due to the "multi-sited" aspect of Mura, you will need to explicitly set the  Permissions  for each group on each site. Because each organization has its own use cases and needs, there's not one, singular "best practice" to promote when it comes to User Pools. That said, a common scenario might be where an organization is hosting both their public-facing website for their customers, as well as a completely separate intranet, designed specifically for the employees. In this scenario, you might want to be able to share the user groups for both sites, so those users will not have to maintain two separate login accounts. If so, you could easily share the "User Pools" of one site, with the other. Note:  When sharing  System User Pools , all users in the " Admin " group will have full administrator privileges on each site that is using its pool of System Users. How to Share User Pools To share  User Pools , follow the steps below: From the back-end administration area of Mura, go to the site you wish to change the  User Pool  for. Select  Site Settings  from the main navigation, and then click  Edit Settings . Click the  Shared Resources  tab to reveal all of the available "pools" you can share. If you would like to use the  Member User Pool  of another site, select it from the dropdown menu. If you would like to use the  System User Pool  of another site, select the desired site from the dropdown menu. Click the  Save Settings  button to save your changes. Next, you will need to establish the permissions for each group. Site Permissions  Once you've  established your user groups ,  created users and assigned them to those groups,  and chosen whether or not to  share User Pools  across your various sites, you need to let Mura know which group(s) will be able to access each, specific site managed under the same installation of Mura. The only exception to this step is the default "Admin" group, which automatically has access and full editing privileges throughout their specific site. Allowing access to each specific site merely means that users assigned to the group will be able to log in to the site. It will be up to you to establish the roles and privileges each group has throughout the various sections of your site. Also keep in mind,  System Groups  will be able to access the back-end administration area of Mura, and  Member Groups  will not be able to. This means users assigned to a "Member Group" will only be able to access the front-end editing features of a site, assuming you've granted them access to the site, and given them the appropriate permissions to do so. If you skip this step, or forget to allow any groups access to the site, only users who belong to the "Admin" group will be able to access anything. For example, if a user named Mary Marketing were assigned to the System Group labeled "Marketing" and attempted to log in to the back-end administration area, she would see the following " Access Denied " screen, if her group were not granted access to the site. So, if a user informs you they see the "Access Denied" screen, you should check to make sure the user has been assigned to the proper group(s) and verify whether or not you need to grant their group(s) access to the site. How to Allow Groups Access From the back-end administration area of Mura, click  Site Settings  on the main navigation, and select  Permissions . You should be taken to the  Permissions  screen. Simply select the checkbox for each group you wish to allow access to. Click  Update , to save your changes. Next, you will need to specify the roles and privileges each group has throughout the various sections of your site. Content Permissions  Before you begin granting or restricting editing privileges for content, ensure you have completed the first four steps outlined on the  Managing Permissions  page. You may also want to review the  Author vs. Editor Roles section , before continuing. Permissions cascade from the top-most content item, down through its children, grandchildren, and beyond. By default, all groups granted access to edit the site begin with " Deny " privileges, except for the " Admin " group. The Admin group automatically has full editing privileges throughout Mura. How to Apply Permissions to Content From the  Content  screen, click the three-dot menu of the content item you wish to manage permissions for, and select  Permissions . Or , if editing a content item, click the  Actions  button, and select  Permissions . From the  Permissions  screen, select your desired options for each group. Editor Groups granted " Editor " permissions are able to " write " content,  as well as  " publish " content. This means they can create new content items, update existing content items, delete content items, and even publish content items (or, make them "live"), but only within the section(s) of the site where they have been granted these privileges. The "Admin" group automatically has Editor privileges throughout Mura. Author Groups granted " Author " permissions can  only  " write " content. This means they can create new content items, and update existing content items. However, they are unable to publish or delete content items. Inherit If selected, permissions applied to the content item's parent will be used. If the parent also has "Inherit" selected, then Mura will traverse up the tree until it finds an explicit setting. If it reaches the "Home" content item, and "Inherit" is selected, the permissions fall back to "Deny." Read Only If selected, users of the group will not be able to edit the content item, or any of its children, unless explicitly overridden with a different setting down the tree. This is very similar to the "Deny" setting, except clicking the three-dot menu of a content item will reveal "Copy" and "Copy All" options. That said, if they choose to Copy a content item with "Read Only" privileges, if the user chooses to "Paste" the content item in an area they have Author or Editor rights to, the content will retain its "Read Only" privileges. Deny This is the default setting for all groups, except the "Admin" group. If selected, users of the specified group will only be able to see the Title, and tree structure of the content. They will not be able to edit the content item, or any of its children, unless explicitly overridden with a different setting down the tree. Click  Update , to save your changes. Users will obtain the new roles/privileges on their next successful login. So, if a user is logged in when the permissions were updated, they will have to log out, and then log back in, to see the changes. Note : A commonly asked question is whether or not there is a way to "hide" content, or sections of a site, from certain groups in the back-end administration area of Mura. While there's always a way to do something programmatically, the short answer is no. The primary reason is twofold: just because a group may not be able to edit a top-level section, the group may actually be granted editing privileges to its children or grandchildren, and secondly Mura offers a way to allow for front-end editing only by assigning a user to a Member Group with editing privileges, instead of a System group. Component Permissions  Managing permissions for  components  is very similar to  managing content permissions , because components can be grouped together in a hierarchy, just like content. As you've seen in the  Components section , you can nest a component, or a group of components together under a Folder, or other components. Not only does this make it easy from an organizational point of view, it really simplifies things from the viewpoint of enabling or restricting editing permissions as well. As you've already learned, permissions cascade from the top-most item, down through its children, grandchildren, and beyond. By default, all groups granted access to edit the site begin with " Inherit " privileges, except for the " Admin " group. The Admin group automatically has full editing privileges throughout Mura. How to Apply Permissions to Components From the  Content  screen, on the  Tree View  tab, click the  Components  button. Since all non-Admin groups begin with " Inherit " privileges, they will not be able to see the " Components " button on the  Content  >  Tree View  tab. For example, the following screen is what a "Marketing Group" user would initially see before permissions for components have been explicitly set. As you'll notice, this user is unable to see a "Components" button at all. The first thing you'll want to decide on is whether or not you want the group to be able to edit components by default. Then, you'll set permissions on the top-level " Components " item itself, and those permissions will cascade down through the rest of the components. So, if you explicitly set the group's permissions on the top-level  Components  item to " Deny ," the group will be able to see the " Components " button on the  Content  >  Tree View  screen, and by default, they won't be able to actually edit anything, unless you explicitly set the group's role to "Editor" or "Author" by following the rest of the steps below. Conversely, if you set the group's permissions on the top-level  Components  item to " Editor " or " Author, " the group will inherit those rights throughout the Components area, unless explicitly overridden somewhere down the tree. Follow the steps below for editing the permissions of the top-level  Components  item itself. Editor Groups granted " Editor " permissions are able to " write " components,  as well as  " publish " components. This means they can create new components, update existing components, delete components, and even publish components (or, make them "live"), but only within the section(s) of the site where they have been granted these privileges. The "Admin" group automatically has Editor privileges throughout Mura. Author Groups granted " Author " permissions can  only  " write " components. This means they can create new components, and update existing components. However, they are unable to publish or delete components. Inherit If selected, permissions applied to the component's parent will be used. If the parent also has "Inherit" selected, then Mura will traverse up the tree until it finds an explicit setting. If Mura reaches the topmost component, and "Inherit" is selected, the permissions fall back to "Deny." Deny This is the default setting for all groups, except the "Admin" group. If selected, users of the specified group will only be able to see the Title, and tree structure of the components. They will not be able to edit the component, or any of its children, unless explicitly overridden with a different setting down the tree. Click the three-dot menu of the component you wish to manage permissions for, and select  Permissions . Or , if editing a component, click the  Actions  button, and select  Permissions . From the  Permissions  screen, select your desired setting for each group. Click  Update , to save your changes. Users will obtain the new roles/privileges on their next successful login. So, if a users is logged in when the permissions were updated, they will have to log out, and then log back in, to see the changes.   Categories Permissions  While Content Managers can easily  categorize content , only the  Admin  group is able to manage  Categories  by default. Allowing a group to manage Categories is an "all or nothing" thing. In other words, if a group has access to manage Categories, they can create, edit, and or delete all categories. How to Apply Permissions to Categories To allow groups the ability to create, edit, and or delete categories, follow the steps outlined below. From the back-end administration area of Mura, select  Categories  from the main navigation. On the  Categories  screen, click the  Permissions  button. Select the checkbox under " Allow " for each group you wish to enable access for. Click  Update , to save your changes. Users will obtain the new roles/privileges on their next successful login. So, if a user is logged in when the permissions were updated, they will have to log out, and then log back in, to see the changes. Users Permissions  Users who belong to the  Admin  group are automatically able to manage groups and users for both  System Groups , and  Member Groups . Mura also allows for the ability to delegate managing  Member Groups  and  Site Member users to other groups. The important thing to keep in mind here is that you cannot delegate another group to manage  System Groups  and  System Users . Only members of the  Admin System Group  and  Super Admin Users  are able to manage  System Groups  and  System Users . How to Apply Permissions to Users From the back-end administration area of Mura, select  Users , and click  Users . On the  Users & Groups  screen, select the  Site Members  tab, if it's not already selected. Click the  Permissions  button. Select the checkbox under " Allow " for each group you wish to enable access for. Click  Update , to save your changes. Users will obtain the new roles/privileges on their next successful login. So, if a user is logged in when the permissions were updated, they will have to log out, and then log back in, to see the changes. Plugins Permissions  Although Mura is extremely powerful and has a multitude of useful features off-the-shelf, we recognize your organization may also require some custom functionality and/or applications to meet your organization's needs. Plugins allows developers to do just that. Often times, plugins have their own, custom administrative user interface, and while it's up to your developers to write the code to prevent unauthorized access, Mura allows for a way to collect data on which group(s) you wish to enable access for. How to Apply Permissions to Plugins It is extremely important to understand the steps outlined below merely collect the information on which group(s) you wish to enable access for to a particular plugin. Following the steps below will  not , in and of themselves, prevent unauthorized access to the plugin. The developer(s) responsible for creating and/or maintaining the plugin are responsible for ultimately writing the proper code to obtain this data, and ultimately prevent and/or allow access to the specified group(s). From the back-end administration area of Mura, select  Plugins  from the main navigation, then click  Site Plugins . You should see the  Site Plugins  screen, and a listing of any plugins which have been enabled for the specific site you are currently working with. Click the three-dot menu to the desired plugin, and select  Permissions . Select the checkbox under " Allow " for each group you wish to enable access for. Click  Update , to save your changes. Users will obtain the new roles/privileges on their next successful login. So, if a user is logged in when the permissions were updated, they will have to log out, and then log back in, to see the changes. You will have to perform these steps for each site you wish to enable and/or restrict access for. Form Permissions  Managing permissions for  forms  is very similar to  managing content permissions , because forms can be grouped together in a hierarchy, just like content. As you've seen in the  Forms section , you can nest a form, or a group of forms together under a Folder, or other forms. Not only does this make it easy from an organizational point of view, it really simplifies things from the viewpoint of enabling or restricting editing permissions as well. As you've already learned, permissions cascade from the top-most item, down through its children, grandchildren, and beyond. By default, all groups granted access to edit the site begin with " Deny " privileges, except for the " Admin " group. The Admin group automatically has full editing privileges throughout Mura. How to Enable/Disable Forms Manager To enable or disable the Forms Manager, follow the steps below. From the back-end administration area of Mura, select  Site Settings , then click  Edit Settings . Select the  Modules  tab. Locate the field labeled  Forms Manager , then select " On " to enable it, or " Off " if you wish to disable it. Click  Save Settings . How to Apply Permissions to Forms From the  Content  screen, on the  Tree View  tab, click the  Forms  button. Since all non-Admin groups begin with "Inherit" privileges, they will not be able to see the "Forms" button on the Content > Tree View tab. For example, the following screen is what a "Marketing Group" user would initially see before permissions for forms have been explicitly set. As you'll notice, this user is unable to see a "Forms" button at all. The first thing you'll want to decide on is whether or not you want the group to be able to edit forms by default. Then, you'll set permissions on the top-level " Forms " item itself, and those permissions will cascade down through the rest of the forms. So, if you explicitly set the group's permissions on the top-level  Forms  item to " Deny ," the group will be able to see the " Forms " button on the  Content  >  Tree View  screen, and by default, they won't be able to actually edit anything, unless you explicitly set the group's role to "Editor" or "Author" by following the rest of the steps below. Conversely, if you set the group's permissions on the top-level  Forms  item to " Editor " or " Author, " the group will inherit those rights throughout the Forms area, unless explicitly overridden somewhere down the tree. Follow the steps below for editing the permissions of the top-level  Forms  item itself. Editor Groups granted " Editor " permissions are able to " write " forms,  as well as  " publish " forms. This means they can create new forms, update existing forms, delete forms, and even publish forms (or, make them "live"), but only within the section(s) of the site where they have been granted these privileges. The "Admin" group automatically has Editor privileges throughout Mura. Author Groups granted " Author " permissions can  only  " write " forms. This means they can create new forms, and update existing forms. However, they are unable to publish or delete forms. Inherit If selected, permissions applied to the form's parent will be used. If the parent also has "Inherit" selected, then Mura will traverse up the tree until it finds an explicit setting. If Mura reaches the topmost form, and "Inherit" is selected, the permissions fall back to "Deny." Deny This is the default setting for all groups, except the "Admin" group. If selected, users of the specified group will only be able to see the Title, and tree structure of the forms. They will not be able to edit the form, or any of its children, unless explicitly overridden with a different setting down the tree. Click the three-dot menu of the form you wish to manage permissions for, and select  Permissions . Or , if editing a form, click the  Actions  button, and select  Permissions . From the  Permissions  screen, select your desired options for each group. Click  Update , to save your changes. Users will obtain the new roles/privileges on their next successful login. So, if a users is logged in when the permissions were updated, they will have to log out, and then log back in, to see the changes.   Content Staging Permissions  If you have the Content Staging Manager enabled on your site, you may want to allow groups the ability to manage Change Sets within the Content Staging Manager. By default, Super Admin Users, and members of the Admin group are automatically able to manage Change Sets. How to Enable/Disable Content Staging Manager To enable or disable the  Content Staging Manager , follow the steps below. From the back-end administration area of Mura, select  Site Settings , then click  Edit Settings .   Select the  Modules  tab. Locate the field labeled  Content Staging Manager , then select " On " to enable it, or " Off " if you wish to disable it. Click  Save Settings . How to Apply Permissions to Content Staging Manager To allow groups the ability to manage Change Sets within the Content Staging Manager, follow the steps outlined below. From the back-end administration area of Mura, select  Staging  on the main navigation. From the  Content Staging  screen, click the  Permissions  button. Select the checkbox under " Allow " for each group you wish to enable access for. Click  Update , to save your changes. Users will obtain the new roles/privileges on their next successful login. So, if a user is logged in when the permissions were updated, they will have to log out, and then log back in, to see the changes.   Collections Permissions  If you have enabled the Collections Manager, you may want to allow some groups the ability to manage Collections. By default, Super Admin Users, and members of the Admin group are automatically able to manage collections. How to Enable/Disable Collections Manager To enable or disable the Collections Manager, follow the steps below. From the back-end administration area of Mura, select  Site Settings , then click  Edit Settings . Select the  Modules  tab. Locate the field labeled  Collections Manager , then select " On " to enable it, or " Off " if you wish to disable it. Click  Save Settings . How to Apply Permissions to the Collections Manager To allow groups the ability to manage Collections, follow the steps outlined below. From the back-end administration area of Mura, select  Collections  on the main navigation. From the  Collections  screen, click the  Permissions  button. Select the checkbox under " Allow " for each group you wish to enable access for. Click  Update , to save your changes. Users will obtain the new roles/privileges on their next successful login. So, if a user is logged in when the permissions were updated, they will have to log out, and then log back in, to see the changes.   Comments Permissions  If you allow comments to be posted to your website, you are definitely going to need someone to help manage those comments. By default, Super Admin Users, and members of the Admin group are automatically able to manage comments. How to Enable/Disable Comments Manager To enable or disable the Comments Manager, follow the steps below. From the back-end administration area of Mura, select  Site Settings , then click  Edit Settings . Select the  Modules  tab. Locate the field labeled  Comments Manager , then select " On " to enable it, or " Off " if you wish to disable it. Click  Save Settings . How to Require Approval of Comments Some organizations prefer comments are moderated, or reviewed and "approved" before being posted for other visitors to the public-facing side of the site to see. To enforce this kind of process, follow the steps below. From the back-end administration area of Mura, select  Site Settings , then click  Edit Settings . Select the  Basic  tab. Locate the field labeled " Allow Comments to be Posted Without Site Admin Approval ." Select " No " to require approval of all comments, or " Yes " if you don't wish to approve all comments before they are posted. Click  Save Settings . How to Apply Permissions to Comments Manager To allow groups the ability to manage Comments, follow the steps outlined below. From the back-end administration area of Mura, select  Comments  on the main navigation. From the  Comments  screen, click the  Permissions  button. Select the checkbox under " Allow " for each group you wish to enable access for. Click  Update , to save your changes. Users will obtain the new roles/privileges on their next successful login. So, if a user is logged in when the permissions were updated, they will have to log out, and then log back in, to see the changes.   Publishing Workflows  In this section, you will learn about the various publishing workflow options that are available to you. From little-to no workflow at all, to forcing all content to go through strict approval chains, Mura can accommodate your organization's publishing workflow needs. Simple Publishing Workflow  As you learned throughout the  Permissions section , all permissions are "group-based." As you've also learned in the  Author vs. Editor Roles section , " Editors " can write  and  publish content, while " Authors " can only "write" content. Whether you realized it or not, these are the basic cornerstones of the most basic publishing workflow within Mura. In short, granting a group "Editor" privileges means users in the group can already publish their content. So, there's no need to notify anyone to review their additions and/or changes before making it "live." However, restricting a group to "Author" privileges forces those users to notify someone with "Editor" privileges in order to publish their additions and/or changes. How "Authors" Can Notify "Editors" In smaller organizations, of course an "Author" might be able to simply ask a known "Editor" who might be nearby to log in and review their new content. Or, "Authors" could send their own email message to a known "Editor" as well. However, "Authors" could also follow the steps outlined below to leverage a baked-in feature of Mura to send an email with a link to review the content. The steps below aren not limited to "Authors" as they could also be used by "Editors," if they wish to notify someone else about their changes. When finished creating and/or updating a content item, select the  Publishing  tab. Towards the bottom of the Publishing tab, located the field labeled " Notify For Review ." When you enable " Notify for Review " by clicking the checkbox, a couple of additional form fields should appear labeled " Send to " and " Message ." The "Send to" field is a multi-select menu listing other users and their roles/privileges such as "Author" and "Editor." You may select users by using + click on a PC, or + click on a Mac. If you wish to include a detailed message, you may enter it in the "Message" field. Otherwise, the default text will be sent. Click the  Save Draft  button, to save your changes, and an email will be sent to the selected user(s).   Content Staging  The  Content Staging Manager  provides a way to schedule a collection of content, via " Change Sets ," to publish at the same date and time. A  Change Set  is like a bucket, where you can toss in any changes you want to make "live" at the same moment. In addition to being able to simultaneously publish a group of content, you can preview a site as if the content assigned to specific Change Sets has been published, before it's actually published. Some organizations may also be interested in using Mura's ability to  force all changes to be published via Change Sets , versus allowing the traditional ability to publish one-off changes. How to Enable/Disable the Content Staging Manager To enable or disable the Content Staging Manager, follow the steps below. From the back-end administration area of Mura, select  Site Settings , then click  Edit Settings . Select the  Modules  tab. Locate the field labeled  Content Staging Manager , then select " On " to enable it, or " Off " if you wish to disable it. Click  Save Settings .   Create a Change Set  As previously mentioned, Change Sets are like buckets where you can toss all kinds of new content and updates together in one place. To create a  Change Set , follow the steps below. From back-end administration area, select  Staging  on the main navigation. This should display the  Content Staging  screen. Click the  Add Change Set  button. You should now see the  Add Change Set  screen. Basic Tab Name A unique name for the Change Set (e.g., 2017 Summer Promo). Description A description that may be helpful for anyone viewing or editing the Change Set. Close Date The Close Date field may be used to prevent any users from adding more content after the specified date. This is useful so that users who need to review and/or approve the change set have time to do so, prior to the Change Set being published, which is why it's typically a good idea to enter a date and time at least a day or two ahead of the Publish Date. Publish Date This is the date and time all content assignments in the Change Set should go "live." Categories Tab You may categorize your Change Set by selecting your desired categories. Tags Tab You may enter a comma-delimited list of tags for the Change Set. Click  Add , to save your new change set. Assign Content to a Change Set  Mura allows you to add content items to Change Sets as well as Components and Forms. To add content to a Change Set, follow the steps below. Either create a new content item, or select an existing content item you wish to edit specifically for the Change Set. Once you have made your desired additions and/or changes, simply click the " Save to Change Set " button. Note : Only groups with "Editor" privileges will be able to see the "Save to Change Set" button. This should launch the  Assign to Change Set  dialog window. Select your desired  Change Set  from the list. Or, select the radio button next to the " Add Change Set " text box, enter a " Title " for it. Click  Save , to save your changes to the Change Set. Repeat these steps for all content you wish to add to the Change Set. View Content Assignment List  Mura maintains a listing of all content that has been assigned to each Change Set. To view the assignments, follow the steps below. From the back-end administration area of Mura, select  Staging  from the main navigation. You should be taken to the  Content Staging  screen. From the list of available Change Sets, select the three-dot menu next to the Change Set you wish to view assignments for, and select the  Assignments  option. You should be taken to the  Change Set Content List  screen. Any content, components, or forms that have been assigned to the Change Set, should be listed here. Preview a Change Set  Once you have added content to a Change Set, you can preview your site to see what it will look like once the Change Set has been published. To preview a Change Set, or obtain a URL to share with other team members, follow the steps below. From the back-end administration area of Mura, select  Staging  from the main navigation. You should be taken to the  Content Staging  screen. From the list of available Change Sets, select the three-dot menu next the your desired Change set, and select the  Preview  option. Or , from the list of available Change Sets, select the three-dot menu next to the Change Set you wish to view assignments for, and select the  Assignments  option. You should be taken to the  Change Set Content List  screen. Here, you either click the Preview Change Set button, or click the shareable URL. The shareable URL may be used by people who don't even have an account in Mura, to see what the site would look like as if the changes were "live" or published. This is useful for organizations where people, such as managers, may want to see your changes, but not necessarily make any changes, or approve anything per se. As you can see in the image below, when a non-Mura use navigates to the shareable URL, an extremely limited version of Mura's front-end toolbar will appear at the top of the screen. Hovering over the name of the Change Set will reveal a list of other Change Sets, as well as the option to select "None" to exit the preview. Hovering over the next icon, will reveal a listing of content items included in the Change Set. You can click any of the links to navigate to the pages to view them in the future state as well. The last icon on the front-end toolbar indicates whether or not the content item you're currently viewing is included in the Change Set. A checkmark indicates "Yes," and the universal symbol for No (or sometimes "Ban"), indicates the content item is not included.   Publish a Change Set  If you enter a Publish Date when creating a Change Set, the Change Set will automatically publish all of the content assignments on that date and time. However, there may be times when you wish to publish everything ahead of schedule. So, Mura also allows you to manually publish a Change Set at any time. From the back-end administration area of Mura, select  Staging  from the main navigation. You should be taken to the  Content Staging  screen. From the list of available Change Sets, select the three-dot menu next the your desired Change set, and select the  Edit  option. You should be taken to the  Edit Change Set  screen. If you're ready to publish the Change Set, click  Publish Now . You should be presented with an  Alert  dialog window to confirm your decision to publish. Select " OK " to confirm, or " Cancel " to stop. Assuming you selected "OK," your Change Set should now be "live" and viewable on the public-facing side of your site. Roll Back a Change Set  If you have published a Change Set, and for some reason, you wish to "un-publish" it, you can do so using Mura's "Roll Back" feature. Follow the steps below to Roll Back a Change Set. From the back-end administration area of Mura, select  Staging  from the main navigation. You should be taken to the  Content Staging  screen. From the list of available Change Sets, select the three-dot menu next the your desired Change set, and select the  Edit  option. You should be taken to the  Edit Change Set  screen. You should also see a notice that the change set has been published. Click the  Roll Back  button to un-publish your Change Set. You should be presented with an  Alert  dialog window to confirm your decision to roll back. Select " OK " to confirm, or " Cancel " to stop. Assuming you selected "OK," your Change Set should now revert back to un-published. Note : Any "new" content which was originally assigned to the Change Set will still be "published." This behavior may change in a future version of Mura. Enable/Disable Publish via Change Sets Only  If desired, you can force all content changes to be published through Change Sets, versus the standard publishing process. To enable or disable this feature, follow the steps below. From the back-end administration area of Mura, select  Site Settings , then click  Edit Settings . Select the  Modules  tab. Locate the field labeled  Publish via Change Sets Only , then select " On " to enable it, or " Off " if you wish to disable it. Click  Save Settings . Approval Chains  Approval chains are collections of pre-defined publishing workflows where content must be approved by specified user groups, in a specific order, before the content is considered "live" and available for viewing on the public-facing side of your site. For many organizations, teams responsible for managing content may be somewhat small, consisting of only a few people. However, they are typically responsible for reviewing and editing work from a much larger group of content contributors. Using a workflow that includes approval chains streamlines how and when publishing tasks happen, making everyone's job cleaner and much easier. Create an Approval Chain  Only members of the  Admin System Group  and  Super Admin Users  have the ability to create, modify, and apply approval chains. Mura can automatically send email notifications to members of each group in the approval chain to inform them a review is needed. Follow the steps below to create approval chains. From the back-end administration area of your site, select  Site Settings  on the main navigation, and click  Approval Chains . You should see the  Approval Chains  screen, listing any existing approval chains. Click the  Add Approval Chain  button. The  Edit Approval Chain  screen should appear. Name Enter a name for the approval chain. If your organization will be utilizing more than one approval chain, you may want to use some descriptive text for the name so that it's easier to remember where you desired to apply the approval chain. For example, if you want to create a specific approval chain for the "News" section of your site, you could use "News Approval Chain" for this field. Description This is text area for you to enter descriptive notes to inform other administrators what the approval chain is being used for. Available Groups ( Drag from here... ) This area lists all System Groups for the site. Using your mouse, you can "click and drag" your desired group from this section, move it over to the " Groups in this Approval Chain " area, and then release your mouse button to assign it to the approval chain. Then, repeat this process for each group you wish to be in the approval chain itself. Groups in this Approval Chain ( ...then drop and set the order here. ) Groups listed here are merely the groups required for reviewing content before it is finally published and "live" for the public-facing side of your site. Approval chains do not affect "permissions" for creating or updating content within any section of a site where the  approval chain has been applied , they merely force content to go through a review process. If you wish to establish permissions, please visit the  Managing Permissions  section. The first group in the chain will be the first group required to make the decision to "Approve" or "Reject" any additions or changes. The order number listed next to the group name indicates the order each group is required to review the content. You can also reorder the chain by clicking on the desired group you wish to move, dragging it to the desired location, and then releasing your mouse. To remove a group from the approval chain, "click and drag" the group back to the "Available Groups" area, and release your mouse button. Click  Update , to save your approval chain. Repeat these steps to create any additional approval chains. Now that you've created your approval chain(s), you'll want to  apply the approval chain(s)  to your site, or selected areas of your site. How to Apply an Approval Chain  After you've  created your desired approval chains , you will want to apply the approval chains to the desired areas of your site, to enforce your publishing workflows. Approval chains may be applied to content, components, and forms. Also, approval chains flow through to any descendants, unless explicitly overridden by a different approval chain option down the tree. Keep in mind, approval chains do not affect "permissions" for creating or updating content within any section of a site where the approval chain has been applied, they merely force content to go through a review process. If you wish to establish permissions, please visit the  Managing Permissions  section. However, only groups with  Editor  privileges will be able to submit content, components, or forms for approval. Groups with  Author  privileges will only be able to use the  Simple Publishing Workflow . Some organizations may want to consider changing a group's privileges from Author to Editor after applying the approval chain, so they may be able to submit content for approval, instead of having to notify an Editor, who must then submit it for approval. To apply an approval chain, follow the steps outlined below. From the back-end administrator of Mura, click  Content  from the main navigation.   Navigate to the desired content item/section, component, or form, click the three-dot menu, and click  Permissions . You may also apply your approval chain to the topmost item in the desired tree, which would then become the default approval chain applied to all descendants. You should see the  Permissions  screen. Notice the column of checkboxes labeled  Approval Chain Exempt , next to each group listed under both System Groups, and Member Groups. The checkbox is automatically enabled for the Admin System Group, and cannot be disabled. The checkboxes for all other groups will be read-only, unless the group is granted Editor privileges. If you select a checkbox for any other group(s) with Editor privileges, members of the selected group(s) will not have to submit anything for approval, and will be exempted from the approval chain process. Some organizations may choose this option if there is only one group in the selected approval chain, and they wish to exclude the group from having to submit their own content for approval. Towards the bottom of the  Permissions  screen, locate the section of the form titled  Approval Chain . Choose your desired option from the  Select Approval Chain  select menu. Click the  Update  button, to save your changes. Repeat these steps for each section you wish to apply a different approval chain. Example Approval Chain Workflow  Approval chains begin when a member of a group with  Editor  privileges submits new or edited content to a section of a site with an approval chain applied to it. In this example, two groups will be represented: News Writers Creates, edits, and submits news content for approval News Approvers Edits, approves, and publishes all news content For this example, the following illustration reflects the News Approval Chain, where the News Approvers group is required to approve all content wherever the approval chain has been applied. In the following illustration, you'll see we've edited the  Permissions  of the News section of our site. Both the News Approvers and News Writers groups have Editor privileges, and the News Approvers group is exempt from the approval chain. This means members of the News Writers group will be able to submit content for approval, and members of the News Approvers group will be notified when someone needs to review the submitted content and "decision" it with either "Approve" or "Reject." vvv   Submitting Content for Approval  Groups require Editor privileges in order to submit content for approval. If a group has only been granted Author privileges, they will have to  notify an Editor , who in turn, may follow the steps outlined below to submit content for approval. Whenever a content item is either edited or added to a section which has an Approval Chain applied, the  Publish  button is replaced with a  Send for Approval  button. If Change Sets are enabled, the  Save to Change Set  button is replaced with  Save to Change Set & Send for Approval . Keep in mind, only groups with Editor privileges will see these buttons. Groups with Author privileges will only see the Save Draft, and Preview buttons. Clicking any of the  Send for Approval  buttons triggers the Approval Chain process. To view your "submissions" for approval, click the down arrow of the user menu in the upper right corner of the screen, in the back-end administration area of Mura. You should then be taken to the  Content  >  List View tab . The " Showing " filter will be preset to  My Submissions , and all submitted content items in " Pending Approval " status will be listed. If you wish to edit a content item in "Pending Approval" status, you can still do so, since it's technically in a "Draft" state. Attempting to edit the content item will invoke a  Select Version to Edit  dialog window. Select the "Edit Latest Draft" to edit the content item. When you edit the content item, an alert will appear above the tabs, with a link to  View Details . Clicking the  View Details  link will launch the  Status  dialog window. You can see who created the content item, and which group the approval is waiting on. If you wish to cancel your request, simply click the  Apply  button. Otherwise, click the " X " at the top right of the window to close the dialog window. Reviewing and Decisioning Pending Approval Requests  Mura offers different workflow options for reviewing pending approval requests, based on which groups you've been assigned to. Super Admin Users and members of the Admin System Group have the ability to review all pending approval requests. Members of all other groups designated as approvers in an approval chain only have the ability to view pending approval requests for their specific groups. How to Review and Decision a Pending Approval Request When logged in to the back-end administration area of Mura, to the right of your user menu, you may see a number next to the down arrow. Click the down arrow to open the user menu. Submissions The amount listed to the right indicates the number of content items the logged in user has submitted for approval. Clicking the  Submissions  option will forward the user to the  Content  screen, with the  List View  tab enabled, and the  Showing  menu will be pre-selected with  My Submissions  which filters all site content in the list below it to display all content items the user has submitted that is still waiting to be decisioned. Approvals The amount listed to the right indicates the number of content items submitted for approval to a group the logged in user belongs to, and is waiting for someone to review, then decide whether to approve or reject the submission. From the user menu, select  Approvals . You should be taken to the  Content  screen, with the  List View  tab enabled, and the  Showing  menu will be pre-selected with  My Approvals  which filters all site content in the list below it to display all content items waiting to be decisioned by the logged in user. From here, you a couple of options to review the submitted content. You could choose to preview the content from the front-end, public facing view of your site, or you could choose to review the content from the back-end administration area. Review Via Front-End, Public Facing View Click the three-dot menu of the content item, and select  Version History . From the  Version History  screen, locate the version with the  Status  of  Pending Approval . Technically, there could be more than one version in Pending Approval when using Change Sets. So, you may have to repeat these steps for each Pending Approval version. Click the three-dot menu next to the Pending Approval version, and select  Preview . The Pending Approval version will display in a new tab, reflecting how the content would look as if it were "live" and published. Click the  Draft  status button on the front-end toolbar. The  Status  dialog window should appear. Continue the steps below. Review Via Back-End Administration Area If you click the title of a content item, a  Select Version to Edit  dialog window will appear. Select the content item located under  Versions Pending Approval  by clicking the pencil icon or the title itself. You should be taken to the  Edit Content  screen. The  Status  should reflect " Pending Approval " and an alert should appear above the tabs with a link to  View Details . Click either the  Pending Approval  link or the  View Details  link to reveal the  Status  dialog window. Continue the steps below. From the  Status  dialog window, you can view details about the content item, and see which group the approval chain is waiting on under the  Approval Status  section. Under the  Action  section, you can choose to  Approve  or  Reject  the submission. If you choose Reject, you will be required to enter  Comments , so the submitter will know why their content submission was rejected. Once you've made your decision, click the  Apply  button to save your decision. This process will need to be repeated by a member of any other group(s) assigned to the approval chain before the item will be officially  Published . Super Admin Users and Admin System Group Members Only  Super Admin Users and members of the Admin System Group have the ability to review all pending approval requests. Follow the steps below to view all pending approval requests. Super Admin Users  and members of the  Admin System Group  have the ability to view pending approval requests for any group. To do so, from the back-end administration area of Mura, they can select  Site Settings  from the main navigation, then click  Approval Chains . From the  Approval Chains  screen. click the three-dot menu next to the desired group, then select  Pending Requests.  Or, click on the name of the approval chain itself to achieve the same result. The administrator should now be able to see a listing of all pending requests for the selected group. Click the three-dot menu of any content item to reveal a menu of options. Edit Forwards you to the  Edit Content  screen. Preview Displays the currently published version of the content item in a new tab. Version History Forwards you to the  Version History  screen, where you can select the desired version you wish to work with. If you selected  Edit  from the three-dot menu, you should see the  Edit Content  Screen. The  Status  should reflect " Pending Approval " and an alert should appear above the tabs with a link to  View Details . Click either the Pending Approval link or the  View Details  link to reveal the  Status  dialog window. From the  Status  dialog window, you can view details about the content item, and see which group the approval chain is waiting on under the  Approval Status  section. Under the  Action  section, you can choose to  Approve  or  Reject  the submission. If you choose Reject, you will be required to enter  Comments , so the submitter will know why their content submission was rejected. Once you've made your decision, click the  Apply  button to save your decision. This process will need to be repeated by a member of any other group(s) assigned to the approval chain before the item will be officially  Published . Summary  In this section, you've learned how to create/manage groups and users, and learned the difference between "author" and "editor" roles. You also learned how to apply editing privileges to each group throughout the content area, and also how to enable or restrict access to other areas of the administrator such as who can manage Categories, Collections, and more. Lastly, you learned about the variety of publishing workflow options, and most likely discovered the one that best fits your organization's needs.