Adding an Application

The following topics are covered in this section:

Adding an Application to Your Organization’s List of Managed SaaS Applications
Initial Ingestion of SaaS Activity Data
Adding New Applications to Technopedia

For details regarding the Managed SaaS Applications user interface, see Managed SaaS Applications.

Best Practice:It is recommended to first integrate your Human Resources (HR) provider. To see which applications have integrations, see the list of SaaS Management’s prebuilt integrations in Application Task Tracking. If you want to request an integration, contact your Flexera account manager.

Important:The Administer SaaS role or the Manage SaaS applications & users role is required to add an application. For details, see Flexera One Roles.

Adding an Application to Your Organization’s List of Managed SaaS Applications

The applications available to be added to your Managed SaaS Applications are sourced from Technopedia.

To add a managed SaaS application in SaaS Management, perform the following steps.

To add an application to your organization’s list of Managed SaaS Applications:

1. From the SaaS menu, click Managed SaaS Applications. The Managed SaaS Applications screen appears.
2. Click Add Application. The Add Application screen appears.
3. Click the card of the application you wish to add. The application’s slideout displays. The contents of the slideout will vary depending on whether an application is integrated.
4. Enter any Tags for the application. This field is optional.

Note:For Salesforce, instance and user type information can be entered after clicking Authenticate Integration.

5. You can either:
a. Complete the integration of this application at a later date by clicking Save. For details, see the topic “Authorizing an Integration at a Later Date” in Authorizing a SaaS Integration. Once your application is saved, the application’s Overview tab opens.
b. Click Authenticate Integration to integrate this application now and follow the steps below.
6. Select the number of days for the Activity Threshold, which defines the number of days of inactivity before an application’s user is labeled inactive. Activity Threshold is not available for all applications.

The default activity threshold is 60 days. After selecting your activity threshold, this value will appear in the application’s Overview tab and adjust your usage data for all application activity throughout the SaaS Management interface.

For applications with an integration, you can customize the activity threshold at a later date to 15, 30, 60, 90, or 120 days. For details, see Setting Activity Thresholds.

7. Select the appropriate Integration Tasks.
8. Click Authorize to complete the process for Authorizing a SaaS Integration. Once your application is integrated, the application’s Integrations tab opens. It will take a few minutes to populate all the tabs within the SaaS Application Details. Initially, 30 days’ worth of historical SaaS activity data is retrieved. For details, see Initial Ingestion of SaaS Activity Data.

Initial Ingestion of SaaS Activity Data

When a new integration is created within SaaS Management, typically 30 days’ worth of historical SaaS activity data is retrieved from the application. Exceptions to the initial 30-day period are noted within the individual integration instructions. Activity data is tracked for active, inactive, and never active users. For a description of these terms, see Common User Activity Terms Found in SaaS Management Help.

The following scenarios describe the SaaS activity data that is available for each time period:

SaaS Activity Data Immediately Available after Initial Integration
SaaS Activity Data after 30 Days
SaaS Activity Data Beyond the Activity Threshold

SaaS Activity Data Immediately Available after Initial Integration

You will immediately see the following SaaS activity data in the SaaS Management UI:

Users that have logged in within the last 30 days appear as Active.
Users that have not logged in within the last 30 days appear as Never Active.
Inactive users appear as 0.

SaaS Activity Data after 30 Days

After 30 days, 60 days of SaaS activity data appears in the SaaS Management UI, as explained in the formula below.

first 30 days + 30 elapsed days = 60 days of data

After 30 days, you will see the following SaaS activity data in the SaaS Management UI with 60 days as the selected activity threshold:

Users that have logged in within the last 60 days appear as Active.
Users that have not logged in within the last 60 days appear as Never Active.
Inactive users appear as 0.

SaaS Activity Data Beyond the Activity Threshold

Users that have not logged in since the selected activity threshold appear as Inactive in the SaaS Management UI.

Example: 60 days is the selected activity threshold

Users that have logged in 61 days ago but not since, appear as Inactive in the SaaS Management UI.

Adding New Applications to Technopedia

If you would like a new SaaS application added to our Technopedia catalog, you need to complete a Technopedia support ticket with the following information.

1. For a list of phone numbers to contact Flexera Support as well as instructions for submitting a support case, see the Contact Flexera Support page in the Flexera Community.
2. Click Open New Case.
3. On the Open new case screen, complete the following fields.
a. The Product field should be set to Data Platform Technopedia.
b. The Version field should be set to Technopedia (installer) 5.5.0.
c. In the Case summary field, enter the application name and version (if applicable) to be added.

Example: Please add Microsoft Office 365 version n.n

d. In the Description field, enter the product information and include a reference of where to find information pertaining to the product being requested. See the example below.
Manufacturer—Microsoft
Product name—Office 365
Version—n.n
Reference—www.<insertwebaddresshere>.com
4. Upload any needed documents for your case before saving it. You will receive an email with the case number.
5. Flexera Support support will follow up on your case and take the appropriate action.