Box, a content management platform for companies of all sizes and industries, is Flexera SaaS Management’s latest SaaS integration to help optimize license spend and license usage. To achieve this goal, you need to create SaaS Management’s new Box Client Credentials  integration.   Best Practice • Flexera recommends creating the Box Client Credentials  integration to view your organization’s Box license usage data. Any existing Box integrations in SaaS Management will be superseded by this new Box Client Credentials integration.   Tip • The Box Client Credentials   integration uses the more secure OAuth 2.0 with Client Credentials Grant Authentication Method . Box Client Credentials Integration Features    The following Box Client Credentials integration features help you further manage your organization’s Box subscription.   OAuth 2.0 with Client Credentials Grant Authentication Method   License Differentiation and License Types   Auto-Populated Box Client Credentials License Information   Managing Available Box Client Credentials Licenses   Reclaiming Box Client Credentials Licenses   License Information and Reclamation API Endpoints   Application Task Tracking Chart   OAuth 2.0 with Client Credentials Grant Authentication Method  The OAuth 2.0 with Client Credentials Grant authentication method is required to authorize this Box Client Credentials integration with SaaS Management. For details, refer to the Box Developer documentation section Client Credentials   Grant .     License Differentiation and License Types This feature allows Software Asset Managers (SAMs) to differentiate between the multiple Box subscription plans (see the table below) that are available and being used by their organization’s users. To learn more about license differentiation, refer to Tracking Application Activity by License Type for License Differentiation. Table -1 • Box License Type Descriptions License Type Description Business Starter Recommended for users at small business, especially those in the initial stages of operations Includes limited storage Can only collaborate with other paying users Business Recommended for users at small to medium-sized organizations that collaborate mostly with other internal users Includes all Starter plan features plus unlimited storage, custom branding, and administrative controls over your Box account Business Plus Recommended for users at businesses in creative industries that collaborate and share often with external users Includes all the Business plan features plus metadata capabilities Can add as many users outside of your business as needed Enterprise Recommended for corporate businesses that need top-notch security and compliance features Includes all Business Plus plan features plus use Box seamlessly with all cloud tools while meeting security and compliance needs across all devices Enterprise Plus Recommended for corporate businesses that need top-notch security and compliance features Includes all Enterprise plan features plus Box Shield, Box Governance, Box Shuttle, Box Platform, enhanced services, and more. Auto-Populated Box Client Credentials License Information  The SaaS Management integration with Box Client Credentials offers a License Information integration task that automatically retrieves every 24 hours the name of the Box subscription and license type. This auto-populated Box Client Credentials license information provides a more complete view of your Box SaaS entitlements and component usage by displaying assigned entitlements and user’s license activity (based on the user’s last login). For more details, refer to the  Box Client Credentials  integration instructions. Managing Available Box Client Credentials Licenses  Once the License Information integration task for  Auto-Populated Box Client Credentials License Information is enabled, you can add or remove the Box Client Credentials product licenses you wish to manage within SaaS Management. For more details, refer to the  Box Client Credentials  integration instructions. Reclaiming Box Client Credentials Licenses  SaaS Management’s SaaS license reclamation workflow offers SAMs the ability to optimize their organization’s Box licenses. To reclaim a Box user’s license, refer to Reclaiming SaaS Licenses.  License Information and Reclamation API Endpoints License Information https://api.box.com/2.0/users  Reclamation https://api.box.com/2.0/users/ <<UserID>> For further API information, refer to the  Box Client Credentials  integration instructions. Application Task Tracking Chart The Application Task Tracking chart includes the following integration features for Box Client Credentials:   Application Access  Application Roster License Differentiation License Information Reclamation  Additional Resources: More information on new features and enhancements can be found in What's New in Flexera One.   ... View more

Flexera's SaaS Management has expanded its integration with Salesforce by providing additional fields to help Software Asset Managers fully see and manage cost driver data in their Salesforce environments. For this release, the additional cost driver fields are only available within the SaaS Management database. In a future release, the new attributes will be made available within the SaaS Management UI. The cost driver data will be presented via a series of Power BI dashboards that are currently being developed. Salesforce Integration Requirements The Salesforce System Administrator profile is required to enable the SaaS Management Setup integration task, which populates the cost driver data within the SaaS Management database. For further details, refer to the Salesforce integration instructions. Important • For existing Salesforce integrations, you must update the permissions of the user credentials for the System Administrator profile, if not already granted, to fetch the new Salesforce cost driver fields.  Additional Salesforce Cost Driver Fields The following Salesforce cost driver fields are only available within the SaaS Management database. For further details, refer to the Salesforce integration instructions. Organization Type Login History Sandboxes Instance Name Primary Org Contact Data Storage Total Data Storage Used File Storage Total File Storage Used ... View more

