Documentation updates, split indexes and permissions into sections
This commit is contained in:
@@ -3,6 +3,10 @@ Indexes
|
||||
=======
|
||||
|
||||
Indexes are an automatic method to hierarchically organize documents in relation to their metadata and to each other.
|
||||
|
||||
Index templates
|
||||
===============
|
||||
|
||||
Since multiple indexes can be defined, the first step is to create an empty index.
|
||||
Administrators then define the tree template showing how the index will be structured.
|
||||
Each branch can be a pseudo folder, which can hold other child 'folders' or
|
||||
@@ -12,13 +16,19 @@ matched the path to reach the document container.
|
||||
.. image:: index_template.png
|
||||
:alt: index template
|
||||
|
||||
This template is the skeleton from which an instance of the index is then
|
||||
Index instances
|
||||
===============
|
||||
|
||||
The template is the skeleton from which an instance of the index is then
|
||||
auto-populated with links to the documents depending on the rules of each
|
||||
branch of the index evaluated against the metadata and properties of the documents.
|
||||
|
||||
.. image:: index_instance.png
|
||||
:alt: index instance
|
||||
|
||||
Index serving
|
||||
=============
|
||||
|
||||
Indexes can be mirrored to the operating system filesystem
|
||||
using the configuration option
|
||||
:setting:`DOCUMENT_INDEXING_FILESYSTEM_SERVING`.
|
||||
|
||||
@@ -5,7 +5,10 @@ Permissions
|
||||
**Mayan EDMS** provides very exact control over what activies users can
|
||||
perform. This control is divided into two levels of operation:
|
||||
|
||||
* 2-tier permission assignment - This level of activity control works
|
||||
2 tier permissions assignement
|
||||
==============================
|
||||
|
||||
This level of activity control works
|
||||
by allowing roles that are composed of users and group, to be granted
|
||||
a permission such that the holder of that permission can exercise it
|
||||
throught the entire collection of objects (document, folders, tags, etc),
|
||||
@@ -16,7 +19,11 @@ perform. This control is divided into two levels of operation:
|
||||
.. image:: permissions.png
|
||||
:alt: 2-tier permission diagram
|
||||
|
||||
* 3-tier access control - When more control is desired over which objects
|
||||
|
||||
3 tier access control
|
||||
=====================
|
||||
|
||||
When more control is desired over which objects
|
||||
actors(user, groups and roles) can exercise an action this method should be
|
||||
used. Under this level, actors are granted a
|
||||
permission but only in relation to a selected object. Example: Granting user
|
||||
|
||||
Reference in New Issue
Block a user