Organizations are the structural backbone of a Docupath tenant, defining how documents are routed, how rules are scoped, and how user access is controlled. Docupath uses a two-level hierarchy - parent organizations and sub-organizations - to model real-world business structures such as holding companies, regional branches, departments, or external partner entities.
Every instruction build, transformation rule, and rejection rule can be scoped to a specific organization, making the organization model the primary mechanism for applying targeted business logic at scale.
How It Works
Organization Hierarchy
Docupath tenants are structured into parent organizations and sub-organizations:
Parent Organization: Represents the main entity (e.g., a company or holding group). It defines the core inbox, rules, and access settings. When it is created, a unique email address is configured for document ingestion on the docupath.app domain.
Sub-Organization: Sits under a parent and represents branches, departments, regions, or subsidiaries. Sub-organizations inherit settings from their parent but allow granular overrides for rules, trading parties, and access controls.
Organization Creation
When creating a parent organization, administrators define the organization name and configure three optional behavior flags:
Urgent Flag: Marks all incoming documents from this organization as high priority
Self-Service Access: Restricts document and user visibility to mapped users only - ideal for external partners or sensitive workstreams
Split documents from this organization: Turns on automatic document splitting for documents arriving under this organization. A file that contains several business documents is separated into one document per part, each processed on its own. See Document Splitting.
Sub-organizations require a name and email, and inherit the parent's Urgent, Self-Service, and split-documents settings, which can be overridden at the sub-organization level.
Override Trading Party
A sub-organization can assign one of its trading parties as the overriding trading party. When enabled, every document routed into that sub-organization automatically has its Primary Party set to the override value - regardless of what the document itself states. This ensures consistent party assignment for organizations that process documents on behalf of a single entity.
Self-Service Access
When self-service is enabled on an organization:
Users mapped to that organization see only documents they uploaded or those assigned to the organization
Its documents are not visible to non-admin users who are not mapped to it. The organization itself still appears in the organization list used by filters, which every user can see
Admins retain full visibility across all organizations, including self-service ones
Who Can Manage Organizations
Creating and editing organizations requires the Manage Organizations module. Navigation follows read access, so Manage Organizations appears in the menu only for roles that can at least view it.
Two settings on an organization have their own access:
Marking documents urgent requires the Priority Queue permission. Without it the toggle is greyed out, not hidden.
Data Processing Pro sets the organization's billing tier. It bills every document from that organization at twice the standard Data Processing rate and changes nothing about how documents are processed. Admins can change it and Managers can view it.
How Organizations Power Automation
Once defined, organizations become scoping boundaries for the entire business logic layer:
Feature | How Organization Scoping Works |
Instruction Builds | Apply extraction logic specific to each organization's document patterns |
Transformations | Define formatting and value manipulation rules per organization |
Rejection Rules | Block non-conforming documents from specific organizations |
Enrichment | Autofill fields using saved organization identifiers and trading party data |
Supported Configurations and Options
Configuration | Detail |
Parent organization fields | Name, Urgent Flag, Self-Service Access, Split documents from this organization, Data Processing Pro |
Sub-organization fields | Name, Email, Urgent (inherited), Self-Service (inherited), Split documents (inherited), Override Trading Party |
Document splitting | Off by default; set per organization and per sub-organization. Changing it on a parent updates every sub-organization still following the parent |
Self-service visibility | Admin: all organizations visible; Non-admin mapped: only assigned orgs; Non-admin unmapped: all non-self-service orgs |
Email address | Configured per parent and sub-organization for email ingestion; must be unique and will follow the format |
Override trading party | Assign one trading party per sub-organization as automatic Primary Party |
Module access | Manage Organizations. Admins and managers have it, and a custom role can be granted read or write |
Urgent marking | Requires the Priority Queue permission |
Data Processing Pro | Billing tier for the organization. Bills every document at twice the standard Data Processing rate and changes no processing behavior. Admin can change it, Manager can view it |
Other Technical Specifications
Parameter | Limit |
Maximum organizations per tenant | 100 |
Maximum sub-organizations per organization | 100 |
Maximum instruction builds per organization | 100 |
Maximum rule groups per organization | 100 |
Maximum field lengths | Organization name 150, receiver name 100, attachment email 254, alternate organization name 150 characters (see Platform Limits and System Requirements) |
Notes
If organizations are not set up correctly, documents may fail validation or visibility checks
Organization-scoped rules sit between Country and Trading Party in the rule precedence hierarchy
API uploads must include the Sub Organization ID to route documents to the correct organization
Self-service access restricts non-admin document visibility - combining it with role-based access is recommended for layered security. A role decides which modules and actions a user gets; organization mapping decides which documents they get
Marking an organization's documents urgent requires the Priority Queue permission, separately from access to the Manage Organizations module
Override trading party applies to all documents in the sub-organization without exception; it cannot be conditionally applied
Email ingestion to the parent organization requires Primary Party matching for sub-organization routing - if no match or multiple matches occur, the document is flagged as "No sub organization detected"
Organization names should be unique and descriptive; ambiguous names can cause confusion in rule scoping and reporting
Deleting an organization does not delete its associated documents, but prevents new document routing to it