AvePoint Docs
Contact support
Contact support
English

Home > Configure Administration Settings > Settings in AvePoint Cloud Index

Export to PDF

Settings in AvePoint Cloud Index

The application administrator must configure the sections below to complete the settings.

Configure Gateway Settings in AvePoint Cloud Index

Follow the steps below to configure the Gateway Settings to enable AvePoint Cloud Index to connect with your file systems or Azure File Storage.

If this is the first time you are accessing AvePoint Cloud Index, or you have not configured the gateway settings before, you will be brought to the Gateway Settings page directly. Otherwise, click the Settings (gear) button on the upper-right corner of the page and select Gateway Settings from the drop-down list to access the Gateway Settings page.

  1. In the Gateway Service Settings section, configure the gateway service information.

    • Gateway Service URL – Enter the URL of the Gateway Service that you have configured in the AvePoint Cloud Index Gateway Admin.

    • Passphrase – Enter the passphrase that you have configured for the gateway service in the AvePoint Cloud Index Gateway Admin.

  2. In the Domain Connections section, connect the domains of AvePoint Online Services tenants with the domain of SharePoint Online sites.

    *Note: This feature is only available if you have configured the Microsoft 365 (All permissions) app profile in AvePoint Online Services > App management.

    1. Click Load Existing Domains, all domains retrieved from the App profiles will be listed.

      *Note: If your SharePoint domain name has been changed, the updated domain name will be retrieved after you click Load Existing Domains.

    2. Select the checkboxes of the corresponding domains and click Add.

    3. Each selected domain will be added as a domain connection and displayed in the Domain Connections table. You can click Delete (The Delete icon.) in the Action column to delete the domain connection.

  3. Click Save to save your settings and exit the current page, or click Cancel to discard your settings without saving any changes.

Configure General Settings

Follow the steps below to configure the general settings.

  1. Click the Settings (gear) button on the upper-right corner of the page and select General Settings from the drop-down list to access the General Settings page.

  2. On the General Settings page, you can configure the domain mappings, user mappings, column settings, manage the App Part settings, permission management, and upload/download settings.

    • Domain Mapping – Manage the domain mappings, which map the domain for SharePoint Online to the domain of the local file system. Click Domain Mapping on the left pane.

      • Add Domain Mapping – Click Add Domain Mapping to create a domain mapping. Refer to Add Domain Mapping for details.

      • Edit a Domain Mapping – Click the Edit (pencil) button in the Action column to edit a certain domain mapping.

      • Delete a Domain Mapping – Click the Delete (bin) button in the Action column to delete a certain domain mapping.

    • User Mapping – Manage the user mappings, which map SharePoint Online users to your local AD users. Click User Mapping on the left pane.

      • Add User Mapping – Click Add User Mapping to create a user mapping. Refer to Add User Mapping for details.

      • Edit a User Mapping – Click the Edit (pencil) button in the Action column to edit a certain user mapping.

      • Delete a User Mapping – Click the Delete (bin) button in the Action column to delete a certain user mapping.

    • Column Settings – Choose the columns that you would like to show with the files in SharePoint Online.

      Click Column Settings on the left pane, select the checkboxes of the columns that you want to show, select a number from the drop-down list next to the checkbox to adjust the display order of the columns, and click Save to save your settings, or click Cancel to discard your settings without saving any changes.

    • App Part Management – Manage the app part settings. Click the Delete (cross mark) button in the Action column to delete the app part settings, or select one or more app parts by selecting the checkboxes and click the Delete button to remove the app part settings for selected app parts. This deletion will only remove the app part settings of the selected app parts and will not remove the app parts.

    • Permission Management – This feature only works for AvePoint Cloud Index App on the SharePoint site. AvePoint Cloud Index provides the ability to trim permissions from the SharePoint site where the Cloud Index App Part resides. By selecting this option, Cloud Index will follow the SharePoint site permission to perform the Cloud Index App Part security trimming, and then users who have permissions to the SharePoint site can access the files and folders in the app part regardless of their permissions to the connected file system.

      The following table shows the back-end permission mappings between SharePoint Online and Cloud Index when enabling this feature.

