After the s-admin has completed the initital set up of the platform,
according to the customer's specifications, and linked it with the
desired Internet domain, he/she turns the platform over to the platform administrator.
At this point, no one can create content on the platform, not even the p-admin, because no permissions have been assigned yet. Users can only register themselves and change their settings.
In this initial phase, the p-admin has to:
- create groups (e.g. customers, project groups, internal administration...)
- assign registered users to groups
- assign permissions to groups: Which group(s) should
have access to certain services?
Which group(s) should be allowed to create content on the highest level
in the structure hierarchy? Which group(s) should be allowed to read,
create content by default?
- structure the content of the platform (create folders,...)
- create a start page
- adapt e-mail templates (texts for the registration and the notification e-mail)
If desired, factline can support you in the beginning as a p-admin.
factline can take over the tasks
of the platform administrator in the beginning. In addition, we offer
advice on how to organise a platform.
As soon as the initial phase is completed, users can create and view content, get into contact with other users (ping, chat
) - provided they have been granted permission to do so.
As concerns the maintenance of the platform, the p-admin has to:
 continue with: Access to the p-admin interface
 return to: Roles of administrators and users
 table of contents
|
