Skip to end of banner
Go to start of banner

Cross organisation ingest

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

This feature is part of release 25.2 and is intended for API integrators

Introduction

When an API integrator wants to upload objects for multiple organisations, a separate API user is required for each organisation. This procedure is cumbersome due to having to create and maintain multiple users. With the new cross organisation ingest feature, the API user will be able specify the target organisation when creating records.

Ingest

By using the property organisationId in the API method POST /records the user can choose a different organisation them their own organisation.

Linked concept

Description

Zone

Because zones are not shareable, the zone must be from the same organisation as the record.

Groups

  • The groups are determined by /wiki/spaces/CS/pages/4251942913

  • When the index is not shared, it will be filtered to only groups from the organisation of the record

Parent record

The parent can be from any organisation. However, if the index is not shared, the parent should be from the same organisation.

Restrictions

The following restrictions apply

  • The user must have the function ADMIN_EDIT_ALL_ORGANISATIONS

  • The organisation must not be special (monitor and _default)

  • When using Resumable Uploads the index must be shared between all organisations

  • No labels