Security framework
In this use case, each of the servers in the infrastructure grants different levels of access to different types of users. For example, someone who creates Schemas should not be able to access the Production Server.
Transfer security is based on the various servers' security frameworks. To illustrate this, this section first shows examples of types of users, and the right they have to read or write certain types of data on the various servers.
This example scenarios assumes the following groups:
- Authors can create content items (Components, Pages)
- Editors can organize content items in Folders and Structure Groups
- Web developers can develop structure in the form of Schemas, Categories and Keywords
- Publication Managers can develop layout in the form of Component Templates, Page Templates and Template Building Blocks
- Testers can create and manage test items of any type
- Site Managers have the final say in approving developed structure and layout
| Group | Permissions on Development Server | Permissions on Test Server | Permissions on Production Server |
|---|---|---|---|
| Author | Read: none, Write: none | Read: none, Write: none | Read: all types, Write: Pages, Components |
| Editor | Read: none, Write: none | Read: none, Write: none | Read: all types, Write: Folders, Structure Groups |
| Web developer | Read: all types, Write: Schemas, Categories, Keywords | Read: none, Write: none | Read: none, Write: none |
| Publication Manager | Read: all types, Write: Component Templates, Page Templates, Template Building Blocks | Read: none, Write: none | Read: none, Write: none |
| Tester | Read: all types, Write: none | Read: all types, Write: all types | Read: all types, Write: none |
| Site Manager | Read: none, Write: none | Read: none, Write: none | Read: all, Write: all |