Flexera’s SaaS Management team received customer feedback to provide more meaningful and accurate SaaS data and metrics for SaaS applications that cannot provide usage data. In response, the SaaS Management user interface now offers an Overview tab design for when the SaaS Management Application Access integration task cannot be enabled for a SaaS application. For a current list of SaaS applications that do not support the Application Access integration task, refer to the empty App Access column in the Application Task Tracking chart. Overview Tab Features for SaaS Applications Without Usage Data From the SaaS menu, click Managed SaaS Applications, which opens the Managed SaaS Applications screen. After clicking a SaaS application name or instance link in the Managed SaaS Applications screen, the Overview tab opens by default. The table below describes the Overview tab features for when usage data is not available for a SaaS application. Table -1 • Overview Tab Features for SaaS Applications Without Usage Data  Feature Description Total Users Depending on the SaaS application, the source for the total number of users comes from the: Application Roster SSO Application Roster Note: SaaS applications that only have an HR Roster task enabled (Example: Human Capital Management (Workday)) will not have a total users count. Managed Licenses The number in the Managed Licenses tile equals the total number of licenses created in the SaaS application’s Licenses tab. Estimated (Est.) Annual Spend This is the total annual cost for all the Managed Licenses. Total Users Over Time This line chart shows the total users over a 30-day, 1-year, or 2-year period. Additional Resources: Flexera One Help: Overview Tab Features for SaaS Applications Without Usage Data More information on new features and enhancements can be found in What's New in Flexera One . ... View more

It is common for customers to have ~500k user accounts in Azure, which was resulting in ~500k API calls when retrieving the Single Sign-On (SSO) applications that are assigned to those users. This volume of API calls - in almost all instances - resulted in the SaaS Management task failing due to a hard 8-hour stop. This issue has been addressed by using the Microsoft AppRoleAssignments API. This API endpoint allows Flexera to approach the challenge in a different way by passing the application ID (rather than the user ID previously) and retrieving the list of assigned users. By reducing the number of API calls, the managed application is hugely more efficient. For further details, refer to the Flexera One Help: Azure  Azure Client Credentials   More information on new features and enhancements can be found in  What's New in Flexera One . ... View more

Flexera’s SaaS Management has enhanced its Tableau Online integration to optimize license spend and license usage. You can now view the total number of allowed Tableau licenses by license type and identify which Tableau licenses have been assigned to your organization’s users. You can also now reclaim underutilized Tableau licenses to optimize license usage. Tableau Online License Types and License Differentiation SaaS Management’s new Application Roster and Application Access API endpoint identifies each Tableau user’s assigned licenses. The new License Information API endpoint can identify the following Tableau Online license types described in the table below. Table -1 • Tableau Online License Type Descriptions License Type Description Creator This license type’s user permissions include: Server administration Advanced server deployment monitoring Programmatic content migration Adding data sources to create new dashboards and visualizations. Explorer This license type’s user permissions include: Site role management, content ownership, settings, and permission settings Visualizing existing data and exploring existing data sources, but not allowing the ability to add any new data or data sources Creating alerts and sending emails when the stated conditions are met Scheduling data flow Creating and sharing custom views. Viewer This license type’s user permissions include: Viewing and interacting with the published dashboards Receiving data-driven alerts and creating personal alerts.   Auto-Populated Tableau License Information The SaaS Management integration with Tableau offers a License Information integration task that automatically retrieves every 24 hours the name of the Tableau subscription, license type, and total allowed number of licenses. This auto- populated Tableau license information provides a more complete view of your Tableau SaaS entitlements and component usage by displaying: Assigned entitlements User’s license activity (based on the user’s last login). Important • If you enable the License Information integration task, note the following: If you have manually managed Tableau application licenses data in SaaS Management prior to enabling the License Information Integration task, then t he managed application's license information you previously entered in the Licenses Tab will be overwritten with the data ingested from Tableau. You need to enter and keep up to date the following Licenses Tab information. The License Information integration task does not pull in this information. The SaaS application’s annual spend calculation relies on entered and accurate license effective and ending dates. Amount Currency Payment Frequency Effective Date Ending Date When the License Information integration task first discovers an active subscription, it defaults the effective date to its discovery date and displays an empty end date. As a result, the license term is effective and will not expire. When the License Information integration task is disabled, the managed application's license information reverts to what it was prior to the License Information integration task being enabled. As a result, your previously manually entered license information appears in the Licenses Tab. When the License Information integration task is re-enabled, the last automatic-captured license data that was available before disabling the License Information integration task appears in the Licenses Tab. To auto-populate Tableau license information using the SaaS Management user interface, refer to the Tableau Online integration instructions. Managing Available Tableau Online Licenses Once the License Information integration task for Auto-Populated Tableau License Information is enabled, you can add or remove the Tableau product licenses you wish to manage within SaaS Management. For details, refer to the Tableau Online integration instructions. What happens when a Tableau license is filtered out? No license entry appears on the Tableau Licenses tab, even when the Show Inactive switch is disabled. Filtered out licenses are not included in annual spend calculations. Filtered out licenses do not appear on the All SaaS Licenses page. Filtered out licenses do not appear on the SaaS License Usage page when the Show License Details switch is enabled. Users who are only entitled to licenses that have been filtered out do not appear in the Tableau Users tab. Activity from users who are only entitled to licenses that have been filtered out does not appear in the Tableau Activity tab. Since users in this filtered state are not listed in the Tableau Users tab, they also would not be flagged as reclamation opportunities. Users in the filtered state would not count toward active/inactive/never/total usage counts from SaaS metrics. The HR roster user entry would not show the user listed in the applications list if they have been filtered out. A user in the filtered state would not be marked as suspicious, even if their HR roster entry were deactivated and they were still generating Tableau usage. The user in the filtered state has been effectively removed from the Application Roster and the Tableau Activity tab. Therefore, the user does not appear on the Suspicious SaaS Activities page. If a user is not assigned any licenses, the user is filtered out of the Tableau Users tab. Reclaiming Tableau Online Licenses The new Reclamation API endpoint allows Software Asset Managers to reclaim underutilized Tableau licenses to optimize license usage. To reclaim Tableau licenses using the SaaS Management user interface, refer to the Tableau Online integration instructions. SaaS Management’s new Application Roster and Application Access API endpoint identifies each Tableau user’s assigned licenses. The new Reclamation API endpoint allows Software Asset Managers to reclaim underutilized Tableau licenses to optimize license usage. For further details, refer to the following API Endpoints and the Tableau Online integration instructions. API Endpoints Application Roster and Application Access https://<base_url>/api/3.14/sites/<siteId>/users License Information https://<base_url>/api/3.14/sites/<siteId> Reclamation https://<base_url>/api/3.14/sites/<siteId>/users/userId Application Task Tracking The following columns in the Application Task Tracking chart were updated to include Tableau: License Differentiation License Information Reclamation Additional Resources More information on new features and enhancements can be found in  What's New in Flexera One . ... View more

