This article explains SSProtect Licensing.
SSProtect product Licensing works the same for both Organization Accounts and Individual Accounts. This article describes the way in which Licensing provides authorization and access to various components, services, features, requests, and resources.
But first, some semi-legal clarification (next two sections).
Some, but not all, expectations, boundaries, prerequisites, and terms to which a user must agree before making use of Licensed entities can be found in the License Agreement presented during software installation.
Note that License Agreements may be, but do not have to be, different for each Organization Account and Individual Account. Additional details are beyond the scope of this article.
Licenses cannot be transferred to other Organizations, though can be re-used within the context of an Organization (see below). These rules are enforced by KODiAC Cloud Services: Your host computer does not contain any License resources that affect authorization to individual entities, though the software provides insight into Licensed State.
SSProtect supports different License Types for accounting, pricing, and general capabilities. These include Employee, Trial, Researcher, Journalist, Partner, Promotional, and Customer Licenses. When downloading software for Trial use, Accounts are initially assigned Trial Licenses. The License Type can be changed at anytime since your KODiAC Cloud Services operator (ISP) manages the License Type and Period (below).
License State and Period
An Account's License State is always either Active or Expired, and over time transitions through Grace and Gap Periods before reaching the Expired Period. Note the difference between the State and the Period; an Expired License within the Grace Period entertains certain capabilities (see below), as does an Expired License in the Gap Period. After the Gap Period expires, the License transitions to the Expired State, which precludes any use of the software and related services.
Default Licenses and Timeframes
When a new user downloads the software and provisions a new Account, it is by default assigned a Trial License, in the Active State for 14 days by default. The License then transitions to the Grace Period, by default 7 days in duration. The Gap Period follows for another 7 days, by default, at which point the Expired License no longer permits access to system resources.
Note that the Active, Grace, and Gap Periods can all be changed with associated Agreements between the Service Provider (DefiniSec) and an Organization or Individual Account (Users; You).
Permissions during the Grace Period
During the Grace Period, applied to all License Types, by default 7 days in duration, you can access protected content but cannot protect new content. This means In-Place Encryption does not re-encrypt content when it is closed - and in fact Releases Protections, which means the resulting plaintext file is afforded no ongoing protection.
If using :Recover, materials can be Restored during the Grace Period. :Assess reporting and User Management (for Delegates and Administrators) also remain available, though you cannot create new Users during the Grace Period. Advanced component behavior varies based on individual agreements.
The Gap Period
The Gap Period, by default 7 days in duration, follows the Grace Period. This is the duration of time for which content is retained, and during which License Renewal results in seamless continuation using pre-existing configuration details and protected content. All :Assess report data, for previously Licensed transactions, remains available.
After the Gap Period expires, there is no certainty that a License can be renewed for continued service using previous configuration and/ or stored data (as noted above). When this happens, you have to create a new License, which then requires re-creation of all configuration. Prior content - including stored protected data and :Assess report details - may be permanently deleted.
Gap -> Expired Transition
A transition from the Gap Period to the Expired State (and Period) does not automatically result in removal of stored information and configuration data, though it is the earliest point at which this can occur. Be sure to Renew if you wish to retain managed content and configuration. As noted, the default Gap Period is 7 days, and agreements can be modified to adjust this timeframe at any time.
License expiration is not currently managed with Administrative Notification, though at Login, you will be presented with the License dialog if operating in the Grace or Gap Periods. This reality is depicted in major UI component Captions.
As noted in the Gap Period section, Licenses can be renewed at any time before the Gap Period expires. After that time, Licenses and associated Accounts/ configuration will likely need to be re-created, and stored data will likely be lost. Coordinate requests directly with Support.
License Seat Associations
Organizations are formed with a pre-configured number of Licenses. If you Sign-Up with a new Organization, as described in the article, Creating an Account, you will by default start with 5 (Trial) License Seats that operate as noted in the previous paragraphs - however only after assigned to an Account.
If you have an Organization provisioned for you, and you receive a Registration Email to operate as noted in the article, Using the Registration Email, you may have more than 5 Licenses available for assignment to new Accounts. This depends on terms specific to your use, and it's likely these are not Trial Licenses, and as a result the timeframes that govern progression through the License States noted in this article will vary.
Licenses are as noted dynamically attached to Accounts, usually when they are Provisioned. As a Privileged User, when you Provision a new Account, a Seat License is pre-reserved and associated with the Account you have created. This License can be dynamically re-used with another Account in two cases - 1) after you Disable an Account, or 2) after you Delete the Account and execute a Recover Seat operation.
Sign-Ups to existing Organizations do not however pre-reserve a License, and as such an Organization does not need to have a License available when an end-user submits the request. You will, however, need an available License to Validate the Account, activating it for use within your Organization.
Refer to the article, Seats, Deleting, and Purging for more information.
You can search this site for more information on various topics, or use this link to submit a specific request. You can also send email directly to firstname.lastname@example.org, and our staff will respond to your needs as soon as possible.
In the meantime, don't forget to check out our primary website and Insights columns for information on current trends, security topics, and how our technologies relate.
This article was updated w/ v9.1.0 of the :Foundation Client