Request Access Management

this view is available for admins, project managers, annotation managers and developers organizational request roles 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 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 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 shared overview 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 210,207,100,134,178,121,124 false true false center unhandled content type center false unhandled content type center false unhandled content type center false unhandled content type false center unhandled content type center false unhandled content type center false unhandled content type center false unhandled content type false center unhandled content type center false unhandled content type center false unhandled content type center false unhandled content type false center unhandled content type center false unhandled content type center false unhandled content type center false unhandled content type false center unhandled content type false center unhandled content type false center unhandled content type false center unhandled content type flexible workflows 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 210,207,100,134,178,121,124 false true false center unhandled content type center false unhandled content type center false unhandled content type center false unhandled content type false center unhandled content type false center unhandled content type false center unhandled content type false center unhandled content type false center unhandled content type center false unhandled content type center false unhandled content type center false unhandled content type false center unhandled content type false center unhandled content type false center unhandled content type false center unhandled content type experimental feature client qa 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 classic workflows in classic workflows there is an additional tab for the review flow 196,207,100,134,178,121,124 false true false center unhandled content type center false unhandled content type center false unhandled content type center false unhandled content type false center unhandled content type center false unhandled content type center false unhandled content type center false unhandled content type