Kavi Help CenterKaviŽ Status Tracker Help
| Appendix H. Default User Types and Project Relationships | ||
|---|---|---|
 |
Part VI. Appendix | 
|
Table of Contents
These tables describe all the Relationships and User Types that provide access to Kavi Status Tracker tools. This includes Project Relationships and User Types installed by Kavi Status Tracker by default, and default User Types installed by KaviŽ Members that provide access to Kavi Status Tracker tools.
A Project Relationship is a relationship between a user or a group of users. Project Relationships are added through the Kavi Status Tracker tool.
User Types and roles are managed and assigned through Kavi Members tools, and the Kavi Members Concepts documents provide extensive information on types and how types can be used to confer roles and access privileges. Types that are required by the application cannot be deleted or edited. For more information, see Kavi Members help.
Individual-to-project or group-to-project relationships are established through project data lookup fields. The following table presents the default relationships, but these are not necessarily in use by your organization. Your organization may have other lookup fields that define individual-to-project or group-to-project relationships. They are likely to share many of the characteristics and behavior of the default project relationships.
Table H.1. Project Relationships
| Name | Relationship | Description |
|---|---|---|
| Project Recorder | An individual-to-project or group-to-project relationship |
Options available in the Configure Kavi Status Tracker Super Admin tool allow status tracking tasks to be shared with users who have some kind of of relationship to a project. This kind of user is known as a Project Recorder. Project Recorders have access to Member Area tools used to track a project and project activities. They have permission to set the Project State and other project data, and manage the project's activity schedule. To enable distributed management, an individual-to-project or group-to-project relationship must be established by the addition of a project data lookup field. The default examples are the individual-to-project relationship 'Project Editor' and the group-to-project relationships 'Owning Group' and 'Consensus Body'. An individual-to-project relationship gives Project Recorder access to an individual selected from the Kavi Members database. In a group-to-project-relationship, the 'Group Chair' and 'Document Manager' (i.e., any group member with document management privileges) of a group selected from the Kavi Groups database are given Project Recorder access. On sites where no individual-to-project or group-to-project relationship is enabled, only the Status Tracker Admin and Status Tracker Super Admin have administrative access to projects. |
| Project Editor | An individual-to-project relationship |
This relationship is established through a data lookup field that is tied to the KaviŽ Members database. The 'Project Editor' is the person who is allowed to edit the project specification or other document deliverable. This designation may be merely semantic in Kavi Status Tracker or the 'Project Editor' may be designated as a 'Project Manager' in the Configure Kavi Status Tracker tool. |
| Owning Group | A group-to-project relationship |
This relationship is established through a data lookup field that is tied to the KaviŽ Groups database. The 'Owning Group' is the group in which project work is being performed. This designation may be merely semantic in Kavi Status Tracker or the 'Group Chair' and 'Document Manager' of the 'Owning Group may be designated as 'Project Managers' in the Configure Kavi Status Tracker tool. |
| Consensus Body | A group-to-project relationship |
This relationship is established through a data lookup field that is tied to the KaviŽ Groups database. The 'Consensus Body' is the group responsible for final approval of the project by the organization. Depending on the organization, this may be the technical committee, all voting members or the board. This designation may be merely semantic in Kavi Status Tracker or the 'Group Chair' and 'Document Manager' of the 'Consensus Body' may be designated as 'Project Managers' in the Configure Kavi Status Tracker tool. |
Kavi Status Tracker User Types confer roles that grant administrative access. These types can be assigned through Kavi Members Add a User and Edit a User tools.
Table H.2. Default User Types
These User Types and Contact Types are automatically added by Kavi Members and can be viewed and assigned to users though Kavi Members tools.
Table H.3. Kavi Members types with Kavi Status Tracker access
| Type | Default role | Description |
|---|---|---|
| Organization Admin | org_admin | The Kavi Members User Type 'Organization Admin' has access to the Admin and Reports Areas and tools in all applications, including the Kavi Status Tracker. 'Organization Admins' can add, edit and delete projects and activities, and generate reports. |
| Report Admin | report_admin | The Kavi Members User Type 'Report Admin' has access to the Report Areas of all Kavi applications including the Kavi Status Tracker Reports Area and tools. |
| Super Admin | super_admin |
This User Type has complete administrative access to the website, including Kavi Status Tracker Super Admin, Admin and Reports Areas. 'Super Admins' can configure Kavi Status Tracker; add, edit and delete projects and activities; and generate reports. |
|
|
 |
|
| Appendix G. Kavi Status Tracker Default Roles |  |
Appendix I. Organization-Wide Project Views |