Your organization’s DocuSign plan can have multiple users in a single account based on the subscribed plan and pricing. Integrating Flexera’s SaaS Management with your organization’s DocuSign instance allows you to store your DocuSign plan name and selected licenses, so you can understand your DocuSign license spend more accurately. You can also now reclaim underutilized DocuSign licenses to optimize license usage. DocuSign License Types SaaS Management integrates with the following DocuSign plans: eSignature Plans and Pricing Personal Standard Business Pro Developer Plans and Pricing Real Estate Plans and Pricing Auto-Populated DocuSign License Information The SaaS Management integration with DocuSign offers a License Information integration task that automatically retrieves every 24 hours the name of the DocuSign plan, license type, and total allowed number of licenses. This auto- populated DocuSign license information provides a more complete view of your DocuSign SaaS entitlements and component usage by displaying: Assigned entitlements User’s license activity (based on the user’s last login). Important • If you enable the License Information integration task, note the following: If you have manually managed DocuSign application licenses data in SaaS Management prior to enabling the License Information Integration task, then t he managed application's license information you previously entered in the License Tab. will be overwritten with the data ingested from DocuSign. You need to enter and keep up to date the following License Tab information. The License Information integration task does not pull in this information. The SaaS application’s annual spend calculation relies on entered and accurate license effective and ending dates. Amount Currency Payment Frequency Effective Date Ending Date When the License Information integration task first discovers an active subscription, it defaults the effective date to its discovery date and displays an empty end date. As a result, the license term is effective and will not expire. When the License Information integration task is disabled, the managed application's license information reverts to what it was prior to the License Information integration task being enabled. As a result, your previously manually entered license information appears in the Licenses Tab. When the License Information integration task is re-enabled, the last automatic-captured license data that was available before disabling the License Information integration task appears in the Licenses Tab. To auto-populate DocuSign license information using the SaaS Management user interface, refer to the DocuSign integration instructions. Managing Available DocuSign Licenses Once the License Information integration task for Auto-Populated DocuSign License Information is enabled, you can add or remove the DocuSign product licenses you wish to manage within SaaS Management. For details, refer to the DocuSign integration instructions. What happens when a DocuSign license is filtered out? No license entry appears on the DocuSign Licenses tab, even when the Show Inactive switch is disabled. Filtered out licenses are not included in annual spend calculations. Filtered out licenses do not appear on the All SaaS Licenses page. Filtered out licenses do not appear on the SaaS License Usage page when the Show License Details switch is enabled. Users who are only entitled to licenses that have been filtered out do not appear in the DocuSign Users tab. Activity from users who are only entitled to licenses that have been filtered out does not appear in the DocuSign Activity tab. Since users in this filtered state are not listed in the DocuSign Users tab, they also would not be flagged as reclamation opportunities. Users in the filtered state would not count toward active/inactive/never/total usage counts from SaaS metrics. The HR roster user entry would not show the user listed in the applications list if they have been filtered out. A user in the filtered state would not be marked as suspicious, even if their HR roster entry were deactivated and they were still generating DocuSign usage. The user in the filtered state has been effectively removed from the Application Roster and the DocuSign Activity tab. Therefore, the user does not appear on the Suspicious SaaS Activities page. If a user is not assigned any licenses, the user is filtered out of the DocuSign Users tab. Reclaiming DocuSign User Licenses SaaS Management’s new Reclamation API endpoint allows Software Asset Managers to reclaim underutilized DocuSign licenses to optimize license usage. To reclaim DocuSign licenses using the SaaS Management user interface, refer to the DocuSign integration instructions. API Endpoints Application Roster and Application Access https://account.docusign.com/oauth/userinfo (Use this API endpoint to obtain the base URL and account ID, which are used for the below API endpoint) https://<<base_url>>/restapi/v2/accounts/<<account_Id>>/users License Information https://<<base_url>>/restapi/v2/accounts/<<account_Id>>/billing_plan  Reclamation https://<<base_url>>/restapi/v2/accounts/<<account_Id>>/users Application Task Tracking The following columns in the Application Task Tracking chart were updated to include DocuSign: License Differentiation License Information Reclamation Additional Resources More information on new features and enhancements can be found in  What's New in Flexera One . ... View more

