Can I index one document with two sub-user IDs at the same time?

No, you cannot index a single document with two Sub-User IDs at the same time in RChilli’s Search & Match system. Here’s a detailed explanation of why this limitation exists and what alternatives you can consider:

Why Dual Sub-User Indexing Is Not Supported

1. Each Indexed Document Is Bound to One subuserid

• When using the IndexDocument or ParseAndIndex APIs, each document must include a single subuserid field.

• This subuserid is used to:

  • Segment documents for multi-tenant environments.

  • Retrieve, search, or delete documents tied to a particular user or organization.

If you attempt to include multiple sub-user IDs, the API will either reject the request or only index the document under one sub-user, potentially resulting in data access inconsistencies.

Workarounds & Alternatives

Option 1: Duplicate the Indexing Call

If two sub-users need access to the same document:

• Step 1: Make two separate API calls, one per subuserid.

• Step 2: Use the same resume or JD data in both calls.

• Result: The document will be indexed twice—once under each sub-user.

Note: This will consume double the indexing API credits.

Option 2: Use a Shared subuserid

If both sub-users belong to the same organizational unit:

• You can choose to assign a common sub-user ID for shared access.

• This simplifies access and avoids duplicate indexing.

Recommended for shared candidate pools or JD repositories.

Option 3: Replicate Results at the Application Layer

If indexing credits are a concern:

• Index the document under one subuserid.

• In your search UI or application layer, retrieve and duplicate the data for display to both users.

• This avoids duplicating backend storage but provides frontend visibility.

Important Considerations

• Indexed data is strictly segregated by subuserid for data privacy and multi-tenancy.

• There is no built-in "sharing" mechanism between sub-user IDs within RChilli’s API infrastructure.

• For long-term shared access, it's better to architect your app with group-level sub-user IDs.

Conclusion