Each level carries a stable internal ID, so renaming labels (for example, updating an Entity name after a rebrand) does not break user access or historical data.

Why Does This Matter for the API?

The DataServ API requires that your account is on the new Organization Structure model. This is because the API routes data based on your hierarchy and ERP associations. Without Organization Structure in place, the API cannot correctly map inbound or outbound data to the right part of your business.

If you are currently using SFTP-based file integration and want to move to the API, Organization Structure setup is a prerequisite for that migration.

What Changes for You?

Once Organization Structure is configured, you gain several benefits beyond API access:

• User security tied to your business hierarchy, so people only see documents for the parts of the business they are responsible for.

• Cleaner multi-ERP support, with each part of your organization correctly associated with the right ERP.

• Better document metadata and reporting, with Region, Entity, Operating Unit, and Location fields on every document.

• A foundation for future capabilities that depend on structured organizational data.

What You Need to Provide

Setting up Organization Structure is a joint project. Your team provides the business model; DataServ handles all technical configuration. Here is what we need from you:

1. Your hierarchy: Regions, Entities, Operating Units, and Locations that reflect how your business is organized.

2. IDs and codes: Any existing ERP company codes, location IDs, or organizational codes you already use.

3. ERP mappings: Which parts of your structure belong to which ERP (relevant for multi-ERP clients).

4. Any special considerations: Legacy entities that should remain for historical access, or upcoming organizational changes.

We provide a template to make this straightforward. Your CSAM will walk you through it.

What DataServ Handles

You do not need to perform any technical configuration. DataServ will:

• Review your proposed hierarchy and ERP mappings.

• Configure or import your Organization Structure in the DataServ platform.

• Validate data routing and ERP assignments.

• Coordinate testing with your team to confirm user access and document flows work as expected.

• Plan go-live timing and agree on how future changes (new locations, entities, etc.) will be requested.

Next Steps

Ready to get started? Here is the path forward:

1. Reach out to your Client Success Account Manager (CSAM) or email DataServ Support at support@dataserv.com.

2. Let us know you want to set up Organization Structure (and whether this includes API migration, multiple ERPs, or both).

3. We will share the hierarchy template for your team to complete.

4. DataServ configures everything and coordinates testing with you before go-live.

Questions? Reach out to your CSAM or email support@dataserv.com.