Permissions in SharePoint OnlinePermissions in Cloud Index
Add ItemsUpload, New Folder
Edit ItemsEdit
Delete ItemsDelete
View ItemsView, Download
The default security trimming logic, which means turning off this feature, is as follows: users’ ability to perform actions in the Cloud Index app part is based on their permissions in the file system. - **Upload/Download Settings** – Choose whether to allow users to upload files from their OneDrives or download files to their OneDrives. - **Allow users to upload files from their** **OneDrives** – With this enabled, end users can upload files from their own OneDrives to Cloud Index app (SharePoint Online), Cloud Index app part (SharePoint Online), and Cloud Index app (Microsoft Teams). - **Download files to users’ own** **OneDrives** – With this enabled, the Download feature will be unavailable when users access Cloud Index from AvePoint Online Services. In the Cloud Index app (SharePoint Online), Cloud Index app part (SharePoint Online), and Cloud Index app (Microsoft Teams), users can download files to their own OneDrives (root folder).

Add Domain Mapping

Follow the steps below to add a domain mapping.

  1. On the Add Domain Mapping page, configure the basic settings first.

    • Name – Enter a name in the text box as the mapping name.

    • Description – Enter an optional description for the mapping.

  2. Add the mapping rules for the domain mapping. A domain mapping can consist of multiple mapping rules.

    1. Enter the domain name of the SharePoint Online sites environment in the Source Domain Name text box.

    2. Enter the domain name of the local file system environment in the Destination Domain Name text box.

    3. Click Add to add this mapping rule. Once added, it will be displayed in the table below. In the table, you can delete a certain mapping rule by clicking the Delete (bin) button in the Action column.

    4. Repeat the steps from a to b to add more mapping rules.

  3. Click Save to save your settings, or click Cancel to discard your settings without saving any changes.

Add User Mapping

Follow the steps below to add a user mapping.

  1. In the General Settings pane, click User Mapping.

  2. Configure the following basic settings.

    • Name – Enter a name in the text box as the mapping name.

    • Description – Enter an optional description for the mapping.

  3. Choose one of the following methods to add mapping rules.

    • To add mapping rules in batch, click download a template, add mapping rules in the downloaded template, and click Upload Configured Mapping List to upload the configured template.

    • To manually add mapping rules, follow the steps below:

      1. In the Source Username textbox, enter the username of a SharePoint Online user.

      2. In the Destination Username textbox, enter the username of a local AD user.

      3. Click Add to add this mapping rule. Once added, it will be displayed in the table below. In the table, you can delete a certain mapping rule by clicking the Delete (bin) button in the Action column.

      4. Repeat the steps above to add more mapping rules.

  4. Click Save to save your settings, or click Cancel to discard your settings without saving any changes.

Manage Connections

Manage connections between AvePoint Cloud Index gateway service and your file systems or Azure File Storage.

Click the Settings (gear) button on the upper-right corner of the page and select Connections from the drop-down list to access the Connections page.

