|
Why permissions?
An intelligent permissioning system allows platform administrators and users to
control, who should be permitted to access services and to view or create and edit information.
The Hierarchy:
For every factline Community Server (the server on which your platform runs),
there is a system administrator (sAdmin), one or several platform administrators (pAdmin) and one or
several write-permitted users.
sAdmin = factline If factline is used as the application service
provider (ASP), the system runs on a server powered by factline. In this case, factline takes over the
tasks of the sAdmin.
The sAdmin defines for each platform a group of platform administrators, who again
specify which groups of users may enter the different services. Finally every user can assign write and
read permissions for every piece of information (fact) they create.
Assigning Permission:
All permissions are assigned when creating and/or editing information. After you have click on the
"next>>" button on the add or edit input mask, a group overview is opened, where you can specify the
permissions. Here a pre-selection is offered to you, which you can accept directly, but you are not
required to.
The preselection is determined by your pAdmin.
General permissions
| read | Read-permitted groups can read, but not work on or hide text. |
| modify | Modify-permitted groups can write, work on, or delete text. |
Special permissions
post
(Forum) | Post-permitted groups can only reply to a
posting. Those users don't have the possibility of deleting or altering the title and description of a
forum. |
work
(for folders
in Structure) | Not every user should have
the permission to make changes in the structure-tree. Still, this user possibly should have the right
to put shortcuts in a specific folder. This is permitted with the "work" permission for that folder. |
|
|
proceed to: 