Front End Level Security Explained:


Security model within GreenOrbit can be applied at multiple levels (i.e. per-subsite, per-folder, per-  page) across multiple publishing roles (i.e. contributors, editors, full control, etc.). This flexible security model enables you to deploy basic or sophisticated publishing protocols, read content on the intranet as well as restrict who can access information, i.e. deny access.  Security can be applied at the Subsite level (i.e. inherited by relevant applications within that subsite), and also the ability to change security settings at the Application level as well. 




Below are the levels of security fully explained:


Full Control: 

Can create/edit/delete content (e.g. Pages/Documents) and content is automatically   approved – create/edit/delete sections of the site structure (e.g. add a new Folder/Category) –   create/edit/delete templates in applications where templates are applicable (e.g. for web pages   create in CMS) – and set security


Editor: 

Can create/edit/delete content (e.g. Pages/Documents) and content is automatically approved – Can create/edit/delete sections of the site structure (e.g. add a new Folder/Category) – but cannot set security


Contributor: 

Can create/edit content (e.g. Pages/Documents) but can only delete content that they have created – content that is created/edited will need to be approved in applications where an approval process is implemented – cannot change the site structure (e.g. add a new Folder/Category) – and cannot set security


Creator: 

Can create content (e.g Pages/Documents) but can only edit/delete content that they have created – content that is created/edited will need to be approved in applications where an approval process is implemented - cannot change the site structure (e.g. add a new Folder/Category) – and cannot set security


Read Only: 

The item can only be viewed


Deny Access:

Access is denied to item