Yes, you can restrict document access between sub-users in RChilli, but the process depends on how your system and API access are configured.
🔐 Restricting Access Between Sub-Users
RChilli provides the concept of sub-user IDs as part of its API request structure. Each API request (e.g., resume parsing) includes a parameter called subuserid
. This ID helps uniquely identify and manage requests by different sub-users under the same parent account.
✅ How This Restriction Works:
-
Each sub-user has a unique
subuserid
, which is passed in API calls. -
Data parsed or indexed under a specific
subuserid
is logically isolated. -
You can prevent sub-user A from accessing documents or search results of sub-user B by:
-
Keeping
subuserid
values unique and non-overlapping. -
Not sharing the same
userkey
or allowing cross-subuserid use in the front-end or API calls.
-
🔒 How to Enforce These Restrictions
-
Use separate
subuserid
values for each sub-user when configuring API requests. -
In Search & Match, ensure that:
-
Documents indexed under
subuserid=A
are not queried usingsubuserid=B
. -
The
DeleteAllDocuments
,ParseAndIndex
, andResumeSearch
APIs respect sub-user boundaries.
-
-
My Account Portal visibility and data access can also be restricted based on user credentials and assigned roles.
-
If you are using Browser Assistant or Oracle Extension, configure user access and environment using the “Add Users” and “Assign Roles” features inside the Oracle Client Panel.
🧩 Example Scenario
If User A parses and indexes resumes using:
And User B uses:
Then:
-
Searches performed using
userB_subid
will not return results fromuserA_subid
, assuming APIs and credentials are isolated properly. -
No overlap in document access occurs unless the same credentials or shared subuserid are used.
👨💻 Need Help Configuring?
If you're unsure how to structure this setup or need help applying restrictions in your system, you can:
-
Contact support@rchilli.com
-
Refer to the Resume Parser API Authentication Guide
-
Use My Account Portal to view current user keys, sub-user IDs, and access controls.
Comments
0 comments
Please sign in to leave a comment.