Roles & permissions

organization roles in an organization , a user can have one or several of the following roles member , time reporter , time report manager , team manager and admin the table below describes the high level access (in terms of features and actions) granted to each role organization roles control organization level features and actions these are configured from docid\ xsnwyhqvd7uqphl1iglgn member time reporter time report manager team manager admin my tasks ✅ ✅ ✅ ✅ ✅ campus ✅ ✅ ✅ ✅ ✅ peer productivity ✅ ✅ ✅ ✅ ✅ user productivity ✅ ✅ ✅ ✅ ✅ my performance ✅ ✅ ✅ ✅ ✅ team management ❌ ❌ ✅ ✅ ✅ teams ❌ ❌ ❌ ✅ ✅ productivity insights ❌ ❌ ❌ ✅ ✅ idle members ❌ ❌ ❌ ✅ ✅ manage team reports ❌ ❌ ✅ ❌ ✅ organization administration ❌ ❌ ❌ ❌ ✅ user management ❌ ❌ ❌ ❌ ✅ report time ❌ ✅ ❌ ❌ ❌ workspace roles in a workspace, a user that is part of the organisation that owns the workspace can have one or several of the following roles member , annotation manager , project manager , developer and admin if a user is part of an organisation that has been invited as a collaborator to the workspace, the roles available to them will depend on the collaboration type assigned to their organisation how workspace roles relate to collaborator types are described in https //docs kognic com/collaborators#cqurk the table below describes the high level access (in terms of features and actions) granted to each role workspace roles control workspace level features and actions these are configured from docid\ ybgkk5zawzvfuhnd9sq l whether someone can access request level features and actions will depend on their organisation's assigned https //docs kognic com/request details#kwyun in the specific request member annotation manager project manager developer admin receive tasks ✅ ✅ ✅ ✅ ✅ project management ❌ ✅ ✅ ✅ ✅ create projects ❌ ❌ ✅ ❌ ✅ create request ❌ ❌ ✅ ❌ ✅ request ❌ ✅ ✅ ✅ ✅ annotation instructions ❌ ❌ ✅ ✅ ✅ data orchestration ❌ ❌ ❌ ✅ ✅ scenes ❌ ❌ ❌ ✅ ✅ integrations ❌ ❌ ❌ ✅ ✅ workspace administration ❌ ✅ ✅ ✅ ✅ workspace settings ❌ ❌ ❌ ❌ ✅ members ❌ ✅ ✅ ✅ ✅ collaborators ❌ ❌ ✅ ✅ ✅ api credentials ❌ ❌ ❌ ✅ ✅ faq why can’t a user see project management or request details even after being added to a workspace? adding the user as member of a workspace is not enough make sure that the following conditions are true the organization that the user belongs to are added as a docid\ cqcqf1jwpzoh14g580 b0 with type annotation partner , producer partner or data partner the organization has https //app archbee com/docs/a z2x5g73vsvy af9audr/cqcqf1jwpzoh14g580 b0#uwtb1 configured for the relevant project the organization is added as a request producer of the request the user is assigned the workspace role annotation manager , project manager or developer