Skip to main content

Organisation Roles

Every member of a Kazinex organisation is assigned an organisation role that defines their baseline capabilities across the platform. This role applies organisation-wide, regardless of which project they are in.

Role overview

RoleForKey capability
org_adminIT admins, senior document control managersFull control — everything
org_managerProject directors, department managersManage members and projects
memberRegular team membersDefined by project role
workflow_responderExternal reviewers, contractorsRespond to assigned steps only

org_admin

The Org Admin has unrestricted access to all features across the organisation.

Can do everything, including:

  • Create, edit, delete, and archive any project
  • Manage all organisation members (invite, role change, remove)
  • Configure all organisation settings: branding, security, storage, metadata, webhooks, mail configuration
  • Access and manage all documents, workflows, correspondence, and transmittals in any project
  • View and export the audit log for any project or organisation
  • Manage billing and subscription settings
  • Access the Super Admin panel (if enabled)
  • Grant and revoke Org Admin to other members

When to assign: Senior document control managers, IT administrators, or the person responsible for the overall Kazinex implementation. Keep the number of Org Admins to a minimum (typically 1–3 per organisation).


org_manager

The Org Manager can manage members and projects but cannot access billing or the most sensitive settings.

Can do:

  • Invite members and change their organisation roles (up to org_manager — cannot grant org_admin)
  • Create new projects and assign project teams
  • Access all projects as if they were a Project Admin
  • Configure organisation settings except: billing, subscription, and Super Admin functions
  • View the organisation-level audit log

Cannot do:

  • Manage billing or subscription details
  • Grant or revoke org_admin role
  • Access Super Admin features

When to assign: Project directors, PMO leads, or department managers who need to create and oversee projects but should not have billing access.


member

Member is the standard role for regular team members. A member's actual capabilities within a project are determined by their project role in that project.

At the org level, a member can:

  • Log in to Kazinex
  • View their profile and notification preferences
  • Access projects they have been explicitly added to
  • Accept invitations to projects

Cannot do at the org level (without a project role):

  • Create projects
  • View other members' details
  • Access any project they have not been invited to
  • Change any settings

When to assign: All regular team members — engineers, coordinators, document controllers, subcontractor contacts.


workflow_responder

Workflow Responder is a special role for external parties who need to respond to workflow steps but should not access the broader platform.

Can do:

  • Log in to Kazinex
  • View workflow steps assigned to them and take actions (approve, review, acknowledge, sign)
  • View the documents linked to their assigned steps
  • Leave comments on their assigned steps

Cannot do:

  • Browse the Document Register
  • View the Correspondence or Transmittals hub
  • Access Reports
  • View other workflows not assigned to them
  • Create documents, correspondence, or transmittals

When to assign: External design consultants, contractor representatives, or client reviewers who need to respond to approval requests but should not see your internal project content. More restrictive than Reviewer (project role) — ideal for parties outside your organisation.

Cost note: Workflow Responders may have different licensing implications than regular members. Check your plan details.

Changing organisation roles

  1. Go to SettingsMembers (Org Admin only).
  2. Find the member.
  3. Click their current role badge.
  4. Select the new role from the dropdown.
  5. Confirm.

Role changes take effect immediately. The member's active sessions are not terminated — they see the new permissions on their next page load.

What's next