Speck CMS - A simple content management system for ColdFusion

you are here: home > documentation > users and security > reserved roles

• Getting Started
  • Speck Concepts
  • System Requirements
  • Installing
  • Upgrading
  • Hello Speck!
  • Articles
  • Caching
• Sample Application
  • Installing
  • Displaying Content
  • Managing Content
• Application Configuration
  • Settings
  • Keywords
  • Globalization
  • UI Customisation
• Building Applications
  • Application Initialisation
  • Creating Content Pages
  • Creating Content Types
  • Built-in Content Types
  • Built-in Property Types
  • Event Handlers
  • Context Sensitive Help
• Users and Security
  • Security Files
  • User Sessions
  • Access Control
  • Password Encryption
  • Reserved Roles
• Optimising Performance
  • Output Caching
  • Query Caching
  • Unnecessary Processing
  • Database Performance

Reserved Roles

Reserved roles in Speck are prefixed by "sp", and include spSuper, spEdit, and spLive. In general you should not add any roles that begin with "sp" followed by an English word, as the names may clash with current or future reserved roles.

Users who have the spSuper role can do anything, other users must have spEdit to add or edit content and spLive to promote content to the live version of the site. If promotion is disabled, users need to have spEdit and spLive because new content and modifications to existing content are immediately promoted to the live version of the site.

The spEdit and spLive roles must exist and these roles must have been assigned to some accessors before any content can be managed. Using  the spEdit and spLive roles administrators can restrict access to manage content to certain accessors. However, there are often cases where access to manage content will need to be further refined. The options to refine access control are discussed in the access control section.