# Salesforce for Confluence


# Introduction

Seamlessly integrate Salesforce data into your Confluence pages and transform the way your teams collaborate, driving productivity!

**Single Source of Truth**

Our add-on bridges the gap between Salesforce and Confluence. Use live links to Salesforce Object and Salesforce Lists within Confluence documents to enhance alignment across teams.

<div data-full-width="true"><figure><img src="/files/ACreXOZMzq1KxkzOGa3h" alt="" width="563"><figcaption></figcaption></figure></div>

**Seamless Salesforce Integration**

Our add-on allows you to effortlessly integrate Salesforce data into Confluence, ensuring everyone in your team to have the most up-to-date information.

With our intuitive SOQL editor, you can customize queries to meet your specific needs. Leverage and reuse SOQL Templates. Users can easily complete the templates by adding any missing information as needed.

**Define your Salesforce Template**

<figure><img src="/files/kH14Ju2m31z86sADiW2x" alt=""><figcaption></figcaption></figure>

**Reuse when inserting Salesforce List macro**

<figure><img src="/files/DnxyODtfArTzNKNnX2i8" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/7bJ5mTIOozYj3G5iJWfW" alt=""><figcaption></figcaption></figure>

**Customizable and Ready-to-Use Templates**

Elevate your business processes with customizable templates tailored to your requirements. Whether it's Account Plans, our add-on empowers you to create personalized templates or leverage our out-of-the-box options for quick and effective documentation. One click, and your document is ready, filled with live Salesforce data.

<figure><img src="/files/3GfhNuFD7OqCdQ5Wf5Td" alt=""><figcaption></figcaption></figure>

&#x20;

#### Centralized Salesforce Connection Management

Manage Salesforce Connections and control access by specifying which user groups are authorized to utilize the connection.

<figure><img src="/files/RoA9nxjp1UkI94kVezvl" alt=""><figcaption></figcaption></figure>


# Getting Started

For Confluence Administrator, please follow [Configure Salesforce Connection](/atlassian-cloud/salesforce-for-confluence/administrator-guide/configure-salesforce-connection)

For Confluence Users, head to [User Guide](/atlassian-cloud/salesforce-for-confluence/user-guide)


# Administrator Guide


# Configure Salesforce Connection

Before users can use the add-on, you must set up Salesforce Connection.

### Go to Salesforce Connection page

Click on **Confluence administration ⚙️** on the top right corner.

Locate **Salesforce** menu on the left sidebar and click **Connections**.

<figure><img src="/files/FryJuzykU7CrPQUocYuX" alt=""><figcaption></figcaption></figure>

### Adding Salesforce Connection

Click **Add Connection**.

<figure><img src="/files/CbeNMRgL9zUoDuTFJFjv" alt=""><figcaption></figcaption></figure>

Input your **Connection name**. Connection name will be used to distinguish connection between different Salesforce instances and credentials.

You can specify user groups that are **authorized** to access and utilize this connection. By default, **Confluence admins** can use all connections.

Finally, click **Save**.

### Authorizing Salesforce Connection

<figure><img src="/files/loi2N6adWqoDAzfTB3ud" alt=""><figcaption></figcaption></figure>

Click **Authorize** to authenticate connection to your Salesforce instance. \
Alternatively, click **Authorize to Sandbox** to authenticate to Sandbox.

Please make sure you are logged in before clicking Authorize.

<figure><img src="/files/OQjrxMVjkrNjsRbaiCg0" alt="" width="563"><figcaption></figcaption></figure>

You will be redirected to Salesforce page. Click **Allow** when prompted.

<figure><img src="/files/ZqVMAnngpmVnra92P2S3" alt=""><figcaption></figcaption></figure>

The Status column will be updated to **Connected** along with Instance URL.

{% hint style="success" %}
Congratulations! Users can now use the add-on
{% endhint %}

### Updating Salesforce Connection

#### Setting Connection as default

<figure><img src="/files/ugqKe6CltS5kmJsi6iWY" alt=""><figcaption></figcaption></figure>

To set Connection as default, click the **More (...)** button.

Click on **Set as default.**

Default connection will be used as the first option when selecting connections in the edit dialog.

#### Manage Connection Permissions

You can limit user groups that can use the connection within the add-on.&#x20;

To do that, click **Edit connection**.

<figure><img src="/files/fh7LqOK3t7TLe9ILXLCR" alt=""><figcaption></figcaption></figure>

In the **Authorized user groups** section, search user groups that can access the connection.

You can also update the Connection name if needed.

Finally, click **Save** once you are done.


# User Guide


# Scenario: Displaying Key Account Plans

Use Case: Displaying Key Account Plans using Salesforce Data with Confluence Blueprints

Prerequisite: [Configure Salesforce Connection](/atlassian-cloud/salesforce-for-confluence/administrator-guide/configure-salesforce-connection)

Macros used: [Salesforce Object Macro](/atlassian-cloud/salesforce-for-confluence/user-guide/salesforce-object-macro) [Salesforce List Macro](/atlassian-cloud/salesforce-for-confluence/user-guide/salesforce-list-macro) [Salesforce Templates](/atlassian-cloud/salesforce-for-confluence/user-guide/salesforce-templates)

Locate **Templates** at the top section.

Select **Salesforce Account Plan.** Click **Use Template**.

<figure><img src="/files/6HNCaU1kmPKfKLPGbjjs" alt=""><figcaption></figcaption></figure>

A page will be created based on the template.

<figure><img src="/files/Cj5UzZQCkzJSDR8N2Kmi" alt="" width="563"><figcaption></figcaption></figure>

Edit **Salesforce Object Macro**.

<figure><img src="/files/0lrmkpcVjMvoYYBF3Tjc" alt=""><figcaption></figcaption></figure>

Enter Account **Object ID** or paste **Salesforce account URL**. The URL will be in the following format `<your-instance>.develop.lightning.force.com/lightning/r/Account/<Object ID>/view`

<figure><img src="/files/Bp633kv5d1HfE4eH4UEQ" alt=""><figcaption></figcaption></figure>

Click **Save** to update the macro

The **Salesforce List** will be automatically updated.

<figure><img src="/files/vPfuskXGltsjujQaHubf" alt=""><figcaption></figcaption></figure>

To Learn More how this works, check out [Template Variables](/atlassian-cloud/salesforce-for-confluence/user-guide/template-variables)


# Salesforce Object Macro

To setup **Salesforce Object Macro**, go to your Salesforce Object page.

Copy the entire link.

<figure><img src="/files/utlj5ncWAfKMBAnos5ar" alt=""><figcaption></figcaption></figure>

Paste the link in a Confluence Page. The pasted link will be converted to Salesforce Object Macro.

<figure><img src="/files/BtSLMqJSstgOHyFchXfr" alt=""><figcaption></figcaption></figure>

You can edit the macro to display more fields.

<figure><img src="/files/R2OLPZhkVQHmw6UFp817" alt=""><figcaption></figcaption></figure>