- If you have not configured any connections before, click **Add** **Connection** to add a connection. Refer to [Add a Connection](../index.md#add-a-connection) for details. - If there are existing connections on the Connections page, you can perform the following actions: - Add a Connection – Click **Add Connection** to create a new connection. Refer to [Add a Connection](../index.md#add-a-connection) for details. - Edit a Connection – Click the connection name link to access the Edit a Connection page, or click the More actions (vertical ellipsis) button of a connection to select **Edit** to access the Edit a Connection page. - Delete a Connection – Click the More actions (vertical ellipsis) button of a connection to select **Delete** to remove a connection.

Add a Connection

Follow the steps below to add a connection.

  1. On the Add Connection page, configure the basic settings in the Basic Settings section.

    • Name – Enter a name in the text box as the connection name.

    • Description – Enter an optional description for the connection.

  2. In the Connection Source Settings section, configure the data source information for accessing the source data.

    • Storage Type – Select the storage type (File System or Azure File Storage) from the drop-down list.

    • Access Options (for Azure File Storage only) – Choose an access option from the following:

      • Use Active Directory Domain Services or Microsoft Entra Domain Services to manage access

      • Manage access based on Azure role-based access control (Azure RBAC)

        *Note: If you want to choose this option, you must create an app profile for Custom Azure app in AvePoint Online Services first. For details about creating an app profile for a custom Azure app, refer to Integration with AvePoint Online Services.

    • For the Azure File Storage type, if you choose the Manage access based on Azure role-based access control (Azure RBAC) option, you need to configure the following information:

      • Subscription – Select a subscription from the drop-down list.

      • Resource Group – Select a resource group from the drop-down list.

      • Storage Account – Select a storage account from the drop-down list.

      • File Share Name – Enter a file share name in the field.

      • Path – Enter the UNC path in the text box to specify the location where the documents will be displayed. The path can be any path in the same local area network where AvePoint Cloud Index Gateway Admin belongs.

        A hidden folder named .apci will be created in this path to store the temp files when you upload a file or download multiple files.

      • Username – Enter the name of the user that has Full Control permission to the specified path. The username format is domain\username or username@domain.com.

      • Password – Enter the corresponding password.

  3. In the General Settings section, choose a domain mapping from the drop-down list to map the domain of the SharePoint Online site to the domain of the UNC path. You can click New Domain Mapping from the drop-down list to create a new domain mapping and refer to Add Domain Mapping for details on how to create a domain mapping.

  4. In the Advanced Settings section, choose whether or not to limit access to this connection.

    • Public – There are no limits to access this connection. Anyone who has at least Read permission to the SharePoint Online sites that have the AvePoint Cloud Index app added can view the connection.

    • Private – Only the specified users can view this connection. Enter the names of the Microsoft Entra ID users and groups who can view the connection. You can click Check Name to verify the username.

      *Note: This option is only available if you have configured the Microsoft Entra ID app profile in the AvePoint Online Services > App management.

  5. Click Save to save your settings, or click Cancel to discard your settings without saving any changes.

Manage Audit Report

Audit Report can track how content is being used in your connections, such as document views, file uploads, renamed files, content edits or deletions, or folder creation. Knowing who is taking what action on which content in your connections can be critical in helping your organization fulfill its requirements.

Click the Settings (gear) button on the upper-right corner of the page and select Audit Report from the drop-down list to access the Audit Report page.

You can perform the following actions to achieve the audit report:

- **Modify Retention Rule** – The retention rule indicates how long the audit data will be kept. Click the **Modify Retention Rule** link, select a number from the **Keep the audit data for** **X months** drop-down list as the retention duration, and click **Save**. The retention period starts from the action time. - **View Audit Report** – The audit data for the selected connection will be displayed in the audit report table. You can click the drop-down list next to **View the audit report of** to select the desired connection. The following table lists the properties of the audit data.
Column NameDescription
User IDThe user account that performs the action.
ActionThe action that has been taken by the user.
PathThe path of file/folder that has been taken action.
Action TimeThe time when the action has been taken.
IPThe IP address of the user.
The following actions in your connection will be tracked in Audit Report.
ActionObject
ViewFile
EditFile
UploadFile
DownloadFile
RenameFile
DeleteFile, Folder
Create FolderFolder
- **Export Audit Report** – You can export the audit report to a local drive for further use. Click **Export Audit Report**, and the **Export Audit Report** page appears. 1. Select a number from the **Export the audit data for the last X months** drop-down list. 2. Select the checkboxes of the connections whose audit data you want to export. 3. Click **Export**. The audit report will be exported in.csv format.

Configure Deployment Manager

Deployment Manager provides you the ability to add the AvePoint Cloud Index App Part to multiple site pages and specify the connection for each App Part in batch.

*Note: Before deploying App parts in SharePoint sites, ensure your AvePoint Online Services tenant has an available app profile for Microsoft 365, and the SharePoint Online permissions have been granted to the app profile.

Click the Settings (gear) button on the upper-right corner of the page and select Deployment Manager from the drop-down list to access the App Part Batch Deployment page.

Follow the steps below to configure the settings for the batch deployment.

  1. In the Deployment Settings section, configure the settings for the batch deployment of AvePoint Cloud Index App Part. You should download the template of the configuration file where you can configure the site pages to add AvePoint Cloud Index App Part, set the connection for each path, and even specify the relative path if necessary.

    • Download Template – Click Download Template to download the configuration file template to local. The download file is BatchDeploymentTemplate.csv.

      Open the downloaded file and configure the site page information where you want to add AvePoint Cloud Index App Part. There are examples as references about how to add the configuration information. Please remove the examples before you customize your own information.

      • Site URL – Enter the full URL of the site where the page you want to add AvePoint Cloud Index App Part resides in.

      • Page URL – Enter the full URL of the page where you want to add the AvePoint Cloud Index App Part.

      • Name – Enter the name of the app part that you want to configure for the app part on this page.

      • Connection Name – Enter the name of the connection that you want to configure for the app part on this page. The connection must be an existing one.

      • Relative Path (Optional) – Enter a subdirectory name of the connection path. If you want to only display documents in a subset of a connection, you can detail the connection path down to a subfolder under it.

        For example, if the connection path is \10.0.1.1\c$\US Technical Writing and the folder path you want to display in the App part is \10.0.1.1\c$\US Technical Writing\AvePoint Online Services\PDFs, you should enter AvePoint Online Services\PDFs in the text box.

      You can add more entries in the configuration file for the batch deployment. After your configurations, save your changes and close the file.

      *Note: Make sure the SharePoint site collection administrator has permission to all the sites configured in the file.

      *Note: You cannot add multiple AvePoint Cloud Index App Parts to the same page. That means if you happen to add the same site page information more than once in the configuration file, the system will use the first entry for the deployment, and the duplicate entries will be excluded. The excluded duplicate entries will not be calculated into the Deployment Report.

    • Import Configuration File – Click Browse to choose the configuration file in the pop-up window and click OK in the pop-up window to import the file. The configuration filename will be populated in the text box.

  2. Click Deploy to add the AvePoint Cloud Index App Part to the configured site pages with pre-configured connections. After executing the deployment, you can go to the Deployment Report page to view the details.

View Deployment Report

Deployment Report displays the history of deployment jobs that you have executed. Every entry indicates one deployment job that you have performed, and the following table lists the properties for every deployment job.

Column NameDescription
Deployment Job IDThe ID of every deployment job.
Job StatusThe status for every deployment job. There are two values:Completed – The deployment job has been completed regardless of the deployment status of the AvePoint Cloud Index App Part to the site pages.Failed – The deployment job failed, which means no deployment has been done.
Number of Deployed Site PagesThe total number of pages that will add the AvePoint Cloud Index App Part, the number of failed deployments, and the number of successful deployments.
ActionThe actions you can take on the job record.View Details – View the detailed deployment status of every entry you configured in the deployment configuration file.Delete – Delete the deployment history from this view.

On the View Details page of a deployment job, you can view the overview deployment statuses of the entries configured in the deployment configuration file on the top of this page. In the table below, you can view the detailed deployment information for every entry.

Column NameDescription
Page URLThe URL of the page where the AvePoint Cloud Index App Part was added.
Deployment StatusThe deployment status for this entry. There are three statuses:Successful – AvePoint Cloud Index App Part has been added to the site page successfully, and its connection has been configured properly.Partially Successful – AvePoint Cloud Index App Part has been added to the site page successfully, but its connection configuration failed. The detailed reason can be found in the Comments column.Failed – It failed to add AvePoint Cloud Index App Part to the site page. The detailed reason can be found in the Comments column.
CommentsThe detailed reason if there is an issue for the deployment.
ActionThe actions you can take on the deployment record.Delete – Delete the deployment history for this entry.

Perform Background Migrations

Background Migration allows you to migrate data to the SharePoint site where your app part resides during a large migration, and you can access your files in the app part in Microsoft 365.

Background Migration is integrated with Fly Server to perform the migration jobs. Currently, the recommended version of Fly Server to work together with Background Migration is 4.0.0.4077. Before configuring the migration settings, you must install Fly Server to build up the Fly Server environment. Refer to the Fly Server Installation Guide for the details on the installation.

After preparing the Fly Server environment, follow the steps below to configure the migration settings and perform migration jobs.

  1. Enable Integration with Fly Server

  2. Configure Migration Settings

  3. Perform Migration Jobs

Enable Integration with Fly Server

Complete the steps below to connect to the Fly Server Manager.

*Note: This page only appears the first time you enable the integration with Fly Server. After completing the integration settings, this page will not appear.

  1. Click the Settings (gear) button on the upper-right corner of the page and select Background Migration from the drop-down list to access the Migration Settings page.

  2. Enter the URL of Fly Server Manager in the first text box. It is the URL which you use to log into Fly Server Manager.

  3. Enter the Fly Server API Key in the second text box. You can find the Fly Server API Key by accessing Fly Server Manager and navigating to Management > General Settings > API Keys.

  4. Click Connect.

Configure Migration Settings

Complete the steps below to configure the migration settings.

  1. Click the Settings (gear) button on the upper-right corner of the page and select Background Migration from the drop-down list to access the Migration Settings page.

  2. On the Migration Settings page, configure the following information in the Basic Settings section.

    • Destination SharePoint Library NamingConvention – Choose the way to define the name of the destination library where you want to migrate file system data.

      • Use the root folder name as the library name – Use the root folder name of the file system connection as the destination library name.

      • Use the App Part name as the library name – Use the App Part name as the destination library name.

      • Customize a library name – Define a custom name for the destination library. Enter a name for the library in the text box. If the entered name is an existing library, the file system data will be migrated to the existing library directly.

    • Display Library in Navigation – Choose whether or not to display the destination library in site navigation. Select the Show the library in site navigation checkbox to display it.

    • Make App Part as Read Only – You can choose to make the app part as read-only in order to ensure data accuracy or follow your migration policy.

      • When the migration starts – Make the App Part as read-only when the migration starts, which means you cannot manage files in the App Part side when the migration starts.

      • When the migration ends – Make the App Part as read-only when the migration ends, which means you cannot manage files in the App Part side after the migration ends.

      • None – The App Part is always active during the migration, and you can manage files on the App Part side.

    • Maximum number of Jobs in Parallel – Choose the maximum number of migration jobs that can be run at the same time. Select a number from the drop-down list.

    • Migration Policy – Choose a migration policy from the drop-down list. Migration policy includes conflict resolutions, filters, mappings, and advanced migration options. You can go to Fly Server Manager to customize your own migration policy, and the customized policies can be loaded in this drop-down list.

      *Note: AvePoint recommends you configure a Folder level filter in your filter policy to exclude the hidden .apci folder for the migration. .apci folder is a hidden folder which resides in the root folder of the connection path, and it is best not to migrate this folder to the destination SharePoint library. The configuration of this Folder level filter in Fly Server can be Name + Does Not Equal + .apci.

  3. In the Account Settings section, configure the user information which will be used to run the migration.

    • App Profile – Choose an app profile from the drop-down list. The app profile is used to connect to the Microsoft 365 API with a Microsoft Entra ID app. With a Microsoft Entra ID app, API calls will be less throttled. The app profile is configured in Fly Server Manager, you can go to Fly Server Manager to add app profiles, and the added app profiles can be loaded in this drop-down list.

    • Microsoft 365 GlobalAdministrator – Configure the user to perform the migration jobs. The user must be the Microsoft 365 Global Administrator. Click the Modify button, the Configure page appears. Enter the username and corresponding password in the text boxes, and click Save.

  4. In the Active Runtime Settings section, configure and manage the time range to run the migration jobs. All the active runtime is displayed in the table. You can click the Delete (bin) button to remove the runtime. You can click Add Active Runtime to add new active time, and configure the following information in the Add Active Runtime window.

    • Choose the days to run the migration – Click the corresponding checkboxes to select the days that you want to run migration jobs.

    • Choose the time range – Configure the exact time that you want to run the migration jobs.

      • Whole Day – The active time range will be a whole day.

      • From … To … – Select the time from the drop-down list to define the active time range to run the migration jobs. Select the Next Day checkbox if you set the end time for the next calendar day.

    Click Add to add the runtime and repeat the procedures in this step to add additional runtime.

  5. Click Save to save all your configurations, or click Reset to clear your settings.

Perform Migration Jobs

The Migration page displays all of the app parts in a table. Click the Settings (gear) button on the upper-right corner of the page and select Background Migration from the drop-down list, and click Migration on the left pane to access the Migration page. The table displays the following information regarding the app parts and their migration jobs.

- **Connection Name** – The name of the connection that the app part connects to. - **App Part Name** – The app part name. - **Site URL** – The URL of the site where the app part resides. - **Migration Status** – The status of the migration job of the app part. There are the following statuses: Not Configured, Running, Waiting, Stopped, Finished, Finished with Exception, and Failed. **Not Configured** means no migration job settings have been configured for this app part. - **Next Job Run Time** – The runtime of the next migration job. This is only available for a scheduled migration job which has run one migration job. - **Actions** – The available actions that you can take for the app part. - Migrate (![Migrate icon.](/en/cloud-index-admin/configure-administration-settings/images/image3.png "Migrate icon.")) – Configure the migration job settings and run the migration job. Click **Migration** in the Actions column and set up the following information: - **Migration Method** – Choose the method to migrate the source objects. **Combine** means to migrate all content and configurations in the source object to the destination object; **Attach as** **a** **child** means to migrate the source file system as a child under the destination object. - **Migration Type** – Choose the migration type. **Full Migration** means to perform a migration for all data in the source; **Incremental Migration** means to perform a migration only for the data that had any changes since the last migration. - **Migration Schedule** – Choose when you want to run the migration job. Choose the frequency that you want to run the migration: Once, Hourly, Daily, and Weekly, and then select the start time for the job by selecting a date and exact time from the calendar button. Click **Migrate Now** to run the migration job immediately regardless of the start time you configure above; click **Save and Migrate** to save your job settings and wait to run the migration job until the start time, or click **Cancel** to return to the Migration page without saving any changes. > ***Note**: This button is only visible for an app part that does not have the migration job settings configured. - Stop – Click the Stop button in the **Actions** column to stop the running migration job and future scheduled jobs in the migration. > ***Note**: This button is only visible when the migration job for this app part is running. - Reset – Click the Reset button in the **Actions** column to remove the migration job settings and the migration reports and reset the migration status to Not Configured. > ***Note**: This button is only visible for the app part, which has performed a migration job. > ***Note**: Background Migration calls the Fly Server API to perform the migration job, so the Waiting status for the job indicates that you are waiting for the API communications on the Fly Server side. If you reset the job settings for a waiting job, the job behavior will differ based on whether the job has been invoked on the Fly Server side. - If the migration job has already been invoked on the Fly Server side, the invoked job will be stopped, and a migration job with new job settings will be invoked. - If this migration job has not been invoked on the Fly Server side, a migration job with old job settings and a migration job with new job settings will both be invoked. For this case, you can log into the Fly Server Manager to stop the previous migration job, and then only migration jobs with new job settings will be invoked. - Rerun – Click the Rerun button in the **Actions** column to configure the job settings and rerun the migration job. > ***Note**: This button is only visible for the app part which has performed a migration job. - Download – Click the Download button in the **Actions** column to download the migration job report in the .csv format. > ***Note**: This button is only visible for the app part which has performed a migration job.

Additionally, you can perform actions on an individual app part in the Actions column, and you can also perform the following actions on app parts in batch.

- **Migrate All Items** – Configure the migration job settings for all app parts that have not configured the job settings. Click **Migrate All Items** and configure the following information for all the available app parts. - **Migration Method** – Choose the method to migrate the source objects. **Combine** means to migrate all content and configurations in the source object to the destination object; **Attach as** **a** **child** means to migrate the source file system as a child under the destination object. - **Migration Type** – Choose the migration type. **Full Migration** means to perform a migration for all data in the source; **Incremental Migration** means to perform a migration only for the data that had any changes since the last migration. - **Migration Schedule** – Choose when you want to run the migration job. Choose the frequency that you want to run the migration: Once, Hourly, Daily, and Weekly, and then select the start time for the job by selecting a date and exact time from the calendar button. Click **Migrate Now** to run the migration job immediately, regardless of the start time you configure above; click **Save and Migrate** to save your job settings and wait to run the migration job until the start time; or click **Cancel** to return to the Migration page without saving any changes. - **Migrate Selected Items** – Configure the migration job settings for the selected app parts that have not configured the job settings. Select one or more app parts that have not configured the job settings, click **Migrate** **Selected** **Items** and configure the following information. - **Migration Method** – Choose the method for how to migrate the source objects. **Combine** means to migrate all content and configurations in the source object to the destination object; **Attach as** **a** **child** means to migrate the source file system as a child under the destination object. - **Migration Type** – Choose the migration type. **Full Migration** means to perform a migration for all data in the source; **Incremental Migration** means to perform a migration only for the data that has changed since the last migration. - **Migration Schedule** – Choose when you want to run the migration job. Choose the frequency that you want to run the migration: Once, Hourly, Daily, and Weekly; and then select the start time for the job by selecting a date and exact time from the calendar button. Click **Migrate Now** to run the migration job immediately, regardless of the start time you configure above; click **Save and Migrate** to save your job settings and wait to run the migration job until the start time; or click **Cancel** to return to the Migration page without saving any changes. - **Rerun All Items** – Rerun the migration jobs for the app parts that have configured the job settings. Click **Rerun All Items** and configure the following information. - Choose the migration type. - **Full Migration** – Perform a migration for all data in the source. - **Only migrate failed objects** – Perform an incremental migration to only migrate the failed objects. - **Migrate the failed, newly added, and/or modified objects** – Perform an incremental migration to migrate the failed, newly added, and/or modified objects. - Choose whether or not to configure a pre-defined start time for the migration job. Select the **Configure a Schedule** checkbox to set up a start time. Click **Save and Rerun** to save the job settings and rerun the job according to the schedule, if any, or click **Cancel** to return to the Migration page without saving any changes.

Manage Files

AvePoint Cloud Index provides you with a centralized interface to manage all of the files in different connections.

Click the Manage Files (file) button on the upper-right corner of the page to access the Manage Files page. All of the configured connections will be displayed on the left pane. You can perform the following actions in every connection: Upload, Download, Create Folder, View, Edit, Rename, Delete, Copy UNC Path, and Search. For details on how to use these actions, refer to AvePoint Cloud Index User Guide.