Organizations in Docupath are configurable units that define the scope for transformations, rejection rules, instruction builds, and self-service access control. Parent organizations inherit configuration across all child sub-organizations unless explicitly overridden at the sub-organization level.

The organization is now created and available for assigning trading parties, creating organization-scoped transformation and rejection rules, managing access control via sub-organizations, and enabling self-service access if required.

Parent Organization A parent organization is the top level of the organization structure. It contains zero or more child sub-organizations, can define default settings inherited by sub-organizations, and defines the primary scoping boundary for rule precedence.

Sub-Organizations (Child) Sub-organizations are nested units within parent organizations. They inherit parent organization settings, can override specific settings at the sub-organization level, can have their own transformation and rejection rules that override parent rules, can be assigned to specific teams or departments, and cannot have child sub-organizations themselves (two-level hierarchy only).

The Urgent flag marks an organization's documents as high-priority. When it is enabled, incoming documents for that organization are flagged for expedited processing and appear at the top of review queues. Useful for time-sensitive contracts or expedited payments.

Marking an organization's documents urgent requires the Priority Queue permission, separately from access to the Manage Organizations module. Without it, the toggle is greyed out, not hidden.

To enable:

Self-service access limits document visibility to the users mapped to an organization. Admins and managers have tenant-wide access and always see all documents regardless of self-service status. Other users mapped to specific organizations see only documents uploaded to or mapped to those organizations, and users who are not mapped to any organization see all documents from organizations that do not have self-service enabled. The organization itself still appears in the organization list used by filters, which every user can see. Risks of over-siloing must be carefully considered (see Notes and Limitations). To enable:

Data Processing Pro is the organization's billing tier. When it is on, every document from that organization is billed at twice the standard Data Processing rate. It affects billing only and changes nothing about how documents are classified, extracted, reviewed, or exported.

Changing the tier requires the Admin role. Managers can see the setting but cannot change it.

To enable:

Sub-organizations are billed on their parent's tier.

Trading parties within a parent organization can be assigned to specific sub-organizations:

Each organization has an associated email address that is generated from the organization name (e.g., "xyz-thetenantname@docupath.app") but can be customized. The email is used for rejection notifications, approval workflows, and audit trail notifications. Ensure email address is monitored by the responsible team.

When trading parties are assigned to organizations, Docupath automatically creates relationship records. A trading party in one sub-organization can relate to parties in other sub-organizations. Relationships are created automatically when documents are processed involving parties in different organizations and can be viewed in Activity > Trading Party Relationships.