Since the **Field(s) to display** will be converted to SOQL query, you can utilize SOQL Select Functions, for instance, to format the AnnualRevenue.

<figure><img src="/files/WsG5Lrge9wcaxrxqSFU1" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/iPS8t9Q6zqblVOeXoX3v" alt=""><figcaption></figcaption></figure>

Alternatively, you can also insert the macro manually.

Type **/sales**.&#x20;

Select **Salesforce Object.**

<figure><img src="/files/6rOWbsbWUxxleaM4grMN" alt=""><figcaption></figcaption></figure>

Select your desired connection and type the Object ID.

By default, Salesforce Object Link will be displayed as the Object's Name.

<figure><img src="/files/SvDFdkjVKy3LP6UJJxf8" alt=""><figcaption></figcaption></figure>

To display more fields, select Field(s) to display. When more than one field is selected, a table will be shown instead.

<figure><img src="/files/U5fHBUgskWJMCJOekvZm" alt=""><figcaption></figcaption></figure>

Finally, Click **Insert** to save.

### Template Variables

Salesforce Object Macro enables you to use Object ID as template variable. To learn more, go to [Template Variables](/atlassian-cloud/salesforce-for-confluence/user-guide/template-variables)


# Salesforce List Macro

Salesforce List Macro enables you to display a list of Salesforce objects in a table based on SOQL queries.

To setup Salesforce List Macro, go to your desired confluence page.

Type **/sales.**

Select **Salesforce List.**

<figure><img src="/files/Gjoiijyb2QqtPAfcjj3U" alt=""><figcaption></figcaption></figure>

Select **Connection**.

There are two ways to define Salesforce List Macro:

1. Manually inserting SOQL in each macro
2. Use pre defined query template

### 1. Manually inserting SOQL in each macro

<figure><img src="/files/h8rD1KmdirxleoRE532z" alt=""><figcaption></figcaption></figure>

Select **Use SOQL**.

Type your **SOQL query**.

Click **Preview**. Then, click **Insert**.

<figure><img src="/files/sIumLoM3O4dK1yKKazWe" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/zoYuoVLoymJwaF47Uy5U" alt=""><figcaption></figcaption></figure>

### Use pre-defined Query Template

Inserting SOQL manually gives you flexibility. However, you can use **Query Template** to enhance reusability.

Refer to [Salesforce Templates](/atlassian-cloud/salesforce-for-confluence/user-guide/salesforce-templates) to setup Templates.

<figure><img src="/files/c4cGcz8Y60CmhVI7Mm9i" alt=""><figcaption></figcaption></figure>

Select your desired **Query template**.

<figure><img src="/files/q4THSwwoNN2jWNTfossS" alt=""><figcaption></figcaption></figure>

If the template doesn't contain variables, you can click **Insert**.

For template containing [Template Variables](/atlassian-cloud/salesforce-for-confluence/user-guide/template-variables), you will need to fill in the gaps.&#x20;

<figure><img src="/files/yerVRRawqxpyEhXrg5jJ" alt=""><figcaption></figcaption></figure>

In this case, you need to fill in the variable Account.

<figure><img src="/files/YqyaGsNkNtpi1vjs1eoy" alt=""><figcaption></figcaption></figure>

Click **Insert** once you are done.


# Salesforce Templates

To facilitate reusability of Salesforce List, you can define Salesforce Template.

Locate **Apps** in the top navigation bar.

Select **Salesforce Template**.

<figure><img src="/files/QHTBUbdGms4HZyWXzDZ0" alt=""><figcaption></figcaption></figure>

### Adding new template

Click **+** to add new template.

<figure><img src="/files/K8J30L1koeC7LCr9bf5P" alt=""><figcaption></figcaption></figure>

Input your desired Template Name and SOQL Query.

<figure><img src="/files/1zlbQwn7nY4Gd1fe5c8x" alt=""><figcaption></figcaption></figure>

Click **Preview** before saving template.

Once your result is successfully previewed, click **Save**.

<figure><img src="/files/0XIaB98qOwqyHm9lEN2c" alt=""><figcaption></figcaption></figure>

### Using Template Variables

**Template variables** enable users to input variable values when inserting **Salesforce List** macro.

Use the syntax **{{VARIABLE\_NAME}}** in your SOQL query.

<figure><img src="/files/P3FhlhDn9hdCQRr53Kdp" alt=""><figcaption></figcaption></figure>

When inserting Salesforce List macro, users just need to fill in the variables.

In the example below, users only need to enter `Fields` variable to select relevant fields.

<figure><img src="/files/VlJcYdDgUXH08T5Uf8su" alt=""><figcaption></figcaption></figure>


# Template Variables

Template Variables is the core functionality of the add-on. This is what sets our add-on apart from the others.

Template Variables enables the creation of customizable templates. You can use it to insert dynamic values into the query. Users simply fill in the gaps, making complex queries straightforward.

<figure><img src="/files/ysbVZOJvk7wUTDnH6itO" alt=""><figcaption></figcaption></figure>

In the image above, a Query Template is defined to find Opportunities based on the matching AccountId. Notice the template variable **{{Account}}**.

You can use the defined template in SOQL List Macro.

Users utilizing this template simply need to input Account value.

<figure><img src="/files/ol1gr9ekmtBAM50Wp5fc" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/kbdOgTEAviDBZ9OsXRVT" alt="" width="563"><figcaption></figcaption></figure>

Template Variables allow the same Query Template to be reused across different situations.&#x20;

<figure><img src="/files/vDBAbQ3bm19mYYrTz52o" alt="" width="563"><figcaption><p>Account Opportunities Template used for Account #1</p></figcaption></figure>

<figure><img src="/files/YKFv2iDe8VR6UxqPb7iz" alt="" width="563"><figcaption><p>Account Opportunities Template used for Account #2</p></figcaption></figure>

### Syncing Template Variable value across multiple macros

Beyond this, Template Variables enables integration between Salesforce Object and Salesforce List macros, making data handling more flexible and efficient.

In the example below, two Salesforce List macros are added on the same Confluence page.

Both of them require the value of **Account** to be filled. When **Account** value is updated on one macro, the value of the same variable will be updated on the other macro as well.&#x20;

<figure><img src="/files/QlsM7eLDvrYvNDDX4g0O" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/14JFw5a5oNgvCGeogBKP" alt=""><figcaption></figcaption></figure>

In addition, you can link both macros to a Salesforce Object macro.

Select the option to **use Object ID as a template variable** when defining Salesforce Object Macro. Enter **Account** for variable name.

{% hint style="info" %}
To link variable in Salesforce List and Salesforce Object macro, the variable must have the **same** name
{% endhint %}

<figure><img src="/files/8zuuHWO3V3SU4MPRNtTH" alt=""><figcaption></figcaption></figure>

The AccountId values needed for the two lists will be automatically filled using the value from Salesforce Object Macro.

<figure><img src="/files/C3yF6w1V9Ib2I8Tw0bjJ" alt=""><figcaption></figcaption></figure>

