Restricting Access of the Agentic Task - Restricting Access of the Agentic Task - Authentication support for Agentic Tasks can be used to restrict access to repository content during content extraction. This prevents an Agentic Task from accessing content even when a content reference is provided, helping enforce repository security and prevent unintended access to documents. - Content Innovation Cloud - Hyland Automate Modeler - Current/Hyland-Automate-Modeler/cis3440473445354 - Current - Current

Hyland Automate Modeler

Platform
Content Innovation Cloud
Product
Hyland Automate Modeler
Release
Current
License
ft:lastPublication
2026-11-16T23:02:28.533499
ft:locale
en-US

Authentication support for Agentic Tasks can be used to restrict access to repository content during content extraction. This prevents an Agentic Task from accessing content even when a content reference is provided, helping enforce repository security and prevent unintended access to documents.

By default, Agentic Tasks can access repository documents when a valid content reference is provided. Restricting access is an optional security feature.

When authentication is configured, the Agentic Task authenticates using a designated service user or internal user. Document access is evaluated using that user's permissions. The Agentic Task can only extract content from documents visible to the authenticated user.

The following authentication methods can be used to restrict Agentic Task access:

    • OAuth 2.0 Client Credentials

    • Bearer opaque token

These authentication methods allow the Agentic Task to run as an Internal User or Service User. Access to documents is then limited to the content available to that user.

To restrict the Agentic Task access:

  1. Use the Administration Portal to create a service user. For more information, see Creating a Service User in the Content Innovation Cloud Administration Portal documentation.
  2. Assign the service user to a regular user group with the required permissions. The group should not have administrator privileges.
  3. Save the name of the application given to the group in the Administration Portal. It will be used for credentials in next steps.
    Note: Client ID and Client Secret will be used for authentication. Client ID is always visible, but Client Secret is only shown once. If you lose it, you will need to navigate to the previously created application to regenerate it.
  4. Go to the External Systems > External Applications tab and set the following scopes for the application that was created:
    • hxp
    • hxpr
    • hxps
  5. Proceed to Workspace and open the project in which you want to use the Agentic Task.
  6. Locate the files to which you want to grant the Agentic Task access to.
  7. Grant appropriate access level to the user group to which your service user was added. For more information, see Managing Document Permissions in Hyland Workspace.
  8. Go back to Studio Modeler and open the process with the Agentic Task.
  9. Add the new authentication type that you want to use. For more instructions, see Authentication Configurations.
  10. Go back to the process and select the Agentic Task.
  11. From the Properties pane on the right, apply the newly created authentication type to your Agentic Task.
    Note:

    When the application is deployed, you will need to provide the credentials from External Application. Besides the Client ID and Client Secret, provide also the application endpoint from the correct environment: it is the[application-address]/idp/connect/token, for example: myapplication.hyland.com/idp/connect/token.

  12. Save the project.
After deployment, the Agentic Task can access only the documents permitted to the configured user or service account, helping prevent unintended document access and security breaches.