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.

The topics in the following steps will help you get started using Gimmal Records Management.  There are detailed guides throughout the rest of the guides, however we recommend you starting with these steps the first time you use the software.

1. Deployment

Gimmal Records Management is a part of the Gimmal Cloud, however it can also be deployed on-premise.  However, even if you use the Gimmal Cloud, you may still need or want to deploy the connectors on-premise.  See the planning topic for more information.

Plan Your Deployment

If you are Deploying the core software on-premise, start with the following topic:

Deploying On-Premise

2. First time setup

If this is the first time you are personally using Gimmal Records Management, you should start here.  Even if you are the first person in your organization to use the software, start here for setting it up the first time.

First time setup

If you are a user, and not configuring the File Plan, skip down to step 6, using the Inbox.

3. Creating the File Plan

The first step for almost any records management implementation is to build your file plan, which contains the retention schedule and lifecycles for you content.  Build each of the following components in order to fully prepare your File Plan

Triggers

Retentions

Lifecycles

Record Classes

4. Add classification rules

Once the File Plan is complete you will need to build classification rules in order to classify content in your sources to the Record Classes in the File Plan.

Classification

5. Adding policies to Record Classes

Once you have information classifying correctly, it's time to assign the lifecycles (policies) to each Record Class.

Lifecycles and Record Classes

6. Using the inbox

Now that content is being classified to your File Plan and adhering to policies, records ready for disposition will start showing up in your Inbox.

Inbox

JavaScript errors detected

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

If this problem persists, please contact our support.