Flexera’s SaaS Management integration with Adobe’s Creative Cloud now offers the following features to manage your online and traditional desktop Adobe assigned entitlements. Auto-Populated Creative Cloud License Information Managing Available Creative Cloud Licenses Viewing the Hybrid Adobe Position Avoiding Duplicate Adobe Licenses between SaaS Management and IT Asset Management API Endpoints Auto-Populated Creative Cloud License Information The SaaS Management integration with Creative Cloud offers a License Information integration task that automatically retrieves every 24 hours the name of the Creative Cloud plan and license type. This auto-populated Creative Cloud license information provides a more complete view of your Adobe SaaS entitlements by displaying the assigned entitlements. Important • If you enable the License Information integration task, note the following: If you have manually managed Creative Cloud application licenses data in SaaS Management prior to enabling the License Information Integration task, then the managed application's license information you previously entered in the Licenses Tab will be overwritten with the data ingested from Adobe. You need to enter and keep up to date the following  Licenses Tab information. The License Information integration task does not pull in this information. The SaaS application’s annual spend calculation relies on entered and accurate license effective and ending dates. # of Items Allowed Amount Currency Payment Frequency Effective Date Ending Date When the License Information integration task first discovers an active subscription, it will default the effective date to its discovery date, and it will have an empty end date. As a result, the license term is effective and will not expire. When the License Information integration task is disabled, the managed application's license information will revert to what it was prior to the License Information integration task being enabled. As a result, your previously manually entered license information will appear in the Licenses Tab. When the License Information integration task is re-enabled, the last automatic-captured license data that was available before disabling the License Information integration task will appear in the Licenses Tab. To auto-populate Creative Cloud license information using the SaaS Management user interface, refer to the  Creative Cloud  integration instructions. Managing Available Creative Cloud Licenses Once the License Information integration task for Auto-Populated Creative Cloud License Information is enabled, you can add or remove the Creative Cloud product licenses you wish to manage within SaaS Management.  For details, refer to the  Creative Cloud integration instructions. What happens when a Creative Cloud license is filtered out? No license entry appears on the Creative Cloud Licenses tab, even when the Show Inactive switch is enabled. Filtered out licenses are not included in annual spend calculations. Filtered out licenses do not appear on the All SaaS Licenses page. Filtered out licenses do not appear on the SaaS License Usage page when the Show License Details switch is enabled. Users who are only entitled to licenses that have been filtered out do not appear in the Creative Cloud Users and Activity tab. Users in the filtered state would not count toward active/inactive/never/total usage counts from SaaS metrics. The HR roster user entry would not show the user listed in the applications list if they have been filtered out. If a user is not assigned any licenses, the user is filtered out of the Creative Cloud Users tab. When a Creative Cloud license is not selected to be managed in SaaS Management, the license will also not appear in IT Asset Management when Viewing the Hybrid Adobe Position. Viewing the Hybrid Adobe Position While Adobe Creative Cloud licenses are assigned and managed in the Cloud, many of the applications and functionality in the Adobe licensing portal are locally installed on users’ devices. Due to the hybrid nature of Adobe Creative Cloud licenses, it is beneficial to integrate Flexera’s SaaS Management with IT Asset Management in order to manage the Cloud licenses and local installations. In SaaS Management, at the top of the Creative Cloud Overview tab, click the View the hybrid Adobe position link to open Flexera’s IT Asset Management License Summary page. This page is automatically filtered to Publisher name starts with Adobe. Together, Flexera’s SaaS Management and IT Asset Management applications provide a complete view of your organization’s Adobe online and traditional desktop usage. The Creative Cloud for enterprise Single App (Single App) plan allows you to choose any one of the available apps per Single App license and assign them to your end users. For details, refer to the Adobe documentation section   Single App | Creative Cloud for enterprise. When SaaS purchase order data is synchronized with Flexera’s IT Asset Management to display the hybrid Adobe position, you only need to manage your Adobe purchases in Flexera’s SaaS Management. You may wish to include the additional SaaS purchase order details in IT Asset Management. However, these IT Asset Management purchases for Adobe will not impact a SaaS Management-created Adobe Named User license in Flexera’s IT Asset Management. BEST PRACTICE: To avoid confusion and potential license duplication, Flexera recommends that any existing Adobe licenses created in IT Asset Management be deleted as the SaaS Management Creative Cloud integration also creates these licenses with imported entitlement and consumption. If SaaS Management is integrated with IT Asset Management, then all Adobe Creative Cloud licenses are deleted from IT Asset Management prior to integrating SaaS Management with Adobe and creating/managing the Adobe licenses in SaaS Management. For details, refer to  Avoiding Duplicate Adobe Licenses between SaaS Management and IT Asset Management. Avoiding Duplicate Adobe Licenses between SaaS Management and IT Asset Management To synchronize existing Creative Cloud licenses between Flexera’s SaaS Management and IT Asset Management All Licenses page, which feeds to the License Summary page, ensure the Flexera SaaS Manager integration is enabled in the IT Asset Management Integrations tab. For details, refer to the IT Asset Management Settings: Integrations Tab section of the IT Asset Management documentation. To avoid duplicating Creative Cloud licenses between SaaS Management and IT Asset Management, refer to the  Creative Cloud  integration instructions. API Endpoints Application Roster List Users https://usermanagement.adobe.io/v2/usermanagement/users/<<OrganizationID>>/  Application Roster List Groups and Product Profile https://usermanagement.adobe.io/v2/usermanagement/groups/<<OrganizationID>>/  License Information https://usermanagement.adobe.io/v2/usermanagement/groups/<<OrganizationID>>/  Application Task Tracking The License Information column in the Application Task Tracking chart was updated to include Creative Cloud.  Additional Resources More information on new features and enhancements can be found in  What's New in Flexera One . ... View more

Flexera’s SaaS Management has added the capability to view more granular user activity and license details from within the user activity slideout. This improved slideout is available within the  Users tab for all  Managed SaaS Applications. Within the  Users tab, click a user’s email link to open the user’s activity slideout. The  view more user details link takes you to the  Administration > SaaS Settings > Organization > All SaaS Users screen and displays the user’s  All SaaS Users Screen Usage Statistics.  Additional Resources Flexera One Help:  Users Slideout More information on new features and enhancements can be found in What's New in Flexera One . ... View more

As part of our vision for Flexera’s SaaS Management to “be the best” we have today expanded our Salesforce user and license activity data capabilities by providing new metrics and using a bespoke UI. You can analyze your Salesforce user activity for all your Salesforce instances (orgs) or drill down to a specific Salesforce org. User activity can also be analyzed per user and per Salesforce license. Salesforce license activity can also be analyzed at the rolled-up view for all Salesforce orgs or drilled down to a specific Salesforce org. Refer to the following sections for further details. Salesforce All Orgs Orgs View Individual Salesforce Org View Salesforce License Drill Through View Salesforce All Orgs View In the Salesforce All Orgs (previously known as the Salesforce Overview) view, you can view entitled, consumed, available, and active/inactive/never active user counts for each aggregated license type for all Salesforce orgs within one location in SaaS Management. You can further analyze all your Salesforce orgs’ user and license activity data in the: Salesforce All Orgs Overview Tab Salesforce All Orgs Orgs Tab Salesforce All Orgs Licenses Tab Salesforce All Orgs Users Tab Salesforce All Orgs Overview Tab Flexera now offers a high-level view of your Salesforce orgs that are integrated with SaaS Management by displaying: Total number of Connected Orgs Successfully Updated Orgs, based on all integration tasks running successfully Total Accounts from all connected Salesforce orgs User activity data has been enhanced in this view by providing: Total percentage of active, inactive, and never active users for all Salesforce orgs in the Activity status graph Data drill throughs to the Salesforce All Orgs Users tab via user activity data links in the Activity status and Days since last activity graphs. Salesforce All Orgs Orgs Tab The Orgs tab provides a high-level overview of your organization’s total Salesforce managed licenses, assigned users and user activity status by org name and org ID. You can drill down to a particular Salesforce org’s Overview tab via the Org Name or the Org ID column links. Salesforce All Orgs Licenses Tab The Licenses tab provides a high-level overview of your organization’s total Salesforce licenses by name, category, number remaining, and number assigned by org name and org ID. You can analyze license activity for a specific Salesforce License Name across Salesforce orgs by checking the Group By License Name box. An aggregated row of the Salesforce license name is displayed, together with aggregated numbers of Remaining and Assigned licenses from multiple Salesforce orgs. License Name Data Drill Through If the Group By License Name box is checked, clicking  the arrow before the aggregated License Name displays a list of License Details pages for each Salesforce org. Clicking the Application link opens the License Details page for the Salesforce org. For details, refer to the Salesforce License Drill Through View. Salesforce All Orgs Users Tab Building on the earlier release of the Salesforce Users Tab, the bespoke UI now offers: A user slideout to manage and optimize licenses at the user level without having to filter or search. Clicking a Username link opens this slideout and displays a user’s assigned licenses, last activity based on the last login date, and activity counts by date range. Filtering user activity by Salesforce Org ID or Org Name. Data drill through to a selected Salesforce org’s Overview tab by clicking the Org ID or the Org Name link. Individual Salesforce Org View From the Salesforce All Orgs view, you can drill down to an Individual Salesforce Org Overview Tab and analyze user and license activity for a specific Salesforce org. You can navigate back to the Salesforce All Orgs view by clicking the View All Salesforce Orgs link at the top. Data drill throughs from the Individual Salesforce Org Overview Tab to a Salesforce org’s Users tab provide opportunities to reclaim underutilized Salesforce licenses by clicking the Reclamation Opportunities tile. For details, refer to Reclaiming SaaS Licenses. Individual Salesforce Org Overview Tab User activity data has been enhanced in this view by providing: Total percentage of active, inactive, and never active users for the selected Salesforce org in the Activity status graph Data drill throughs to a Salesforce org’s Users tab via user activity data links in the Activity status and Days since last activity graphs. License activity at the Salesforce org level now displays in the Licenses table. You can view a Salesforce org’s license position by license name, category, number remaining, and number assigned. Clicking the License Name link opens a License Details page for the selected Salesforce org. For details, refer to the Salesforce License Drill Through View. Salesforce License Drill Through View In this view, user and license activity is focused on the users assigned to a specific Salesforce license either at the All Orgs level or for a selected Salesforce org. You can access this view through the Salesforce All Orgs Licenses Tab or by clicking the Licenses Name in the Licenses table of the selected Salesforce org Overview tab. At the top of the license drill through is the Salesforce license name with the relevant org links underneath. Clicking a Salesforce org link opens the Overview tab for the selected Salesforce org. If several Salesforce org links are listed under the Salesforce license name, the license usage data is rolled up from the users who are included in those orgs. For Salesforce user licenses, the Activity Status and Days Since Last Activity graphs drill down to the Users table at the bottom of the Salesforce license drill through view. IMPORTANT: In the Salesforce license drill through view, the Activity Status, Days Since Last Activity, and Activities Over Time graphs are only available for Salesforce user licenses. Additional Resources Flexera One Help: Analyzing Salesforce User and License Activity Data More information on new features and enhancements can be found in  What's New in Flexera One . ... View more

Flexera’s SaaS Management has enhanced its Smartsheet integration by now offering user event activity tracking and improving the Smartsheet license reclamation workflow. User Event Activity Tracking For organizations with Smartsheet Enterprise plans and the add-on feature Event Reporting, SaaS Management’s integration with Smartsheet can now track user event activity data. The Smartsheet Event Reporting Reference lists all currently supported user event activity. For Smartsheet Pro and Business plans, SaaS Management’s integration with Smartsheet only tracks last login activity. For further details, refer to the API Endpoints below and the Smartsheet integration instruction section Integrating Smartsheet with SaaS Management. Note • The SaaS Management License Information integration task is not yet supported for Smartsheet. Currently, there is no Smartsheet API endpoint that fetches license type information and the total number of available licenses. Reclaiming Smartsheet User Licenses Smartsheet user licenses can now be reclaimed using a similar SaaS Management license reclamation workflow as used for reclaiming Microsoft 365 and Salesforce user licenses. Once Smartsheet user licenses are reclaimed in SaaS Management, the users become Free Collaborators in your organization’s Smartsheet account. Free Collaborators are not tracked in the Smartsheet Activity tab within SaaS Management. For further details, refer to the Smartsheet integration instruction section Reclaiming Smartsheet User Licenses. API Endpoints Application Roster https://api.smartsheet.com/2.0/users  Application Access If Enable Event Activity is set as “Yes”: https://api.smartsheet.com/2.0/events If Enable Event Activity is set as “No” or left blank: https://api.smartsheet.com/2.0/users  Reclamation https://api.smartsheet.com/2.0/users/ <<UserID>> Additional Resources More information on new features and enhancements can be found in  What's New in Flexera One . ... View more

Flexera's SaaS Management integration with Coupa has been enhanced with the more secure authentication method OAuth2 with Client Credentials. Beginning with Release 35 (January 2023), Coupa will no longer support API keys and instead require the use of the more secure authentication method OAuth2 with Client Credentials. The following details will help you prepare for the Expense (Coupa) integration enhancement. Action Required for New SaaS Management Integrations with Expense (Coupa) You must grant permissions using the Coupa Integration Admin role with the generated Client ID and Client Secret values as described in Actions Required for Existing SaaS Management Integrations with Expense (Coupa). Actions Required for Existing SaaS Management Integrations with Expense (Coupa) Due to SaaS Management's migration from the token-based authentication method to OAuth2, existing Expense (Coupa) integrations will fail due to a 401 Unauthorized Error. Once the Expense (Coupa) integration tasks start failing, you must reauthorize the Expense (Coupa) integration using the Coupa Integration Admin role with the generated Client ID and Client Secret values as described below. Minimum Permissions Required Minimum API required permissions are based on the Application Permission and User Role. Application Permission Table -1 • Application Permission Permission Description Integration Task Name core.user.read To read the list of users in your Coupa account Application Roster core.expense.read To read the Expense data in your Coupa account Expense Discovery User Role Table -2 • User Role Role Description Integration Admin To grant the application permissions, the user must have Integration Admin access. For details, refer to Coupa’s documentation section OAuth 2.0 Getting Started with Coupa API. Obtaining Client Credentials Log in to Coupa as an Integration Admin to create an OAuth2/OIDC client with the client credentials grant type. Once configured, the Client ID and Client Secret values are used to gain access to the Coupa API. To set up your Coupa instance with a new connection, go to Setup > Oauth2/OpenID Connect Clients. To navigate quickly to this page, type “oauth” in the Search box. Complete the following on Coupa’s Oauth2/OpenID Connect Clients page: Click Create. For Grant Type, select: Client credentials. Specify a name for the Client, Login, Contact info, and Contact Email fields. Select the Scopes as mentioned in the Application Permission section. Scopes are available for review at https://{your_instance_address}/oauth2/scopes. Click Save. Saving the client gives you values for the Client Identifier and Client Secret, which are needed to gain access to the API Scopes you have defined for it. Copy the Client Identifier, which is the Client ID and click Show/Hide to display and copy the Client Secret. Paste the Coupa Client ID and Client Secret values in SaaS Management as mentioned in the Expense (Coupa) integration instructions section Integrating Coupa with SaaS Management.  Additional Resources More information on new features and enhancements can be found in  What's New in Flexera One . ... View more

On or about Monday June 20, 2022, the SaaS Management integration with Coupa will be enhanced with the more secure authentication method OAuth2 with Client Credentials. Beginning with Release 35 (January 2023), Coupa will no longer support API keys and instead require the use of the more secure authentication method OAuth2 with Client Credentials. The following details will help you prepare for the Expense (Coupa) integration enhancement. Action Required for New SaaS Management Integrations with Expense (Coupa) You must grant permissions using the Coupa Integration Admin role with the generated Client ID and Client Secret values as described in Actions Required for Existing SaaS Management Integrations with Expense (Coupa). Actions Required for Existing SaaS Management Integrations with Expense (Coupa) Due to SaaS Management's migration from the token-based authentication method to OAuth2, existing Expense (Coupa) integrations will fail due to a 401 Unauthorized Error. Once the Expense (Coupa) integration tasks start failing, you must reauthorize the Expense (Coupa) integration using the Coupa Integration Admin role with the generated Client ID and Client Secret values as described below. Minimum Permissions Required Minimum API required permissions are based on the Application Permission and User Role. Application Permission Table -1 • Application Permission Permission Description Integration Task Name core.user.read To read the list of users in your Coupa account Application Roster core.expense.read To read the Expense data in your Coupa account Expense Discovery User Role Table -2 • User Role Role Description Integration Admin To grant the application permissions, the user must have Integration Admin access. For details, refer to Coupa’s documentation section OAuth 2.0 Getting Started with Coupa API. Obtaining Client Credentials Log in to Coupa as an Integration Admin to create an OAuth2/OIDC client with the client credentials grant type. Once configured, the Client ID and Client Secret values are used to gain access to the Coupa API. To set up your Coupa instance with a new connection, go to Setup > Oauth2/OpenID Connect Clients. To navigate quickly to this page, type “oauth” in the Search box. Complete the following on Coupa’s Oauth2/OpenID Connect Clients page: Click Create. For Grant Type, select: Client credentials. Specify a name for the Client, Login, Contact info, and Contact Email fields. Select the Scopes as mentioned in the Application Permission section. Scopes are available for review at https://{your_instance_address}/oauth2/scopes. Click Save. Saving the client gives you values for the Client Identifier and Client Secret, which are needed to gain access to the API Scopes you have defined for it. Copy the Client Identifier, which is the Client ID and click Show/Hide to display and copy the Client Secret. Paste the Coupa Client ID and Client Secret values in SaaS Management as mentioned in the Expense (Coupa) integration instructions section Integrating Coupa with SaaS Management.  Additional Resources More information on new features and enhancements can be found in  What's New in Flexera One . ... View more

In August 2021, Microsoft introduced a new capability   to allow the ability to globally configure how Personal Identifiable Information  (PII)  is shared within Microsoft 365 reports. Enabling Data Anonymization encrypted the unique ID of a user. When Data Anonymization is enabled, Flexera's SaaS Management is unable to match the data retrieved from the Microsoft 365 portal to a user, which results in the users being shown in the SaaS Management Suspicious Activities report. Disabling Data Anonymization presented a challenge for customers as it breached their internal policies. This release means that Flexera no longer requires Data Anonymization to be disabled, opening up the power of our SaaS Management Microsoft 365 and Microsoft 365 Client Credentials integrations to all customers.  More information on new features and enhancements can be found in  What's New in Flexera One . ... View more

On May 3, 2022, the SaaS Management Microsoft   Azure and   Azure Client Credentials integrations migrated from Microsoft Azure AD API to Microsoft Graph API. The Azure AD Graph API is now deprecated. Starting June 30, 2022, support ends for Azure AD Graph. Apps using Azure AD Graph after June 30,   2022   will no longer receive responses from the Azure AD Graph endpoint. The following details will help you prepare for the Microsoft Graph API migration.  Action Required for New SaaS Management Integrations with Azure and Azure Client Credentials  You must grant permissions for Microsoft Graph API instead of Azure AD Graph API. Refer to the future API endpoints below.  Azure and Azure Client Credentials API Endpoints  Below are the future Microsoft Graph API endpoints.  HR Roster  https://graph.microsoft.com/vl.0/users   Application Discovery  https://graph.microsoft.com/vl.0/servicePrincipals   SSO Application Access  https://graph.microsoft.com/vl.0/auditLogs/signIns   SSO Application Roster  https://graph.microsoft.com/vl.0/users/<UseriD>/appRoleAssignments   Actions Required for Existing SaaS Management Integrations with Azure and Azure Client Credentials  Due to SaaS Management's migration from Microsoft Azure AD APIs to Microsoft Graph APIs, existing  Azure and Azure Client Credentials  integrations will fail due to a 401 Unauthorized Error.   Actions for Existing Azure Integrations  Once the Azure integration tasks start failing, you must reauthorize the integration. For the Microsoft Graph APIs, an  Offline_access  permission is also necessary for the refresh token generation.   Complete the following action to prevent this error for Existing Azure Client Credentials Integrations  Update the existing permissions to the required Microsoft Graph API permissions:  Auditlog.Read.All  Directory.Read.All IMPORTANT: The Azure integration with SaaS Management will fail if consent is not given to both the AuditLog.Read.All and the Directory.Read.All permissions. For details, refer to the Microsoft List signIns documentation section. More information on new features and enhancements can be found in   What's New in Flexera One. ... View more

Flexera SaaS Management’s integration with ServiceNow and ServiceNow OAuth2 now tracks all user activity and the time the activity occurred. Software Asset Managers can now identify whether users with ServiceNow Approver and Fulfiller (ITIL) licenses are using the paid aspects of their licenses and are delivering services to requesters or approving requests within the appropriate time period. Some examples of tracked ServiceNow user activity include, but are not limited to, the following: Request Approved Request Updated Request Inserted Incident Updated Incident Inserted Incident Inactive Problem Inserted Actions Required for Existing SaaS Management Integrations with ServiceNow and ServiceNow OAuth2 If you currently have a ServiceNow or a ServiceNow OAuth2 integration with Flexera’s SaaS Management, complete the following tasks to track user events and the time the events occurred. For further details, refer to the ServiceNow or ServiceNow OAuth2 integration instructions. The minimum permissions for ServiceNow and ServiceNow OAuth2 have been updated. For details, refer to the appropriate minimum permissions table: Minimum Permissions Required for ServiceNow or Minimum Permissions Required for ServiceNow OAuth2. Enable the updated ServiceNow or ServiceNow OAuth2 user role permissions based on whether your existing integration supports license differentiation. For details, refer to Enabling ServiceNow and ServiceNow OAuth2 User Role Permissions. If your organization currently implements the optional task of Creating a Custom Role with a Reading Permission Specific to the Tables Used in the Integration API, note that step 6 has been added to these instructions. The ServiceNow and ServiceNow OAuth2 API endpoints have been updated. Refer to the appropriate API endpoints based on whether your existing integration supports license differentiation: API Endpoints with License Differentiation or API Endpoints without License Differentiation. Actions Required for New SaaS Management Integrations with ServiceNow and ServiceNow OAuth2 You need to complete the following tasks to integrate ServiceNow or ServiceNow OAuth2 with SaaS Management. For further details, refer to the ServiceNow or ServiceNow OAuth2 integration instructions. To track user activity and the time the activity occurred, complete the task: Enabling the SaaS Management Application Access Integration Task. Note the appropriate user permissions: Minimum Permissions Required for ServiceNow or Minimum Permissions Required for ServiceNow OAuth2. As an option for your organization, you can enable the task: Creating a Custom Role with a Reading Permission Specific to the Tables Used in the Integration API. Based on your decision whether to support license differentiation for your integration, refer to the appropriate API endpoints: API Endpoints with License Differentiation or API Endpoints without License Differentiation. Enabling the SaaS Management Application Access Integration Task To track ServiceNow and ServiceNow OAuth2 user activity and the time the activity occurred, you need to enable the SaaS Management Application Access integration task per the appropriate instructions: Integrating ServiceNow with SaaS Management Integrating ServiceNow OAuth2 with SaaS Management Note • During the first run of the Application Access task, Flexera pulls data for only the last 6 days. Minimum Permissions Required for ServiceNow Role Description Integration Task Name admin, snc_read_only These roles are required for retrieving the ServiceNow users and their activities. For details, refer to the Base System Roles section of the ServiceNow documentation. Application Roster Application Access admin This role is required to: Retrieve the ServiceNow users and their activities Manage user licenses for the Reclamation task. For details, refer to the Base System Roles section of the ServiceNow product documentation. Application Roster Application Access Reclamation Minimum Permissions Required for ServiceNow OAuth2 Role Description Integration Task Name admin, snc_read_only These roles are required for retrieving the ServiceNow users and their activities. For details, refer to the Base System Roles section of the ServiceNow documentation. Application Roster Application Access admin This role is required to: Retrieve the ServiceNow users and their activities Manage user licenses for the Reclamation task. Register the Client Application Generate the Client ID and Client Secret in ServiceNow. For details, refer to the Base System Roles section of the ServiceNow documentation. Application Roster Application Access Reclamation Enabling ServiceNow and ServiceNow OAuth2 User Role Permissions Follow the steps below to enable the correct ServiceNow and ServiceNow OAuth2 user role permissions for an existing SaaS Management integration with ServiceNow. Task: To enable the correct user role permissions for an existing SaaS Management integration with ServiceNow, determine whether License Differentiation is enabled. When License Differentiation is enabled for an existing SaaS Management integration with ServiceNow added using itil and snc_read_only permissions: If you want to enable only the Application Roster and Application Access tasks, you are required to elevate the user role to admin and snc_read_only. If you want to enable the Application Roster, Application Access, and Reclamation tasks, you are required to elevate the user role only to admin. When License Differentiation is not enabled for an existing SaaS Management integration with ServiceNow: If you want to enable only the Application Roster and Application Access tasks, you are required to have the rest_api_explorer role. If you want to enable the Application Roster, Application Access, and Reclamation tasks, you are required to have the user_admin role. For details, refer to the Base System Roles section of the ServiceNow product documentation. Creating a Custom Role with a Reading Permission Specific to the Tables Used in the Integration API If you wish to have a custom role with a reading permission specific to the tables used in the integration API, then follow the steps below to create a custom role. Important • If you enable the Reclamation task, the user_admin role and the custom role are required. Task: To create a custom role with a reading permission specific to the tables used in the integration API: Log in to your ServiceNow instance as a security_admin or log in as a system administrator. Elevate your role by clicking System Administrator. Navigate to Elevate Roles and enable the security_admin check box, which enables this permission to edit the Access Control List. To create a custom role, navigate to the Roles tab by searching for the “roles” keyword in the All Applications menu on the left side of the screen. Click the New button and enter the desired name for the role. Click Submit to create this new role. In the All Application navigator, search for the “Access Control” keyword. Click Access Control (ACL) to navigate to the Access Control tab. In the Access Control tab, search for the access control keyword “sys_user_has_role”. Click on the record with the read operation type, add the custom role created under the Requires Role section, and click Update. Repeat the same steps for the “sys_user_role” Access Control record, add the custom role created to the Requires Role section, and click Update. In the Access Control tab, search for the access control keyword “sysevent”. There will be two records with read operation. Open the record type that does not contain the default entry of “pa_data_collector“. Add the custom role created under the Requires Role section. Click Update. API Endpoints with License Differentiation Application Roster https://<<instance>>.service-now.com/api/now/stats/sys_user_has_role  https://<<instance>>.service-now.com/api/now/table/sys_user_has_role Application Access https://<<instance>>.service-now.com/api/now/stats/sysevent  https://<<instance>>.service-now.com/api/now/table/sysevent Reclamation https://<<instance>>.service-now.com/api/now/v2/table/sys_user_has_role/{sys_id} API Endpoints without License Differentiation Application Roster and Application Access https://<<instance>>.service-now.com/api/now/stats/sys_user  https://<<instance>>.service-now.com/api/now/table/sys_user Reclamation https://<<instance>>.service-now.com/api/now/v2/table/sys_user/{sys_id}    More information on new features and enhancements can be found in  What's New in Flexera One . ... View more