Content Access Control

Advanced access control for Field Collection items following the design of node access in drupal core.

Abstract

Boost large websites using content_access (eventually combined with other access modules like node access node reference or node access user reference

A generic dashboard application based on JavaScript, HTML and CSS that runs in modern browsers. A server is only used to serve the dashboard files. Simply arrange and configure widgets to display data from any data source - not limited to Internet of Things.

A plugin API that allows easy widget and data source development to keep the dashboard as extensible as possible. All plugins are loaded securely in sandboxed iFrames.

This module provides an intermediary between configured system paths and created content.

System paths (such as the site's front page and error pages) can refer to content such as node pages. These may not be available in all environments, and may be deleted by content editors who have no access to update the site configuration.

As a solution, System Nodes provides configurable "soft reference" paths that can be used in the configuration, and which can be assigned to nodes while editing.

This module allows to handle the node access based on taxonomy. In tac_lite module, It will handle the permission based on term ids. If any one tid from node allows true, It will allow access. This module allows to handle the permission across the vocabulary by AND / OR Condition (configurable). It supports view, edit, delete permissions.

This module extend theme permission.
Allow edit theme for specific role.

How to use ?

1. Activate module
2. Go to admin/people/permissions and select theme permission for specific role

Description

This module extends the Field Permissions module by adding Organic Group membership level permissions as access requirement options for each field.

Teams solves a gap that appears in many organizations: the need for departments to own content, and not (necessarily) just people. Thus many people within a department team can create and edit content, alongside many other departments or teams, without the worry of someone having access to edit others' content.

This is a project being developed by the University of Calgary in an effort to manage the needs of 1,000+ departments across 14 faculties and 20 business units, with over 1,000 active editors.

A basic approach to handling API keys, implemented to be used together with REST.

Using 4 different headers and a HMAC based approach to authenticate users, all POST, PATCH, DELETE, PUT requests can be authenticated – I have not attempted to do this using GET requests as those mostly have a tendency to be broken.

Notice that even though this is API Key based do not mean that the /session/token can be omitted.