Template Variables allows you to tailor complex Salesforce process to reusable template.

The possibilities are endless!


# Confluence Blueprints

Salesforce Object and Salesforce List macro utilizing Template Variables integrates seamlessly with Confluence Templates and Blueprints, enhancing efficiency and user experience through reusable templates.

You can create  **Space** templates or **Global** templates.

Please follow this page to create your blueprints.

Space: <https://support.atlassian.com/confluence-cloud/docs/create-a-template/>

Global: <https://support.atlassian.com/confluence-cloud/docs/create-a-global-template/>

The add on comes with **Salesforce Account Plan** as an example.

<figure><img src="/files/Hj3UdrrLN6cpcxABEXJs" alt=""><figcaption></figcaption></figure>

&#x20;Go to [Scenario: Displaying Key Account Plans](/atlassian-cloud/salesforce-for-confluence/user-guide/scenario-displaying-key-account-plans) to examine further.


# SOQL List Results Indexed in Confluence Search

The **SOQL List Macro** has been enhanced to improve searchability within Confluence.&#x20;

Results returned by the SOQL List Macro are **indexed** by Confluence’s built-in search functionality.&#x20;

This allows users to search for Salesforce data directly from the Confluence search bar, which will point them to the specific Confluence page containing the macro and its associated Salesforce data.

As an example, consider the following confluence page, using SOQL List Macro to display contacts:

<figure><img src="/files/k2rkkizk4dinXKCVnurU" alt=""><figcaption></figcaption></figure>

Searching for "Tim Barr" in the SOQL List Macro results will direct users to the specific Confluence page containing the macro.

<figure><img src="/files/ZJlE2ADEnDkcLvws0HeO" alt=""><figcaption></figcaption></figure>

### How often is the search index updated?

The page will be updated with the latest Salesforce data whenever the SOQL List Macro is viewed, provided there have been changes to the data. When this occurs, a new page version will be created with the comment "Index Salesforce macro."

<figure><img src="/files/VlTTEPKARb9I4oQIq0eb" alt="" width="375"><figcaption><p>Page versions can be viewed by clicking (...) More actions > Page history</p></figcaption></figure>

It may take some time for Confluence Cloud to reflect these updates in its search results.

If you would like to test the searchability of your SOQL List Macro, you may copy the existing macro to a new Confluence page. Newly created pages are indexed more quickly by Confluence Cloud.

Please note that:

* Only the first occurrence of the term in a page will be shown in Confluence's search results
* Only the first 2,000 items in the list are searchable

### Can I disable indexing?

Yes, you can disable SOQL List indexing on the Confluence Administration > Salesforce > Settings page.

<figure><img src="/files/l51XJO5eo9ntLBf1vBc6" alt=""><figcaption></figcaption></figure>


# Editable Table Headings

Users can now customize table headings within Confluence pages where Salesforce data is displayed.

This update gives you greater flexibility to customize your data display in Confluence.

<figure><img src="/files/NBthsA78l4hL8DxL27LB" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/EUfkHe41rQ2Y4029wYjo" alt=""><figcaption></figcaption></figure>

### Support and Assistance

If you need any support or assistance, please feel free to reach out to our team. \
We’re here to help you make the most out of Salesforce for Confluence.


# Security Statement

## Overview <a href="#securitystatement-overview" id="securitystatement-overview"></a>

This Security Statement explains how our data is stored and what informations are collected from you.

## Data and Access <a href="#securitystatement-data" id="securitystatement-data"></a>

* We use AWS to host our cloud apps. Daily backups are performed every 24 hours.
* We do not track any private/sensitive information.
* We never store any connected integrations data on our servers or database. The only thing we store is OAuth details. Data may be cached in memory for optimisation purposes, but it will expire once time to live reaches zero.
* Application uses HTTPS and JWT as a validation.

## Billing, Licensing and Privacy Policy

We rely on Atlassian for billing and licensing. Therefor, any personal information is collected and processed by Atlassian, governed by the Atlassian Marketplace Terms of Use and the Atlassian Privacy Policy.&#x20;

We collect information to provide better services to our customers. The types of personal information or personal data we may collect about you include:

* your name;
* your contact details, including email address, mailing address and/or telephone number;&#x20;
* your demographic information, such as postcode;
* your preferences and/or opinions;
* details of the services we have provided to you and/or that you have enquired about, and our response to you;
* your browser session and geo-location data, device and network information, statistics on page views and sessions, acquisition sources, search queries and/or browsing behavior;
* information about your access and use of our services, including through the use of Internet cookies, your communications with our services, the type of browser you are using, the type of operating system you are using and the domain name of your Internet service provider;
* additional personal information that you provide to us, directly or indirectly, through your use of our services, associated applications, associated social media platforms and/or accounts from which you permit us to collect information; and
* any other personal information requested by us and/or provided by you or a third party.

## Customer Support

When you contact us for support, we will do our best to respond within 24 business hours from the time of your request. As we are a small company, we appreciate your patience.

## Contact

If you have any questions, please do not hesitate to contact us at **<support@upsmith.app>**


# Scrybe External Data Objects and Query for Jira


# Overview

{% hint style="info" %}
This app is built with **Atlassian Forge**. It is running on Atlassian hosted infrastructure.
{% endhint %}

**Scrybe External Data Objects and Query for Jira** empowers Jira users to view and interact with external data integration (Salesforce, Hubspot, etc) directly within Jira issues.\
\
It enables teams to **link, search, and query external data objects** directly inside Jira issues, eliminating the need to switch between multiple platforms.

The app provides two core features under Jira Issue Panel:

1. **External Data Objects**
2. **External Data Query**

### **1. External Data Objects**

