Frequently Asked Questions

Q. When configuring 3Sixty the docs all suggest using the 3Sixty Admin UI - is there a way to configure Objective 3Sixty through code?

A. Objective 3Sixty jobs can be created and configured using API calls. We provide a comprehensive set of admin APIs to accomplish that.

Q. The plan is to install 3Sixty on a VM and run redaction tasks - what specs do you recommend?

A. Sizing recommendations will be provided in the design document based on

  • Throughput & volumes of documents

  • Avg/Max document size

  • Other requirements like OCR, document conversion, etc.

Q. What would admins/users need to do to log in to an Objective 3Sixty instance, using IP address or localhost?

A. Suggest using a DNS alias & certificate – not localhost or IP address. This will be covered in the technical design document.

  • Docker deployment info can be found in the standard help files, although is out of date – an update has been requested from Product. 

  • Authentication can be:

Q. When using Objective Redact with 3Sixty, the documentation mentions the redaction task, but there is also an OpenAI chat completion task for redaction. Which task do you recommend for redaction?

A. The 3Sixty Redaction tasks are not required.

  • 3Sixty will create a target file for document redaction via the OpenAI Chat task.

  • The target file will contain all redaction terms found by the OpenAI Chat task based on the prompt provided. Note this may require several rounds of refinement to get the desired output.

  • Redaction is then completed via Objective Redact not 3Sixty. This is a manual task which involves loading the source document and target redaction file into Redact and confirming all required terms have been located.

Q. To use AI redaction, does an AI embeddings task need to be used before the redaction task can be used?
A. AI Embeddings tasks are not needed.

Q. For AI redaction, is there a way to use a locally-installed LLM (such as Llama)? Or to point to an LLM hosted elsewhere (such as Azure Open AI)?

A. You can use any OpenAI compliant LLM, either installed locally, or cloud hosted.

  • 3Sixty only requires an endpoint and an API key.

  • Note: Azure Open AI is a slight exception as it differs from other Open Source OpenAI models and would need a small product uplift to work.

  • LLM options:

    • Cloud Based: can be an option if passes security considerations

    • On-Premise: If compliance or security considerations mean data cannot leave the environment, we suggest using an open-source GPT model deployed locally

    • Recommended model is GPT OSS  https://openai.com/index/introducing-gpt-oss/

    • This can be deployed via a GPU-supported Docker-based setup (e.g., Ollama - https://hub.docker.com/r/ollama/ollama , allowing full control over data and processing.

    • Ollama already supports gpt-oss - https://ollama.com/library/gpt-oss

    • Running this model on-premise would require approx. 100GB of RAM for the GPU

Q. The plan is to perform redaction of PDF documents. Do you recommend that PII Detection or Trivial Detection are also used in addition to the redaction task? Or would the redaction task be enough by itself?

A. The OpenAI chat task can be used to find PII as well as other suitable text for redaction – there should be no requirement to also use the 3Sixty PII Task, which is regex based.

  • The 3Sixty Trivial task filters documents out based on age or type – it can optionally be added to the jobs if useful but is not required.

  • Non-AI PII detection is supported in Objective Redact directly - so you can apply this in addition to the AI-generate target file if useful.

  • The output of the OpenAI Chat task is a Redact Target file containing all the text to be redacted from that particular document.

  • The document and the target file can then be loaded into Objective Redact for manual confirmation and completion.    

Q. Can 3Sixty track deletions in X source system and delete them in X target system?
A. No. 3Sixty does not currently have any method to track deletions (or movements) in any system beyond auditing specific API calls. As of now, except in very rare cases around version reconciliation and Records Management, 3Sixty does not delete documents.

Q. Some 3Sixty/Discovery page is displaying odd behaviour or breaking after patching / updating
A. This is likely due to JavaScript being cached by the browser. Try hitting Control / Command + Shift + R. If that doesn't work try some options found here.
How to hard refresh your browser and clear your cache.

Q. Can 3Sixty only read documents that have been modified since the last time the job was run?
A. That would be an Incremental Job type.

Q. Help! My job isn't reading any documents, but I know they're in there!
A. In your job, under the Details tab, make sure the start and end times are wide enough to capture the modified dates of the documents you wish to read in.
See the Integration Job Overview page for more detail.

Q. Help! My documents are coming over as 0 bytes!
A. In your job, under the Details tab > Advanced Options, make sure Include Binaries is checked.
See the Advanced Options Section of the Integration Jobs Overview page for more details.

Q. My search views are not showing up. I'm only able to see the home page.
A. Check the security settings of the content views. Certain users or user groups may have been restricted from seeing certain search views.

Q. My login for Discovery isn't working.
A. Look at the user roles set up in the user management section of 3Sixty to be sure that the user is set up with the correct level of access to Discovery and if need be to Records Management. Also see instructions for setting access via User Groups.

Related Articles:

Contact 3Sixty for Support

3Sixty Integration Tutorials