Request Access Management
This view is available for Admins, Project Managers, Annotation Managers and Developers.
During the lifetime of a request, several users and organizations collaborate on it. Organizational request roles control the access that organizations' users have to different information and actions in requests. So far, there are two roles: Producer and Owner.
Producer is the only explicit role for now. The Producer organization has the most access to a request's actions. Its users can:
- Add team members of all responsibilities
- Expire and assign all types of tasks
- Reject Delivery-Ready annotations
If your organization ordered data from Kognic, then Kognic is the Producer. If you use the platform to produce data yourself, your organization has the Producer role.
As shown on the top of the page, check the request header to verify your organization's role in the request.
Owner is an implicit role of the organization under which the project and request are located in the platform. Usually, this is the organization that uploaded the data and the one that will be consuming the final data. Its users can:
- Monitor the general progress of the request and its inputs
In phases where they have review access:
- Add Review team members in Phases
- Expire Review tasks of their users
- Assign Review tasks to their users
There are some differences when it comes to access between Flexible Workflows and Classic Workflows, but share the general overview tabs. These are summarized in the table below
Tab | Owner | Producer | Documentation |
---|---|---|---|
Summary View progress | β | β | ο»ΏSummaryο»Ώο»Ώ |
Inputs View list of inputs with their status | β (In workflow stages with owner access) | β ο»Ώ | ο»ΏInputsο»Ώο»Ώ ο»Ώ |
Tasks View list of tasks, to-do, in-progress or completed | β (In workflow stages with owner access) | β | ο»ΏTasksο»Ώο»Ώ |
Team Manage your request workforce and their responsibilities | β (In workflow stages with owner access) | β | ο»ΏTeamο»Ώ |
Apart from the shared general overview tabs, Flexible Workflows also contains one tab per phase. Owner/Producer access is handled per phase and is summarized in the table below
Tab | Owner | Producer | Documentation |
---|---|---|---|
Annotate Monitoring of the Annotate phase | β | β | ο»Ώ |
Review Monitoring and management of the Review phases | β (Unless Client QA is enabled for the phase, see below) | β | ο»Ώ |
Delivery Monitoring and management of the Delivery phase | β | β | ο»ΏDeliveryο»Ώ |
A Sampled Review Phase can be designated as a Client QA phase, where the Owner can manage their Review activity.
If Client QA has been enabled for a phase, the Owner in that request will have elevated privileges in that phase, similar to those in the Delivery phase.
A PM from the Owner organization can then assign their users to the Review action in that phase and manage tasks related to the Review action.
In classic workflows there is an additional tab for the Review Flow and possibly one for Exam Configuration
Tab | Owner | Producer | Documentation |
---|---|---|---|
Review Overview of reviews progress and task acceptance/rejection | β When review flow is used | β | ο»ΏReview monitoringο»Ώ |
Exam Configuration Configure Campus Examinations | β | if part of license | ο»ΏExam Configurationο»Ώ |
ο»Ώ