External Data Objects allow you to link external data entities to Jira issues.\
\
Each configured object (e.g. Salesforce Account, Contac&#x74;*,* Case) appears as a dedicated tab inside Jira issue view, giving users instant access to related external data.\
\
Within each tab, you can add objects and configure which fields will be displayed in the table view. Moreover, you can mirror object field values to a Jira field for JQL search, reporting, and automation. You can also configure access control to specify which user groups are allowed to access each tab.

<figure><img src="/files/MLjnKCDCMNIygFK1FI7M" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/HpitT0BhwSISJ2DYSu8t" alt=""><figcaption></figcaption></figure>

**Key Features**

* **Multiple Integrations**\
  Connect Jira with external systems such as Salesforce, HubSpot and more.
* **Customizable Object Tabs**\
  Each configured object (e.g. Case, Account, Deal) appears as its own tab in the Jira issue view.
* **Mirror Fields**\
  Sync and mirror external field values into Jira fields, making them:
  * Searchable via JQL
  * Visible in Jira filters and reporting
  * Apply transformations such as `SUM`, `COUNT`&#x20;
* **Permission Aware**\
  Each tab can be configured with access controls to limit which users or groups can view/modify it.

### **2. External Data Query**

External Data Query lets you configure **dynamic queries** to fetch live data from external applications directly within Jira issues.\
\
Each configured query appears as a tab in the issue view, giving users the ability to run and view contextual data in real time.

<figure><img src="/files/EYX0aleDTfuM0Lo0YXKP" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/guGn4BefEKG7WNVnnzz0" alt=""><figcaption></figcaption></figure>

**Key Features**

* **Dynamic Query Configuration**\
  Create custom queries to retrieve external data, fully configurable in each Space.
* **Real-Time Data Access**\
  Fetch data directly from external systems on demand.
* **Smart Values for Jira Issues**\
  Use Jira issue fields dynamically in your queries with the syntax:

  ```
  {{issue.[property]}}
  ```

  **Example**

  ```
  SELECT Id, Name, Account.Name, Owner.Name 
  FROM Contact 
  WHERE Email = '{{issue.reporter.emailAddress}}'
  ```
* **Query Variables**\
  Define query variables for more flexible query using the format:

  ```
  {{variable_name}}
  ```

  **Example**

  ```
  SELECT Id, Name, Owner.Name 
  FROM Account 
  WHERE Name LIKE '{{AccountName}}%'
  ```

  \
  When query variables are specified, users will be prompted to enter the values directly in the Jira issue. This makes the query dynamic, allowing you to create reusable templates. The entered values are saved and automatically applied the next time the tab is loaded.

  <figure><img src="/files/gGaqtCXAnH78RyvVlSSF" alt=""><figcaption></figcaption></figure>
* **Access Control**\
  Control which users or groups can view each configured query tab.

***

#### **Example Use Case**

**Scenario:**\
A support engineer is investigating a Jira issue linked to a Salesforce Case or HubSpot Ticket.

1. **External Data Objects** configuration adds tabs (e.g. Case, Account, Contact) to the Jira issue based on the connected systems.
2. The engineer searches for and links the relevant Case or Ticket from Salesforce, HubSpot, or other integrated platforms.
3. **External Data Query** automatically runs a query using smart values from the Jira issue (e.g. the reporter’s email) to retrieve related contacts, accounts, or tickets.
4. The engineer can also:
   * Query and display related **tickets**, **accounts**, or **contact details**.
   * Use mirrored fields and transformations to enrich Jira with external data.

This workflow gives the support engineer a full customer view directly inside Jira, without switching between systems.

***

### **Benefits**

* Centralize external customer and business context inside Jira.
* Eliminate tab switching between Jira and external applications.
* Access live, query-driven insights.
* Enable cross-platform search and reporting via mirrored fields.
* Search external field values with mirror fields and apply transformations if needed.
* Limit user access using configurable access controls.

**Additional Resources**

If you need further assistance, don’t hesitate to contact our support team at **<support@upsmith.app>**. We’re always happy to help!


# Getting Started

For Jira Administrator, please take a look at [Administrator Guide](/atlassian-cloud/scrybe-external-data-objects-and-query-for-jira/administrator-guide)

For Jira Users, head to [User Guide](/atlassian-cloud/scrybe-external-data-objects-and-query-for-jira/user-guide)


# Administrator Guide


# Getting Started

This page provides a step by step guide to configure the add on.

If you'd like to check the plugin overview to explore the plugin's inspiration and use cases, you can refer to [Overview](/atlassian-cloud/scrybe-external-data-objects-and-query-for-jira/overview).\
\
**Step by step guide:**

{% hint style="info" %}
**NOTE:** Configuration is managed separately for each space.
{% endhint %}

1. Navigate to Space Settings.<br>

   <div align="left" data-full-width="true"><figure><img src="/files/wMEQk03B0ygarlduOSlH" alt="" width="375"><figcaption></figcaption></figure></div>

2. Under **Apps**, click **Scrybe External Data Objects and Query**.<br>

   <figure><img src="/files/Pyfk7ZCMHOw7XjWH1aoc" alt=""><figcaption></figcaption></figure>

3. Find your desired integration and click **Connect**.

4. Sign in with your credentials and complete the OAuth flow. It is recommended to connect using an admin account.

5. Once connected, click **Manage** to configure External Data Objects and External Data Query settings.

\
To set up the Salesforce Object and Query Panel, check [Configure Salesforce Integration](/atlassian-cloud/scrybe-external-data-objects-and-query-for-jira/administrator-guide/configure-salesforce-integration).

To set up the HubSpot Object and Search Panel, check [Configure HubSpot Integration](/atlassian-cloud/scrybe-external-data-objects-and-query-for-jira/administrator-guide/configure-hubspot-integration).

\
**Additional Resources**

If you need further assistance, don’t hesitate to contact our support team at **<support@upsmith.app>**. We’re always happy to help!


# Configure Salesforce Integration

{% hint style="info" %}
Please make sure you are connected to Salesforce. Otherwise, head to [Getting Started](/atlassian-cloud/scrybe-external-data-objects-and-query-for-jira/administrator-guide/getting-started)
{% endhint %}

### Object Views Configuration

This section lists the details for configuring object views.

Step by step guide:

1. Click on add object view<br>

   <figure><img src="/files/cn0flKULGZF80T6eL1HN" alt=""><figcaption></figcaption></figure>

2. In the dialog, the **Title of view** will be used as the tab name in the Jira issue panel. You can configure multiple tabs, allowing you to display different objects within the same Jira issue.\
   \
   \- Select the Salesforce object you want to use as the main object. \
   \- You can configure which fields will appear in the table view. \
   \- You can also specify which user groups are allowed to access the tab.<br>

   <figure><img src="/files/PFYLkCMAAkCtIf7OQkpQ" alt=""><figcaption><p>Salesforce object view in JIRA issue</p></figcaption></figure>

   <div align="left"><figure><img src="/files/smfXJXa2kLSRLOFnOgnu" alt="" width="375"><figcaption><p>Edit dialog for Salesforce object view</p></figcaption></figure></div>

3. Click **Save** once you are done.

### Query Views Configuration

This section lists the details for configuring query views.

Step by step guide:

1. Click on add query view.<br>

   <figure><img src="/files/kvGOJLAk46XmaOGcxhvR" alt=""><figcaption></figcaption></figure>

2. In the dialog, the **Title of view** will be used as the tab name in the Jira issue panel. You can configure multiple tabs, allowing you to display different queries within the same Jira issue.<br>

   <div align="left"><figure><img src="/files/QuSRQAdcMn2IRU4Myjr6" alt="" width="375"><figcaption><p>Edit dialog for Salesforce query view</p></figcaption></figure></div>

3. In the SOQL query section, you can enter the SOQL query you want to run. There are three types of queries:

   1. **Query with no variables**\
      A standard SOQL query with fixed values.\
      Exampl&#x65;*:* `SELECT Name FROM Account`
   2. **Query with issue variables**\
      You can reference values from the Jira issue (e.g., reporter email) to make the query dynamic.\
      Example:

      ```
      SELECT Id, Name, Account.Name, Owner.Name 
      FROM Contact 
      WHERE Email = '{{issue.reporter.emailAddress}}'
      ```

      With this, the query will automatically run using the issue reporter’s email.
   3. **Query with query variables**\
      These queries require the user to input values directly in the Jira issue. Once entered, the values are saved and will be used automatically the next time the tab is loaded.\
      Example:

      ```
      SELECT Id, Name, Owner.Name 
      FROM Account 
      WHERE Name LIKE '{{AccountName}}%'
      ```

      You can then provide the variable value within the Jira issue.<br>

      <figure><img src="/files/KOmYe3JfdNUodJMTt9wc" alt=""><figcaption><p>Salesforce query view in JIRA issue</p></figcaption></figure>

   \
   You can also specify which user groups are allowed to access the tab.<br>

4. Click **Preview** to verify that the query runs successfully. Once everything looks correct, click **Save**.

\
**Additional Resources**

If you need further assistance, don’t hesitate to contact our support team at **<support@upsmith.app>**. We’re always happy to help!


# Common Errors on Salesforce OAuth

#### Overview

When connecting to Salesforce, there are several common OAuth errors you might encounter. This guide walks through the typical causes and provides step by step actions to resolve each one.

{% hint style="info" %}
**NOTE:** It is recommended to connect with **System Administrator**
{% endhint %}

### **OAUTH\_APPROVAL\_ERROR\_GENERIC An unexpected error has occurred during authentication**

**Cause:**

Due to the following [change](https://help.salesforce.com/s/articleView?id=005132365\&language=en_US\&type=1), Salesforce Connected apps might need to be installed in an organization before OAuth authentication can be completed.

**Resolution Steps:**

When the initial user goes through the OAuth process, the app will be listed in the org and an admin will need to install the connected app.

1. Log in to Salesforce as a **System Administrator**.
2. Head to **Setup.**
3. Search for "Connected Apps OAuth Usage"<br>

   <figure><img src="/files/1ru7kLzSfSot524XhA5z" alt=""><figcaption></figcaption></figure>
4. Find "Scrybe Salesforce for Jira" and click the Install button<br>

   <figure><img src="/files/v6wrCp6U3eZHbMdFhJEc" alt=""><figcaption></figcaption></figure>

Alternatively, you can also do the following:<br>

If the above option is not feasible, a Salesforce Administrator can grant a permission to the user's profile.

1. Login as Salesforce Administrator and navigate to **Setup**.
2. In the Quick Find box, search for "Profiles" and open the user’s profile.
3. In the "System Permissions" section, they should enable the "Approve Uninstalled Connected Apps" permission.<br>

   <div align="left"><figure><img src="/files/Ule0N3JEa9ZpTbGTbqOt" alt=""><figcaption></figcaption></figure></div>

After the Salesforce Administrator completes the steps above, ask your users to do the following before attempting to connect again:\
• Clear their browser cache and cookies\
• Retry connecting to Salesforce again

### **OAUTH\_ERROR=TRUE**

Ensure that the user’s profile in Salesforce includes the "**API Enabled"** permission. This permission is essential for API access within your organization. Without it, the user will not be able to connect their personal Salesforce account to send activities.

### **OAUTH\_APP\_BLOCKED**

Verify that Scrybe Salesforce for Jira application is not blocked. If it is blocked, please unblock the app to restore access.

\
**Additional Resources**

If you need further assistance, don’t hesitate to contact our support team at **<support@upsmith.app>**. We’re always happy to help!<br>


# Configure HubSpot Integration

{% hint style="info" %}
Please make sure you are connected to HubSpot. Otherwise, head to [Getting Started](/atlassian-cloud/scrybe-external-data-objects-and-query-for-jira/administrator-guide/getting-started)
{% endhint %}

### Object Views Configuration

This section lists the details for configuring object views.

Step by step guide:

1. Click on add object view<br>

   <figure><img src="/files/jtLhb686z6VLz4EmpPG9" alt=""><figcaption></figcaption></figure>

2. In the dialog, the **Title of view** will be used as the tab name in the Jira issue panel. You can configure multiple tabs, allowing you to display different objects within the same Jira issue.\
   \
   \- Select the HubSpot object you want to use as the main object. \
   \- You can configure which fields will appear in the table view. \
   \- You can also specify which user groups are allowed to access the tab.<br>

   <div align="left"><figure><img src="/files/4wejhrGfFtbLpQ8OXCtu" alt="" width="375"><figcaption><p>Edit dialog for HubSpot object view</p></figcaption></figure></div>

   <figure><img src="/files/pHdAeYtxaRYB8dV3Ozjf" alt=""><figcaption><p>HubSpot object view in JIRA issue</p></figcaption></figure>

3. Click **Save** once you are done.

### Search Views Configuration

This section lists the details for configuring query views.

Step by step guide:

1. Click on add query view.<br>

   <figure><img src="/files/LKWmcbFVIbF7LBp0gY1r" alt=""><figcaption></figcaption></figure>

2. In the dialog, the **Title of view** will be used as the tab name in the Jira issue panel. You can configure multiple tabs, allowing you to display different queries within the same Jira issue.<br>

   <div align="left"><figure><img src="/files/XtEkPVNUmfWb0ou446aK" alt="" width="375"><figcaption><p>Edit dialog for HubSpot search view</p></figcaption></figure></div>

3. In the search body section, you can enter the parameters you want to search with:
   1. **Search body with no variables**\
      Search body with fixed values.\
      Exampl&#x65;*:*&#x20;

      ```
      {
          "filterGroups": [
              {
                  "filters": [
                      {
                          "propertyName": "firstname",
                          "operator": "EQ",
                          "value": "Brian"
                      }
                  ]
              }
          ]
      }
      ```
   2. **Search body with issue variables**\
      You can reference values from the Jira issue (e.g., reporter's email) to make the search dynamic.\
      Example:

      ```
      {
          "filterGroups": [
              {
                  "filters": [
                      {
                          "propertyName": "email",
                          "operator": "EQ",
                          "value": "{{issue.reporter.emailAddress}}"
                      }
                  ]
              }
          ]
      }
      ```

      With this, the query will automatically run using the issue reporter’s email.
   3. **Search body with query variables**\
      These search bodies require the user to input values directly in the Jira issue. Once entered, the values are saved and will be used automatically the next time the tab is loaded.\
      Example:

      ```
      {
          "filterGroups": [
              {
                  "filters": [
                      {
                          "propertyName": "email",
                          "operator": "EQ",
                          "value": "{{EmailAddress}}"
                      }
                  ]
              }
          ]
      }
      ```

      You can then provide the variable value within the Jira issue.<br>

      <div align="left"><figure><img src="/files/XhlSEPTLUrg9RGkEuViE" alt="" width="563"><figcaption><p>HubSpot search view in JIRA issue</p></figcaption></figure></div>

4. You can also specify which user groups are allowed to access the tab (optional).

5. Click **Preview** to verify that the query runs successfully. Once everything looks correct, click **Save**.

\
**Additional Resources**

If you need further assistance, don’t hesitate to contact our support team at **<support@upsmith.app>**. We’re always happy to help!


# Mirror Fields

Coming soon


# User Guide


# Getting Started

This page outlines the steps to access External Data Objects and External Data Query within a Jira issue.\
\
Step by step guideline:

1. Open the Jira issue where you want to view external data.
2. In the issue panel, locate and click on **External Data Objects** or **External Data Query**.<br>

   <figure><img src="/files/orNYDnsOuC5uTn0twekW" alt=""><figcaption></figcaption></figure>

### **External Data Objects**

External Data Objects allow you to link external data entities to Jira issues. You can navigate between different tabs to access different objects. For example, you can link a Jira issue to Salesforce Cases, Accounts, Contacts, HubSpot Deals, Tickets, and more.

#### **What You Can Do with External Data Objects**

* **Search & Link External Records**\
  Search for Salesforce records or HubSpot objects and link them to your Jira issue. For example:
  * Salesforce Cases, Accounts, Contacts, Deals, Tickets
  * HubSpot Contacts
* **View Fields Data**\
  Each tab displays a table of your configured fields, letting you quickly view and verify external data pulled into Jira. Navigate across tabs to see data from different external objects.
* **Mirror Fields (Coming soon)**\
  Key field values from external record can be synced into Jira fields, making them usable in JQL searches and reports.
* **Access Control & Permissions**\
  Each tab includes its own access control and permission settings, ensuring users only see the external data they are authorized to access.
* **Supports multiple integrations**\
  Works with Salesforce, HubSpot, and more in the future.

<figure><img src="/files/I7LwktOXlGerehYAuxPJ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/iHDOr4VwL7YeFeeECJP3" alt=""><figcaption></figcaption></figure>

### **External Data Query**

External Data Query allows you to run real time queries against external systems (such as Salesforce, HubSpot and other integrations) directly inside Jira issue. It gives you flexible, dynamic control over the exact data you want to retrieve and display on an issue.

#### **What External Data Query Can Do**

* **Run real time queries**\
  Pull fresh data on-demand from your external system whenever you open or refresh the panel.
* **Use Issue Variables**\
  Insert values from the Jira issue, such as reporter email, project key, or custom fields into your query to automatically filter external records.
* **Use Query Variables**\
  Create your own input variables to allow users to interact with and refine the query directly from the Jira issue.
* **Display results in a structured table**\
  Retrieved data is shown in a clean table layout, organized into configurable columns.
* **Support multiple query tabs**\
  Add as many query tabs as you need, each with its own query, fields, and permissions.
* **Supports multiple integrations**\
  Works with Salesforce, HubSpot, and more in the future.
* **Secure and permission aware**\
  Access control ensures users only see the data they are authorized to view.

<figure><img src="/files/9Gp6Dhv42qj5NcSFVSEC" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/sP0l4pclcYvz2UMYU4EP" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/CGS6PcDmcfHq04QHeOLu" alt=""><figcaption></figcaption></figure>

**Additional Resources**

If you need further assistance, don’t hesitate to contact our support team at **<support@upsmith.app>**. We’re always happy to help!


# Mirror Fields

Coming soon


# Security Statement

## Overview <a href="#securitystatement-overview" id="securitystatement-overview"></a>

This Security Statement explains how our data is stored and what informations are collected from you.

## Data and Access <a href="#securitystatement-data" id="securitystatement-data"></a>

* App is built and hosted on Atlassian Forge, levaraging Atlassian's cloud infrastructure for reliability and data protection.
* We use AWS to host our backend apps, which are only used for OAuth authorization. All other functionalities runs entirely on Atlassian Forge. Daily backups are performed every 24 hours.
* We do not track any private/sensitive information.
* We never store any connected integrations data on our servers or database. The only thing we store is OAuth details. Data may be cached in memory for optimisation purposes, but it will expire once time to live reaches zero.
* Application relies HTTPS and JWT on Atlassian Forge as a validation.

## Billing, Licensing and Privacy Policy

We rely on Atlassian for billing and licensing. Therefor, any personal information is collected and processed by Atlassian, governed by the Atlassian Marketplace Terms of Use and the Atlassian Privacy Policy.&#x20;

We collect information to provide better services to our customers. The types of personal information or personal data we may collect about you include:

* your name;
* your contact details, including email address, mailing address and/or telephone number;&#x20;
* your demographic information, such as postcode;
* your preferences and/or opinions;
* details of the services we have provided to you and/or that you have enquired about, and our response to you;
* your browser session and geo-location data, device and network information, statistics on page views and sessions, acquisition sources, search queries and/or browsing behavior;
* information about your access and use of our services, including through the use of Internet cookies, your communications with our services, the type of browser you are using, the type of operating system you are using and the domain name of your Internet service provider;
* additional personal information that you provide to us, directly or indirectly, through your use of our services, associated applications, associated social media platforms and/or accounts from which you permit us to collect information; and
* any other personal information requested by us and/or provided by you or a third party.

## Customer Support

When you contact us for support, we will do our best to respond within 24 business hours from the time of your request. As we are a small company, we appreciate your patience.

## Contact

If you have any questions, please do not hesitate to contact us at **<support@upsmith.app>**


# Terms of Service

**This End-User License Agreement (EULA)** is a binding legal agreement between **UpSmith**(the «**Licensor**»), a provider of cloud-based and downloadable applications including related documentation and services (the «**Software**») through the Atlassian Marketplace or any other means that interoperate with applicable products and services by Atlassian Pty Ltd («**Atlassian**»), and you (either an individual or a single legal entity, the «**Licensee**») whose details are provided to the Licensor when you order or receive the Software from the Licensor or a Reseller (the «**Purchase**»).

The Licensee agrees to be bound by the terms of this EULA by copying, downloading, installing, licensing, purchasing or otherwise using the Software. If the Licensee does not agree to the terms of this EULA, the Licensee may not copy, download, install or otherwise use the Software.

This EULA is a supplement to the Atlassian Marketplace Terms of Use (the «**Marketplace Terms of Use**»). In case of a conflict between this EULA and the Marketplace Terms of Use, this EULA shall prevail.  &#x20;

## Grant of License

1.1 The Software is licensed, not sold, and no ownership right is conveyed to the Licensee, irrespective of the use of terms in this EULA.

1.2 This EULA grants the Licensee the rights according to the Licensee’s order through the Atlassian Marketplace or a Reseller and the respective specifications including, but not limited to, for example the license, a maintenance or subscription period, the price, support and other services, and the number of authorized users (the «**Order**»).

1.3 The Licensor grants the Licensee a non-exclusive, non-sublicensable, non-transferable and worldwide license to use the Software limited to the scope of the Order. The Licensor reserves all rights not expressly granted to the Licensee in this EULA.

1.4 The rights under this EULA are non-exclusive, non-sublicensable and non-transferable. The Licensee may not convey, sell or transfer the Software to any third party without the Licensor’s prior express written consent.

1.5 The Licensee may not decompile, disassemble, modify or reverse engineer the Software in whole or in part, or create any derivative works from the Software without the Licensor’s prior express written consent.

1.6 The Licensee is allowed to make necessary backup copies for the purpose of backup only and for no other purpose.

1.7 The Licensee is allowed to install the Software and make the Software available for use on systems controlled, leased or owned by the Licensee or a third-party provider as long as the Licensee remains fully responsible for any compliance with this EULA.

1.8 The Software will, if not otherwise agreed or offered, delivered only in electronic form.

## 2. Third-Party Software

2.1 The Licensee acknowledges that the Software may contain software licensed by the Licensor from third parties, including open source software, and embedded in the Software, and that in addition to this EULA, additional obligations may apply in relation to any use of such third-party software by the Licensee. The Licensor shall not be liable for any third-party software.

2.2 The Software may depend on, require and use various third-party Application Programming Interface (APIs). The Licensor shall not be liable for any third-party APIs.

## 3. Payment Terms, Modifications and Termination

3.1 The Licensor may ask for upfront payments as a condition to grant any license to the Licensee. Any license shall only be granted to the Licensee if the Licensor has received full payment for the respective license.

3.2 The Licensor may modify this EULA at any time and at its sole discretion. If a modification is detrimental to the Licensee, the Licensor shall use reasonable efforts to notify any affected Licensee by sending e-mails to known e-mail addresses or by publishing a notification on the Licensor’s website or on the Atlassian Marketplace. Continued use of the Software after such a notification by the Licensee is considered as an agreement with the modified EULA.

3.3 The Licensor may terminate any license if the Licensor is in default with payments or if the Licensor cannot reasonably expect the Licensee to make due payments.

3.4 The license shall terminate automatically if the Licensor fails to comply with this EULA.

## 4. Limitation of Liability and Warranty

4.1 The Licensor will use reasonable efforts to provide solutions for any reported issues. The Licensor will provide maintenance and support services, unless such services cannot be reasonably expected, for the Software on the Licensee’s request within the scope of the Order.

4.2 The Software is provided on an «as is» and «as available» basis without warranty, express or implied, of any kind of nature, including, but not limited to, any warranties of fitness for a specific purpose, or performance.

4.3 The Licensor shall not be liable to the Licensee or any other person for any consequential, direct, incidental, indirect or special damages of any kind due and in relation to the Software.

## 5. Miscellaneous

5.1 The Licensee grants the Licensor the right to use the Licensee’s company name / name and logo and any review provided or published in relation to the Software within promotional material, on the Licensor’s social media channels and on the Licensor’s website. The Licensee can revoke this right for future usage any time by submitting a respective request to the Licensor.

5.2 If any provision of this EULA should be held to be unenforceable for any reason, such provision shall be amended only to the extent necessary to make it enforceable and the remaining provisions of this EULA shall remain in full force and effect.

## 6. Choice of Law and Venue

6.1 This EULA shall be governed exclusively by Malaysian law excluding its conflict of laws rules and the United Nations Convention on Contracts for the International Sale of Goods (CISG).

6.2 The exclusive venue for both parties shall be the registered office of the Licensor.


# Notion Embedder

<details>

<summary>Supported Notion block types</summary>

* **Page Elements**: Page, Text, Heading 1/2/3, Quote, Callout, Toggle
* **Lists**: Bookmark, Bulleted List, Numbered List, Todos (checkboxes)
* **Content**: Table of Contents, Divider, Column, Column List
* **Media**: Image, Video, Audio, Embed, PDF, File, Link, Page Link, External Page Link
* **Integrations**: Figma, Google Maps, Google Drive, Tweet
* **Special Elements**: Equation (block and inline), Code (block and inline), Collections (table, gallery, board, list)

</details>

## Getting Started

Embed Notion page in:

{% tabs %}
{% tab title="Item View" %}

1. **Get public URL from Notion**\
   Click "Share", publish the page and copy the URL

   <figure><img src="https://dd364-service-23420343-da20e93d.us.monday.app/step1.gif" alt=""><figcaption></figcaption></figure>

2. **Create a new Link column for Notion (optional)**

   <figure><img src="https://dd364-service-23420343-da20e93d.us.monday.app/step2.gif" alt=""><figcaption></figcaption></figure>

3. **Paste Notion public URL**

   <figure><img src="https://dd364-service-23420343-da20e93d.us.monday.app/step3.gif" alt=""><figcaption></figcaption></figure>

4. **Select column in Settings**

   <figure><img src="https://dd364-service-23420343-da20e93d.us.monday.app/step4.gif" alt=""><figcaption></figcaption></figure>

{% endtab %}

{% tab title="Board View" %}

1. **Get public URL from Notion**\
   Click "Share", publish the page and copy the URL

   <figure><img src="https://dd364-service-23420343-da20e93d.us.monday.app/step1.gif" alt=""><figcaption></figcaption></figure>

2. **Paste Notion public URL in Settings**

   <figure><img src="https://dd364-service-23420343-da20e93d.us.monday.app/board-step2.gif" alt=""><figcaption></figcaption></figure>

{% endtab %}

{% tab title="Dashboard Widget" %}

1. **Get public URL from Notion**\
   Click "Share", publish the page and copy the URL

   <figure><img src="https://dd364-service-23420343-da20e93d.us.monday.app/step1.gif" alt=""><figcaption></figcaption></figure>

2. **Paste Notion public URL in Settings**

   <figure><img src="https://dd364-service-23420343-da20e93d.us.monday.app/board-step2.gif" alt=""><figcaption></figcaption></figure>

{% endtab %}

{% tab title="Workspace View" %}

1. **Get public URL from Notion**\
   Click "Share", publish the page and copy the URL

   <figure><img src="https://dd364-service-23420343-da20e93d.us.monday.app/step1.gif" alt=""><figcaption></figcaption></figure>

2. Paste URL in the text field&#x20;

   <div align="left"><figure><img src="/files/kKGv1G447Kh2KpWV87e2" alt="" width="468"><figcaption></figcaption></figure></div>

{% endtab %}
{% endtabs %}

Still facing issues? [Contact us](mailto:support@upsmith.app)


# Security Statement

## Overview <a href="#securitystatement-overview" id="securitystatement-overview"></a>

This Security Statement explains how our data is stored and what informations are collected from you.

## Data and Access <a href="#securitystatement-data" id="securitystatement-data"></a>

* We use AWS to host our cloud apps. Daily backups are performed every 24 hours.
* We do not track any private/sensitive information.
* We never store any connected integrations data on our servers or database. The only thing we store is OAuth details. Data may be cached in memory for optimisation purposes, but it will expire once time to live reaches zero.
* Application uses HTTPS and JWT as a validation.

## Billing, Licensing and Privacy Policy

We rely on Atlassian for billing and licensing. Therefor, any personal information is collected and processed by Atlassian, governed by the Atlassian Marketplace Terms of Use and the Atlassian Privacy Policy.&#x20;

We collect information to provide better services to our customers. The types of personal information or personal data we may collect about you include:

* your name;
* your contact details, including email address, mailing address and/or telephone number;&#x20;
* your demographic information, such as postcode;
* your preferences and/or opinions;
* details of the services we have provided to you and/or that you have enquired about, and our response to you;
* your browser session and geo-location data, device and network information, statistics on page views and sessions, acquisition sources, search queries and/or browsing behavior;
* information about your access and use of our services, including through the use of Internet cookies, your communications with our services, the type of browser you are using, the type of operating system you are using and the domain name of your Internet service provider;
* additional personal information that you provide to us, directly or indirectly, through your use of our services, associated applications, associated social media platforms and/or accounts from which you permit us to collect information; and
* any other personal information requested by us and/or provided by you or a third party.

## Customer Support

When you contact us for support, we will do our best to respond within 24 business hours from the time of your request. As we are a small company, we appreciate your patience.

## Contact

If you have any questions, please do not hesitate to contact us at **<support@upsmith.app>**


# Service Level Agreement

The level of service you can expect from us

## Response Times

When you request support for UpSmith product, our commitment is to provide a response within three business days from the time you submit your request. In cases where UpSmith or Atlassian identifies a support request as critical, we will respond within 24 hours. We will do our best to get back to you sooner.

## Business Hours

Our business hours are Monday through Friday from [9AM to 6PM Singapore Time (GMT/UTC +8)](https://www.timeanddate.com/worldclock/singapore). We are closed on [major holidays in Singapore](https://www.mom.gov.sg/employment-practices/public-holidays). To see our business hours in your timezone, check [timeanddate.com](https://www.timeanddate.com/worldclock/converter.html?iso=20231117T140000\&p1=tz_sgt).

## Support

Please contact us at <support@upsmith.app>

### What we can help you with

* Help with installation
* Help troubleshooting problems with UpSmith apps
* Help to identify workarounds

### What's not included in our support

* Product Training
* Customers who do not have a valid and current license or active subscription
* Support related to non-UpSmith apps
* Support for Confluence/Jira issues
* Support for Confluence/Jira versions that are no longer supported by Atlassian or UpSmith.


# End User License Agreement (EULA)

**This End-User License Agreement (EULA)** is a binding legal agreement between **UpSmith**(the «**Licensor**»), a provider of cloud-based and downloadable applications including related documentation and services (the «**Software**») through the Atlassian Marketplace or any other means that interoperate with applicable products and services by Atlassian Pty Ltd («**Atlassian**»), and you (either an individual or a single legal entity, the «**Licensee**») whose details are provided to the Licensor when you order or receive the Software from the Licensor or a Reseller (the «**Purchase**»).

The Licensee agrees to be bound by the terms of this EULA by copying, downloading, installing, licensing, purchasing or otherwise using the Software. If the Licensee does not agree to the terms of this EULA, the Licensee may not copy, download, install or otherwise use the Software.

This EULA is a supplement to the Atlassian Marketplace Terms of Use (the «**Marketplace Terms of Use**»). In case of a conflict between this EULA and the Marketplace Terms of Use, this EULA shall prevail.  &#x20;

## Grant of License

1.1 The Software is licensed, not sold, and no ownership right is conveyed to the Licensee, irrespective of the use of terms in this EULA.

1.2 This EULA grants the Licensee the rights according to the Licensee’s order through the Atlassian Marketplace or a Reseller and the respective specifications including, but not limited to, for example the license, a maintenance or subscription period, the price, support and other services, and the number of authorized users (the «**Order**»).

1.3 The Licensor grants the Licensee a non-exclusive, non-sublicensable, non-transferable and worldwide license to use the Software limited to the scope of the Order. The Licensor reserves all rights not expressly granted to the Licensee in this EULA.

1.4 The rights under this EULA are non-exclusive, non-sublicensable and non-transferable. The Licensee may not convey, sell or transfer the Software to any third party without the Licensor’s prior express written consent.

1.5 The Licensee may not decompile, disassemble, modify or reverse engineer the Software in whole or in part, or create any derivative works from the Software without the Licensor’s prior express written consent.

1.6 The Licensee is allowed to make necessary backup copies for the purpose of backup only and for no other purpose.

1.7 The Licensee is allowed to install the Software and make the Software available for use on systems controlled, leased or owned by the Licensee or a third-party provider as long as the Licensee remains fully responsible for any compliance with this EULA.

1.8 The Software will, if not otherwise agreed or offered, delivered only in electronic form.

## 2. Third-Party Software

2.1 The Licensee acknowledges that the Software may contain software licensed by the Licensor from third parties, including open source software, and embedded in the Software, and that in addition to this EULA, additional obligations may apply in relation to any use of such third-party software by the Licensee. The Licensor shall not be liable for any third-party software.

2.2 The Software may depend on, require and use various third-party Application Programming Interface (APIs). The Licensor shall not be liable for any third-party APIs.

## 3. Payment Terms, Modifications and Termination

3.1 The Licensor may ask for upfront payments as a condition to grant any license to the Licensee. Any license shall only be granted to the Licensee if the Licensor has received full payment for the respective license.

3.2 The Licensor may modify this EULA at any time and at its sole discretion. If a modification is detrimental to the Licensee, the Licensor shall use reasonable efforts to notify any affected Licensee by sending e-mails to known e-mail addresses or by publishing a notification on the Licensor’s website or on the Atlassian Marketplace. Continued use of the Software after such a notification by the Licensee is considered as an agreement with the modified EULA.

3.3 The Licensor may terminate any license if the Licensor is in default with payments or if the Licensor cannot reasonably expect the Licensee to make due payments.

3.4 The license shall terminate automatically if the Licensor fails to comply with this EULA.

## 4. Limitation of Liability and Warranty

4.1 The Licensor will use reasonable efforts to provide solutions for any reported issues. The Licensor will provide maintenance and support services, unless such services cannot be reasonably expected, for the Software on the Licensee’s request within the scope of the Order.

4.2 The Software is provided on an «as is» and «as available» basis without warranty, express or implied, of any kind of nature, including, but not limited to, any warranties of fitness for a specific purpose, or performance.

4.3 The Licensor shall not be liable to the Licensee or any other person for any consequential, direct, incidental, indirect or special damages of any kind due and in relation to the Software.

## 5. Miscellaneous

5.1 The Licensee grants the Licensor the right to use the Licensee’s company name / name and logo and any review provided or published in relation to the Software within promotional material, on the Licensor’s social media channels and on the Licensor’s website. The Licensee can revoke this right for future usage any time by submitting a respective request to the Licensor.

5.2 If any provision of this EULA should be held to be unenforceable for any reason, such provision shall be amended only to the extent necessary to make it enforceable and the remaining provisions of this EULA shall remain in full force and effect.

## 6. Choice of Law and Venue

6.1 This EULA shall be governed exclusively by Malaysian law excluding its conflict of laws rules and the United Nations Convention on Contracts for the International Sale of Goods (CISG).

6.2 The exclusive venue for both parties shall be the registered office of the Licensor.