Step 5: Asset permissions configuration

If you want to configure who can administer asset, create new asset types and etc, you should configure permissions. Permissions are applied to Roles. If you aren't already familiar with Drupal's Role based permissions, please read Users, roles and permissions.

Asset module provides following permissions:

User Roles

One of the most basic features of administering user Web Site permissions is through the creation of roles.

Rather than assigning individual permissions to each user, roles are used to assign specifically selected permissions to selected users. The use of roles allows greater control over groupings of permissions and also makes it easier to assign or remove a role (thus multiple permissions) from a user.

For example assigning the role of "Author" to select authenticated users can be used to allow them to write and publish articles on your Web Site. Permissions for the "Author" role could open the permissions under "Node", "Article", - "Create new content", "Edit new content", and Delete own content" that other users and/or roles do not have. If a user no longer writes for your Web Site, Their User Profile can be quickly modified by removing the "Author" role and thus, all the permissions assigned under that role.

Your first step is to go to Administration/People/Permissions/Roles. Once there you will find three default roles of "Anonymous", "Authenticated", and "Administration" along with a text box allowing the addition of a custom role.


Viewing unpublished content

By default, anonymous and authenticated users will not be able to see unpublished content in Drupal. The way to grant them access is slightly different in Drupal 6 and 7.

Drupal 6

Users that are allowed to create content, will be able to see unpublished content created by themselves, but not nodes created by others. By enabling the permission 'administer nodes' in Drupal 6, you give them permission to see all unpublished content.

Note that 'administer nodes' does much more than just allowing users to see unpublished content and should be used with care. (more information on 'administer nodes')

View Unpublished Content with Views Module
The Views module allows access to view data from unpublished nodes. It has a separate filter for published / unpublished status to block access if wanted.

Drupal 7

In Drupal 7, users are not allowed to view any unpublished content by default, not even content created by themselves. By enabling 'View own unpublished content', you grant users access to their own unpublished content.

The only way to allow users access to all unpublished content in Drupal 7 (without using a contributed module), is to enable the permission 'Bypass content access control'.

Fedora Linux settings.php notes

If you have clean Fedora (or RHEL, CentOS, Scientific Linux) you have SELinux enabled by default after clean installation. There are few more steps to be done to be able to finish Drupal installation on SELinux enabled site to gain more security by SELinux.

Step 3: Create the settings.php file

Your Drupal download comes with a sample configuration file at sites/default /default.settings.php.

Before you run the installation script, you must copy the configuration file as a new file called settings.php file and then set some permissions.

Note: With Drupal 7.x, on some types of shared/local hosting, if PHP and Apache are run by the same user, Drupal will attempt to execute the first three steps for you. If you get errors referring to the "Settings file" during installation, you can perform these steps manually.

  1. Copy the default.settings.php file and save the new file as settings.php in the same directory. To do this, run the following command from the directory that contains your Drupal installation files:

    cp sites/default/default.settings.php sites/default/settings.php

    Note: Do not simply rename the file. The Drupal installer needs both files.

  2. To make the settings.php file writeable and to allow the installer to edit the file, use either of the following commands:

    chmod a+w sites/default/settings.php
    chmod 666 sites/default/settings.php

    Both commands have the same effect.


Subscribe with RSS Subscribe to RSS - permissions