---
title: "Platform Import & Export"
slug: "configuring-platform-import-export"
updated: 2025-03-26T12:41:12Z
published: 2025-03-26T12:41:12Z
canonical: "docs.agilenow.io/configuring-platform-import-export"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agilenow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform Import & Export

The **Import & Export** functionality in **Agile.Now** allows administrators to **transfer, synchronize, and maintain system configurations** across different environments. This feature ensures **consistent configurations, efficient organization, and optimized access control** within the **Workspace application**.

The Import & Export process helps:

- **Move configurations** between development, testing, and production environments.
- **Create backups** of system settings.
- **Replicate settings** for faster deployment.

However, **use this feature with caution** as importing configurations can override **applications, modules, and roles**, potentially granting customers access beyond their **subscription limits**.

## **Access Rights Information**

To use the Import & Export functionality, you need the **`Configuration Sync`** role with read and update permissions.

- **Ensure you have the `Configuration Sync` role with create and update permissions.**
- **Use caution when granting this functionality to customers, as incorrect imports may override configurations.**

## **Configuring Import & Export Settings**

Follow these steps to configure **Import & Export** in Agile.Now.

### **1. Access the Platform Import & Export Settings**

- Navigate to **Settings** → **Configuration**.
- Locate the **Import & Export Configuration** section.  

![Platform import and export](https://cdn.document360.io/06417a5c-658f-4a8a-ad57-27f6e06c9e0d/Images/Documentation/Platform%20import%20and%20export.PNG)

### **2. Exporting Platform Configurations**

The **Export** function allows you to create a **backup of system settings** or transfer configurations between environments.

#### **Steps to Export:**

1. Click **Export** button.
2. System generate the **export file**.
3. Download the **secure export package**.

#### **What is Included in the Export?**

- Applications & Modules
- Roles & Access Rights
- Workspace Application Settings

> **Note:** The export file is **security-protected** and **cannot be manually modified**.

---

## **3. Importing Platform Configurations**

The **Import** function applies pre-configured settings from an **export file** into the target environment.

#### **Steps to Import:**

1. Click **Import Configuration**.
2. Upload a **valid, unmodified** export file.
3. Confirm the import process.
4. Agile.Now will **validate the file's fingerprint** for authenticity.
5. If valid, configurations are applied automatically.

### **Security Restrictions for Importing**

The **Import File** has strict **security features** to prevent unauthorized changes: ✅ **Manual modifications are prohibited** – If altered, the **fingerprint changes**, and the import will fail. ✅ **Cannot modify own applications** – You can only **add applications to child tenants**. ✅ **Cannot change access rights** – Ensures security and prevents privilege escalation.

---

## **4. Best Practices for Using Import & Export**

### ✅ **Use Import & Export Wisely**

- Do **not** grant Import access to customers without careful consideration.
- Improper imports can **override applications, modules, and access rights**.
- Customers **may gain more access** than their **subscription allows**.

### ✅ **Secure Your Export Files**

- Store exported configurations in a **safe location**.
- Use the export feature **only when necessary** to prevent unauthorized access.

### ✅ **Ideal for Environment Synchronization**

- Move configurations from **development/testing to production**.
- Avoid manual reconfiguration by using a secure **import process**.

---

## **5. Tenant-Specific Import & Export**

When a **new tenant is created**, they **automatically inherit** the global import/export settings.

- If you grant tenants access to **`Configuration Sync`**, they can **import configurations into their own workspaces**.
- However, they **cannot modify access rights or system applications**.

---

## **6. Troubleshooting Import & Export Issues**

If you encounter issues with Import & Export, review the following table:

| **Issue** | **Possible Cause** | **Solution** |
| --- | --- | --- |
| Import fails with a fingerprint error. | The file was manually modified. | Use an **untouched** exported file. |
| Import does not apply settings. | Incorrect configuration scope selected. | Verify the **imported settings**. |
| Customer gained unexpected access. | Imported configuration **overrides permissions**. | Ensure the **import file matches subscription limits**. |
| Unable to modify access rights. | Security restrictions prevent access changes. | **Directly modify roles** in the system. |

For additional assistance, refer to [Agile.Now Documentation](https://docs.agilenow.io).

---

## **Conclusion**

The **Import & Export** feature in Agile.Now simplifies **system configuration transfers**, reducing manual effort and ensuring **consistent platform settings**. However, **use this functionality carefully**, as incorrect imports may **override applications, modules, and access permissions**.

Would you like additional **examples of environment migration workflows** or **best practices for multi-tenant synchronization** included in this article?