Organization Tab

Introduction

Settings on the Organization Tab allow the PSIfusion environment to be customized to meet the needs of your organization.

General Section

Name

The organization name is for administrative purposes and is not displayed to users. This refers to either the name of your company, organization or department.

In future releases the name may be used to differentiate between organizations on a single server or server cluster.

Storage Section

PSIfusion uses a file system based data store to monitor and manage documents, including document images, metadata, visualization data and workflow state.

Storage Path

The storage path defines where PSIfusion will store all documents for the organization.  A number of sub-folders will be created within the storage path, each with a distinct purpose:

FolderDescription
IncomingDocuments in the Incoming folder are waiting for processing before being added to a queue
QueueDocuments in the Queue folder have been imported into PSIfusion and added to a queue, pending processing
CompleteDocuments that have been indexed and completed are moved from the Queue folder to the Complete folder
InvalidDocuments that fail to import from Incoming, or otherwise fail to load from a Queue folder will be moved to the Invalid folder

Options Section

The options section includes settings that modify the user experience, establish document security, and enable and configure Teams.

Session Timeout

The session timeout setting allows administrators to specify how long a user may remain idle before their session will be closed.  PSIfusion sessions are created when a user successfully logs into the system, and the last activity for each session is monitored and recorded as the user progresses through the user interface.  Each action the user takes that involves a call from the client browser application to the server will update the session's last activity time.  Once a user's time between activities exceeds the session timeout the session is closed and the user will have login again when they return to the application.

Document Type Field Name

Internally, PSIfusion uses the term Document Type to describe a particular classification of document, and it's associated metadata and indexing requirements.  In cases where the organization uses an alternate term for this functionality, this setting will allow an administrator to change the label used in the client side application.  This allows you to configure the mandatory document type selection field such that it can serve more than one purpose, by associating the field with a domain concept that is specific to your organization or solution.

Example

In a default PSIfusion configuration, the document type field would be displayed as follows:

If your organization is creating one document type for each department, and using PSIfusion to index those documents and route them to the department; you could rename the document type field to "Department".

For more information about PSIfusion Document Types please refer to the Document Types article.

Document Type Permissions Policy

PSIfusion supports a robust permissions system that enables an administrator to limit which document types each UserUser Group or Team may access.  This feature can be used both for security, by limiting access to sensitive document types that a particular user should not be processing; and for an improved user experience, by filtering the list of document types a user can see to the smallest subset that applies to their role within the organization.

OptionDescription
NoneNo document type permissions are enforced, all users will have access to all document types.
SimpleDocument type permissions will be defined using a grant action. Users will have not have access to any document types except those to which they are explicitly granted access.
AdvancedDocument type permissions will be defined using both grant and deny actions. Users will not have access to any document types except those to which they are explicitly granted access and where access has not been explicitly denied.


By default, PSIfusion includes a link at the bottom of the client side application window that allows users to contact our Support Team directly.  In environments where users should be contacting an internal IT department or administrator, this option allows the administrator to either disable the link completely, or customize the link destination. The link text specified here is a standard URL, so all of the following Uniform Resource Locator (URL) types are supported:

TypeExampleDescription
HTTPhttp://support.mycompany.comA standard Hyper Text Transfer Protocol (HTTP) URL to your companies internal support portal.
HTTPShttps://support.mycompany.comA link to your company support portal, using a Secure Sockets Layer (SSL) encrypted HTTP connection.
MAILTOmailto:support@mycompany.comA mail URL that will launch the user's default mail client and initiate an email to your support mail address.

These URL's are just illustrating how you may choose to use this feature.  Any other standard URL types that are supported by the client's browser are also supported for the support link.

Enable Teams

Teams within PSIfusion represent a set of users, a supervisor, and optionally a document type permissions set.  For a comprehensive overview of teams, as well as how they should be configured and utilized within an organization, please refer to the Teams article.

Using this option administrators can enable and configure, or disable support for teams within PSIfusion.  

OptionDescription
Deny login for users without a team assignmentIf enabled, users cannot log into PSIfusion if they have not been assigned to a team.
Enable Document Type PermissionsIf enabled, document type permissions will be configurable at the team level, in addition to the User and User Group levels.
Restrict Queue Editing to SupervisorsIf enabled, only supervisors may edit document queues. Queue editing enables a user to route documents to other users or delete documents from the queue entirely.

Display file name in Document Queue list

Available in version 2.0.0.21 and higher

When this setting is enabled, a new line is displayed for each Document in the Document queue list showing the file name of the first page of that Document (as shown on the right). NOTE: Fusion stores each page of a Document as a single page tiff, so multi-page Documents will have multiple files, we only display the name of the first page.

Document Queue Sorting

This option allows you to sort by:

  • Timestamp (current behavior)
  • File name of the document

NOTE: File name sorting is still available whether the file name showing or not.

v. 2.0.0.23 and higher

Enable QA Commands

By default this option should be enabled for new and existing installs. If the user disables QA commands, the following commands should not be available to run:

  • Save Rotation (still allow Rotate Left and Right, just don't allow saving)
  • Delete Page
  • Delete Document
  • Split Document at Page
  • Insert After Page
  • Insert Before Page
  • Replace Page


Mail Settings

PSIfusion supports an alert system for various system conditions, such as document aging.  When an alert is generated the alert is sent to the appropriate user, typically either a supervisor or an administrator.  Adding mail settings configuration to a PSIfusion system and enabling notifications extends the alert system by automatically generating emails for each alert that is logged.  

Server

Enter the SMTP mail server address to be used by the PSIfusion mail service. 

Port

Enter the port required by the mail server. Common server ports are:

  • SMTP – port 25 or 2525 or 587
  • Secure SMTP (SSL / TLS) – port 465 or 25 or 587, 2526 

Authentication

If server authentication is required, enter the Username and Password to be used by the PSIfusion service for sending mail.

Encrypted Connection Type

Allows you to specify the encryption type used by the Mail Server (i.e. TLS, SSL).

Notifications

Enables the generation of email notifications when new alerts are created.  You must provide a valid email address from which the notification emails should be sent.

When Notify users when new documents are posted in their queue is enabled the user will only be sent a single email from the time they log off until they log back into PSIfusion regardless of how many new documents are added to their queue. A single email is sent in order to avoid a user getting spammed with too many notification emails.

Mail Spool

When PSIfusion email features are enabled, generated emails are placed into a mail spool on the server.  Messages are then sent to the mail server on a fixed interval.  In the event that the mail server is unreachable or delivery of a message fails for another reason, the mail spool will report the message status, as well as allow an administrator to immediately retry or delete all messages in the spool. 

Logs

PSIfusion uses a multiple layered approach to logging.  Log files for deployment related issues, and issues where the PSIfusion application is not accessible are logged to a text file within the deployment storage folder.  All other log entries are stored in the deployment database.

The logs tool in the administration module allows an administrator to query log entries and export them to a text file.

For assistance locating the deployment manager log files, please see PSIfusion Log Files.

API Keys

PSIfusion API is designed for managing administrative tasks such as user and queue monitoring. You can connect and develop using any preferred programming language. The default response is JSON but the server will also return XML if requested.

You can find the API Key tool in the bottom row of buttons under the Organization tab.

To create an API Key for a user click on the API Keys button as shown above. A pop up screen will appear.

Click on the Create button located on the right of the window as shown above. A pop up screen will appear.

Enter the username the API Key will be assigned to and click OK. Use this API Key for calling out actions. For more information on API Calls available in PSIfusion please see our API Calls article.

On this page:


Related Items: