These are the permissions and a brief description of what they do/why they're risky:

Edit Read-Only Fields: can edit fields which are 'Read Only' as per Field Level Security or on the Page layout. This behavior is seen if the Profile associated with the User has 'Edit Read Only Fields' selected (source: https://help.salesforce.com/s/articleView?id=000335725&type=1)


Manage Login Access Policies: can administer Login Access Policies, which allows them to control whether your users are prompted to grant account access to Salesforce admins, and whether users can grant access to publishers (source: https://help.salesforce.com/s/articleView?id=sf.controlling_login_access.htm&type=5)


Manage Password Policies: can set org wide password policies (source: https://help.salesforce.com/s/articleView?id=sf.admin_password.htm&type=5)


Manage Profiles and Permission Sets: can create, edit, and delete profiles and Permission Sets (source: https://help.salesforce.com/s/articleView?id=000332385&type=1)‍


Manage Sharing: can use the Sharing Settings page to manage your organization-wide sharing defaults, sharing rules, and other sharing settings (source: https://help.salesforce.com/s/articleView?id=sf.security_sharing_settings.htm&type=5)

A limited subset of standard objects that are non-customizable do not appear in Field Utilization results. This is because Salesforce does not provide field information for these objects when they are returned in a metadata extract.

If you'd like to further understand the standard objects that currently do not show field data in the Field Utilization dashboard, we invite you to review the table. Keep in mind that the table may not be exhaustive and some standard objects may only appear when certain features are enabled.

There are multiple reasons why a field may not have data in the Field Utilization dashboard. Let's start by looking at the icon next to the blank field for more information.

🔒 Lock symbol: this indicates that a field is encrypted and therefore Hubbl Diagnostics is not able to access the field with an aggregate query to calculate field utilization.

⚠️ System Timeout: this indicates that Salesforce timed out while attempting the aggregate query to capture field utilization (after multiple retry attempts).

🚫 Circle Backslash symbol: this indicates that Hubbl was not able to calculate field utilization for one of the following reasons:

Unsupported Field Type: The field has a field type that doesn't support being queried in aggregate (e.g., Checkboxes, Long Text, Rich Text, Multi-select Picklists, Custom Metadata, etc.)

Missing Access: The user who authorized the scan does not have access to the field or parent object.

Use these instructions to export recommendations from the Recommendations tab and import them into a Jira project.

Prepping Your Hubbl File
1. Navigate to an advanced scan and click the Export to CSV button
2. Unzip your export and open the issues CSV in your favourite spreadsheet tool (Excel or Google Sheets)
3. Remove the following columns:
id
scanScoreId
itemId
value
recommendationId
isBasic
wellArchitectedTopicId
wellArchitectedTopicLevel4URL
createdAt
updatedAt

You can optionally remove the following columns if you do not want to include the Well Architected topics, metadata categories, or namespace in your Jira stories: wellArchitectedCategoryLevel1
wellArchitectedCategoryLevel2
wellArchitectedCategoryLevel3
wellArchitectedCategoryLevel4
recommendationCategorynamespace

5. Export the updated sheet as a CSV


Creating Jira Stories
1. Log in to Jira as a user with the Jira administrators global permission
2. Navigate to the Gear Icon (top right) > System > Import & export > External System import
3. Select CSV to open the CSV file import page
4. Select your recently created CSV document
5. Leave the Use an existing configuration file checkbox unchecked and select Next
6. Choose the project you would like to import into, and select Next (if you do want to import to multiple then follow the directions here:  https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html)

7. In the Setup field mappings page, map the fields in the CSV file to the issue fields in the selected project. In the Jira field column, select the Jira field that you want to map to the field from the CSV file. We recommend the following but every Jira project is unique:

apiName → DescriptionLabel → Description
recommendationContent → Description
recommendationEffort → Story Points (or related Effort field) (For this field select Map field value)
recommendationPriority → PriorityFor this field select Map field value
recommendationTitle →Description
relatedObject → Description
rule → Summary
8. On the Setup value mappings page, specify the Jira field values for each CSV file field value that has been detected by the CSV file import wizard.

If you do not want to change any values then leave this as is.recommendationEffort1 is high and 3 is low, map to your relevant valuesrecommendation

Priority1 is high and 3 is low, map to your relevant values

Select the Begin Import button when you are ready to begin importing your Hubbl Recommendation data into Jira. You will be able to see your progress and receive a success message once it completes.  


🚀 Hubbl Tip: for additional details on importing Jira issues check out their documentation.

Hubbl Org Intelligence analyzes the custom code, declarative code, and environment settings of your org, along with certain value-add analytics/exports.

Hubbl Process Intelligence is a powerful tool that helps you gain insights into the efficiency and effectiveness of your business processes. It serves as both a discovery and coaching tool.

As a ‘discovery tool’, it provides objective insights into the current state of a process, helping to identify systemic issues.

As a ‘coaching tool’, it allows you to benchmark the performance of individuals, teams, or products against your organization's average or the best-in-class standards.

As a ‘hypothesis testing tool’, it enables you to evaluate the effects of system or process changes by comparing processes before and after, for even minor changes.

Business Process Mining, as defined by analyst firm Gartner, refers to tools designed to discover, monitor, and improve processes by extracting knowledge from events captured in information systems.

These tools provide continuous visibility and insights into your processes. Business Process Mining tools accelerate the application of data science to business processes. They are typically system-agnostic but may require data preparation and data science expertise to operate effectively.

In developing Hubbl Process Intelligence, we aimed to address the challenges associated with traditional process mining, particularly for smaller organizations. The key distinctions are as follows:

Data Preparation: Hubbl Process Analytics focuses on radically reducing the need for extensive data preparation. Traditional process mining often requires significant data preparation efforts, which can be time-consuming and resource-intensive.

Time to Insight: Hubbl Process Analytics is designed to deliver insights quickly. It prioritizes minimizing the time it takes to gain valuable insights from your processes, making it more efficient than traditional process mining.

Cost Efficiency: By streamlining data preparation and accelerating the time to insight, Hubbl Process Analytics helps lower the costs associated with process mining projects.

Hubbl Process Intelligence is tailored to serve as a tool for both end-users of Salesforce applications and Salesforce administration and implementation teams. It is specifically designed to cater to the needs of these groups within your organization.

Process Intelligence and Business Intelligence (BI) serve different but complementary purposes:

Business Intelligence (BI): BI is valuable for identifying metrics and trends. For example, it can tell you that sales last quarter were 20% greater than the same quarter last year, with products A and B as the main contributors. However, BI doesn't provide insights into why product C's deals are taking longer to close this year compared to last year.

Process Intelligence (Process Mining): Process analytics excels at pinpointing specific process-related issues. It reveals exactly where in the process problems are arising. For instance, it can identify that product C's delays are due to a lengthier contracting process. Process analytics complements BI by diving deep into process efficiency and effectiveness, offering insights that traditional BI may miss.

The frequency metric in Hubbl Process Intelligence indicates the number of occurrences of each completed activity. For instance, in an opportunity process visualization, if you see 'Customer Evaluating' with a frequency of 762, it means that 762 sales opportunities have passed through that specific stage.

A variant in Hubbl Process Intelligence represents a unique path through a business process. For example, different customer support cases may follow various sequences of statuses. Each path is a variant, and the most common ones have a high record count.

In the settings panel on the right of the visualization tab, you'll find a listing of each process flow variant. Each time an opportunity, case, or object completes a variant, it counts as a record. The activities column indicates the number of activity steps in that particular variant.

The line color and thickness in the visualization tab are explained in the key at the bottom left. These colors represent relative times for all line segments in the process being visualized. For instance, red segments might take longer, but it doesn't necessarily indicate a problem. Context matters; for instance, a red segment after sending an email may simply reflect a customer response time.

The Hubbl Score is a powerful metadata scoring system that quietly evaluates your org behind the scenes and translates complex system signals into crystal-clear guidance. The Hubbl Score helps users identify, understand and communicate optimization opportunities in their Salesforce configurations. It rolls up the severity of issues found and the overall quality of changes made to the organization into a relative score that allows users to prioritize remediation efforts, understand where their Salesforce org needs improvement and monitor progress.

It takes about two minutes to create a Hubbl Diagnostics account (even from your mobile device) and start monitoring your org at hubbl.com/get-started. When you start monitoring your Salesforce org with Hubbl, the metadata is analyzed and passed through scoring thresholds in an AI recommendation engine to identify org optimization opportunities. The results are summarized into the Hubbl Score and displayed once your org scan is complete.

The score considers two main factors: the severity of the issues found (high, medium, or low) and your org size (the amount of metadata). High-severity issues undergo a logarithmic transformation that heavily penalizes their presence, while medium and low-severity issues are treated differently, with varying degrees of impact on the score. It also accounts for the ratio of number of issues which exist to total number of metadata, which help to make the score relevant to different org sizes.

1. High severity recommendations will have higher impact than before

2. Low severity recommendations will have less impact on the score, as they are calculated exponentially

3. Increase scalability of the scoring algorithm from the smallest org to the largest org

4. Increased transparency by sharing the expected impact to the overall score that can be achieved by addressing each recommendation

A low Hubbl Score indicates that there are significant issues within your Salesforce. It suggests that there's a need for immediate remediation to improve the health and performance of the org.

A high Hubbl Score indicates that your Salesforce has fewer issues, is well-maintained and secure. However, even with a high score, continuous monitoring and improvement are still necessary.

Each recommendation shows the impact of solving it on the Hubbl score. This helps you prioritize remediation based on severity. We automatically prioritize recommendations in the Hubbl Action Plan so you always have ideas for what to do next. 

If the org you are scanning restricts network access to your Salesforce org then you will have to add Hubbl Technologies' IP addresses as trusted. Follow the instructions in this Salesforce Help article.

Hubbl Technologies IP addresses to add as trusted:

44.225.168.119
54.244.175.74

NOTE: The Start and End IP Address will be the same.

The number of API calls differs per org. For an average org it could be in the high 100s but for a really large org it could be in the 1000s. This is dependent on the number of objects and fields on the objects. We do two calls per object, one call per 100 fields on an object and various other one off calls.

We perform only read-only operations on connected orgs:

1. We make GET requests to the Metadata API
2. We make GET requests to the REST API
3. We make GET requests to the Tooling API


Due to the way metadata list/retrieve permissions work in Salesforce, we do require Modify Metadata, because there is no read-only equivalent to that permission.

We will never modify client data or metadata.

For the REST calls, we never retrieve transactional data from objects; we only run what's called aggregate count queries.  These types of queries simply return a number representing a count of records. We use this to get record counts by object, and we use this to count empty fields to help identify field utilization percentages. If a scanning user does not have Create/Read/Update/Delete (CRUD) or Field Level Security (FLS) permissions on certain objects and fields, we cannot report on them.

Running a scan with Hubbl Diagnostics will have no performance impact to normal business operations in your Salesforce org.

However, there are two considerations:

1. During the short period of time (typically minutes) that it takes to temporarily extract the metadata to perform our aggregated analysis, deployments and large data loads to the Salesforce org will not be possible.

2. In the rare scenario that the Salesforce org is closely approaching its API call limits, be aware that Hubbl Diagnostics does consume API calls to analyze the org. For an average org, the number of API calls could be in the high 100s, but for a large org these could be in the 1000s - all dependent on the number of objects and fields in the org.

In addition, you may also choose to schedule your Hubbl scans to run off-hours.

When authorizing the Hubbl Diagnostics connected app during the org scanning process, you'll be prompted to grant four specific permissions:

1. Access the identity URL service: Hubbl retrieves a limited set of user information for troubleshooting and the confirmation page scan flow.

2. Manage user data via Web browsers: This permission allows Hubbl to capture certain org information not accessible through APIs but visible in Setup pages.

3. Manage user data via APIs: Hubbl requires this permission to collect metadata, configuration details, usage limits, and aggregate record and field count information.

4. Perform requests at any time: This permission enables Hubbl to support scheduled and repeating scans. For one-time scans, access tokens are automatically deleted upon scan completion, ensuring that Hubbl cannot reconnect post-scan regardless of this permission.

Hubbl Process Intelligence starts by visualizing your process using Salesforce field history logs. It creates a flow diagram that displays the times and frequencies of each path taken through the process, also known as variants. These variants can be further analyzed. For instance, you can explore the fastest path through the process, paths with the most steps, or paths followed by specific products. These analyses can be done manually or automated within the product.

Hubbl Process Intelligene simply requires access to Salesforce field history logs, which are available once the tool is installed in your Salesforce organization for analysis. You can specify the object, date range, and attributes you need, and an easy-to-use wizard takes care of the rest. Additionally, event logs from other applications can be imported into custom Salesforce objects for analysis.

The primary output is an interactive process visualization that can be customized with filters. Additionally, you will receive a series of observations about the process, leading to actionable business insights.

The ideal amount of historical data for analysis depends on several factors:

Volume of Records: Ideally, you should have hundreds or thousands of records (instances of the process being executed) to conduct meaningful analysis.

Annual Cycles: To capture a full year's process, approximately 14 months' worth of history is recommended.

Process Lifecycle Time: Consider the duration of your process lifecycle. For instance, if your sales cycle spans 12 months, aim to use 18 months of data for a comprehensive view. If a service ticket is typically resolved in one day, then three months' worth of ticket data should suffice if there's a significant volume.

We would be sad to see you go! But if you choose to not renew your subscription to Hubbl Technologies, here’s what happens:

1. You will retain access to your advanced scans until the end of your subscription.

2. On your subscription end date all of your existing scans will revert back to basic scans.

At any time, you can check the amount of licenses you have used by accessing your Account in Hubbl.

You can find your Account on the top right hand corner of Hubbl Diagnostics by clicking your name and then selecting Account. There, you will be able to review your Account Name, Account Admin, your total number of licenses purchased, and the amount that are still available for use. You will also be able to dial down into the usage details of the licenses you have already used, such as Install Date, Usage Date, Organization ID and Allocation date.

This tab is designed to make it easy for you to manage and track your licenses, ensuring you always have the necessary number of licenses to perform as many scans as you need.

To add users to your Hubbl account, you need to have purchased a license.

Ask your users to sign up and then submit a support case with the request, we will get them added to your account, so they can access Hubbl  licenses and premium features.

Yes! Users can easily share results with other Hubbl users within your company.

Sharing outside your organization is available for Premium and Enterprise customers. It is not available in the Basic.

The easiest solution would be to run the scan as a System Administrator. However, if you want to be more specific with the permission assignments, the following permissions would be needed:

Modify Metadata - Required
This is necessary for Hubbl to retrieve and analyze metadata from the org.

Approve Uninstalled Connected Apps - Required
This is a new permission added by Salesforce on August 28, 2025. This is necessary for any Connected App like Hubbl that accesses an org without installing a package.‍


View All Data, or appropriate Object CRUD + Field Level Security (FLS) - Required
Hubbl can only provide object and field analysis on fields that the user running the scan has read access to. Any objects or fields where permissions are not available will be omitted from the scan output.

Install Packages and Manage Package Licenses - Optional
In order to provide package analysis, Hubbl requires both of these permissions. Salesforce does not have a discrete read-only permission to view installed packages.

ViewHealthCheck - Optional
For some recommendations, Hubbl relies on Health Check information. Without this permission, these recommendations will not be available.