Skip to main content
Skip table of contents

Getting Started

First of all, thank you for being a client. We appreciate that you trusted Gimmal for your purchase.

Gimmal Records by Role

The documentation for Gimmal Records is separated into guides for each role

  • Administrator Guide - Topics that are only available to administrators, such as deployment, global configurations, and security

  • Record Manager Guide- Day to day functions related to managing records and file plan

  • User Guide - For users who primarily access Gimmal Records Management to approve items for disposition

  • Developer Guide - PowerShell options and report designers for a more technical audience

Gimmal Records Step by Step

1. Deployment

Deploying Gimmal On-Premises requires installing and configuring the Core application (including the Manager Web and Lifecycle Service), setup security, and then install connectors to manage specified data sources. The following planning topics will help you understand your options:

Physical Records Management Deployment

The integrated Physical Records Management for Gimmal Records should not be confused with Gimmal Physical, which is a separate application.

If you have licensed Physical Records Management for Gimmal Records, you will need to ensure it is correctly deployed. If you are deploying the physical records management software on your servers, start with the Physical Records Management Server Deployment topic.

2. First-Time Setup

For a new, greenfield set-up, as an administrator, please view this article:

As an end user accessing the application for the first time:

3. Creating the File Plan

The next step after installation is to build your file plan, which contains the retention schedule and lifecycles for your content. Start with:

4. Using the Inbox

Now that records are being classified to your File Plan, records ready for disposition will start showing up in the Inbox.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.