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.
How It Works
Accessing the Organization Management Interface
Navigate to Settings in the left sidebar
Select Manage Organizations
The Organizations tab displays all parent organizations within your tenant
Click on any organization to view or edit its details and sub-organizations
Creating a Parent Organization
In Settings > Manage Organizations, click + Add New Organization
Complete the required fields:
Organization Name: A descriptive name for the parent organization (e.g., "North America", "Sales Division", "London Office")
Email Address: Choose the first part of the organization's email address. Docupath appends your tenant name and domain, producing an address like xyz-thetenantname@docupath.app, where xyz is what you type in.
Configure optional settings:
Urgent Flag: Enable to allow users to mark documents as urgent within this organization
Self-Service Access: Toggle to restrict user visibility to documents they upload or map to their organization (see related article for details)
Click Create
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.
Understanding Organization Hierarchy
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).
Configuring Organization Settings
Urgent Flag
The Urgent flag allows users to mark documents as high-priority. When enabled at the organization level, the Urgent option appears in the document upload interface. Urgent documents are flagged for expedited processing and appear at the top of review queues. Useful for time-sensitive contracts or expedited payments. To enable:
Open the parent organization
Check Enable Urgent Flag
Click Save
Self-Service Access
Self-service access restricts user visibility to their own documents. Admin users always see all documents regardless of self-service status. Non-admin users mapped to specific organizations see only documents uploaded to or mapped to those organizations. Non-admin users not mapped to any organization see all non-self-service documents. Risks of over-siloing must be carefully considered (see Known Limitations). To enable:
Open the parent organization
Check Enable Self-Service Access
Click Save See the "Configuring Self-Service Organization Access" article for detailed guidance on implementation and RBAC interaction.
Assigning Trading Parties to Organizations
Trading parties within a parent organization can be assigned to specific sub-organizations:
Navigate to Settings > Manage Organizations
Open the parent organization
Click the Trading Parties tab
Assign existing trading parties to sub-organizations, or
Create new trading parties directly within a sub-organization Each trading party belongs to exactly one sub-organization, ensuring clear accountability and scoping.
Email and Notifications
Each organization has an associated email address that is generated from the organization name (e.g., "xyz-thetenantname@docupath.app") but can be customised. The email is used for rejection notifications, approval workflows, and audit trail notifications. Ensure email address is monitored by the responsible team.
Auto-Generated Relationships
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.
Supported Configurations and Options
Feature | Supported | Notes |
Parent organizations | Yes | Up to 100 per tenant |
Sub-organizations per parent | Yes | Up to 100 per parent |
Organization naming | Yes | Descriptive names recommended |
Email customisation | Yes | Auto-generated; can be customised |
Urgent flag | Yes | Enable/disable per parent organization |
Self-service access | Yes | Optional; see related article for details |
Trading party assignment | Yes | Parties assigned to sub-organizations or parent directly |
Transformation rules scoping | Yes | Rules can be created at parent or sub-organization level |
Rejection rules scoping | Yes | Rules can be created at parent or sub-organization level |
Sub-organization override | Yes | Sub-org rules override parent rules at same scope level |
Self-service email notifications | Optional | Can be customised per organization |
RBAC mapping | Yes | User roles can be restricted to specific organizations |
Other Technical Specifications
Parameter | Specification |
Organization hierarchy | Parent with 0 to 100 child sub-organizations |
Max organizations per tenant | 100 parent organizations |
Max sub-organizations per parent | 100 |
Max trading parties per organization | Unlimited (system capacity dependent) |
Organization naming | Free text; 255 character limit |
Email field | Auto-generated or customisable; must be unique within tenant |
Urgent flag | Boolean |
Self-service access | Boolean; optional feature |
Rule groups per organization | Maximum 100 |
Rules per group | Maximum 500 |
Override scope level | Sub-organization rules override parent at same precedence |
Deletion | Organizations can be soft-deleted; documents remain accessible |
Notes and Limitations
Transformation Rules: Organization-scoped rules apply to all documents assigned to that organization
Rejection Rules: Organization-scoped rules enforce organization-specific compliance
Instruction Builds: Organization-specific instruction configurations determine document field mapping
Access Control: User roles mapped to organizations; users only see assigned organizations' documents (if self-service enabled)
Trading Party Management: Trading parties belong to organizations; relationships span organizations
Activity Logs: All organization changes logged with user attribution and timestamp
Sub-Organization Hierarchy: Parent settings inherited by child organizations; child rules override parent
Data Export: Organization context included in exported data; export templates can be organization-specific
Limitation | Workaround |
Two-level hierarchy only | No nested sub-sub-organizations; plan structure with parent and single child level |
No organization deletion | Organizations can be soft-deleted; documents remain in system; consider archiving strategy |
Trading party single-org assignment | Each trading party belongs to one organization only; use alternate names if party operates in multiple orgs |
Email uniqueness | Organization emails must be unique within tenant; ensure naming convention prevents collisions |
Self-service over-siloing | Enabling self-service can inadvertently silo data; carefully plan access control |
Default assignment ambiguity | If user is not mapped to any organization, they see all non-self-service docs; test access control thoroughly |
Parent rule inheritance complexity | Sub-org users may not understand inherited parent rules; document inheritance clearly |
Cross-organization relationships | Relationships can span organizations; ensure document routing rules account for this |
Email notification failures | If organization email is misconfigured, rejection notifications may not reach intended recipients |