Administrator
What is the function of an Administrator?
Administrators are responsible for managing the Enterprise settings and ensuring the members can perform their tasks. This will emphasis the role of Administrator.
As an Administrator, following actions can be performed in the Enterprise.
Create/Move/Delete Groups
Create/Edit/Delete Template DataBase
Create/Edit Settings
Create Lifecycle
Create/Move/Disable/Reset Members
Assign Roles to Members
Create User Sets
Create Task Queues
Key concepts
Hierarchy: Tree-based representation of a Business Organisation, where user's location define what they can or cannot access in an Enterprise.
Enterprise : A hierarchy of members, data and application configurations for a business.
Group : Structuring element of the Enterprise that gathers members in a given Hierarchical position with roles and authorization.
Template DB : Repository in which Published Templates are stored.
Style : Set of functionalities that allow to customize an Enterprise.
Lifecycle : Defining the publication process for Templates.
Member : User of FieldLogs.
Roles : User attributes that define the access to interface elements, data and/or actions in FieldLogs.
Task queue : Logical member-based groups in which members can pick up and/or assign tasks.
User set : Custom group of members defined according to their hierarchy, their group and/or their role.
Access right : Rule that defines the level of access to a securable object.
Securable object : Key element of the internal data structure or of the graphical interface of FieldLogs (section, job, template, object) to which a specific access right is given in the context of a role.
Security rule : Combination of a securable object and an access right.
Setting up a Hierarchy
Administrator is the first member of the Enterprise and belong to the Root Group. The first action is to create the Hierarchy. The hierarchy must be carefully designed as it is not recommended to move/delete the elements of the hierarchy such as Groups, Members or Template DB.
The Parent Group can comprise of many Child Groups as shown below.
The Template DB is attached to a Group, which determines its place in the hierarchy of the Enterprise and determines the published templates accessing rights.
Settings can be added to the Group to customize the look and feel of the Enterprise.
A Group comprises of several users/members who are assigned Roles in the hierarchy.
The first step is to Create Groups to build the Hierarchy.
Template DB is a repository of Published Templates. Add a template DB at the root of your Organization. All the Members of the Group will have access to the Templates stored in that Template DB.
Before being published in a Template DB, a Template goes through several steps of validation called a Lifecycle. The Lifecycle defines the steps involved in the Template publication process. In addition to the Standard static Lifecycle for content approval, FieldLogs also allows you to design a dynamic Custom Lifecycle to edit, review, publish, and test Templates.
Then, to customize the Enterprise, Add a Setting to the root group. In the Styles panel, you can replace the default logo with the logo of your company, change the colors of the interface and replace the labels of buttons and sections with the vocabulary used in your enterprise.
Next step is to create members in the Enterprise. To Create Members you must define their login, Password and Assign the Role to the Member.
You can either use the predefined roles, or create your own roles. The roles define the access rights of the members.
After creating members and assigning roles, next is to create user sets. A User set is a collection of Members from different Groups in the Hierarchy.
User sets are used to create Task Queues. Task Queues assigns Task to the users.
On the long run, you will have to manage the security aspect of your enterprise and solve issues of access. You can modify the roles of course, but data bridges and security exceptions are two tools that will help with temporary or permanent issues.