Back: Discover and report - Egnyte

Available Reports

The following reports can be generated for Egnyte Connections:

ReportDescription
Egnyte Object TotalsProvides the total number of all types of object that will be migrated
Permissions by ObjectIdentifies the permissions applied to each object. Can be used to find locations with too many permissions
Permission CountsCount of permissions by user

Egnyte Object Totals

This report provides information about:

  • The total number of objects within a scanning scope

  • Estimated Data Volume for each user and across the scanning scope

Best Practice: Determine the total number of objects in the source environment to discover potential migration performance impacting factors such as high permission counts, or excessive data volume

Report fields

This report contains the following fields:

 

Field Name

Description

User

Owner

Egnyte Private Folders

Count of private folders

Egnyte Files

Count of files

Egnyte Shared Folders

Count of shared folders

Egnyte PermissionsCount of permissions
Egnyte Permissions SetCount of permission sets
TotalTotal count

Permission Counts

This report provides information about:

  • The total number of users with permissions within a scanning scope

  • How many permissions each user is assigned
     

Best Practice: Identify power users with high content ownership and numbers of permissions and permission sets. Create mappings to balance the content ownership across the target domain or split power users into multiple bridges to increase migration performance.

Report fields

This report contains the following fields:

 

Field Name

Description

Email

The name of each user account within the scanning scope

Total

The number of permissions assigned to the user or group

Permissions by Object

This report provides information about:

  • The total number of sharing rights assigned to each object within the scanning scope

  • The owner of each object within the scope, and each user with editor and viewer rights

  • Each object with permissions explicitly assigned rather than inherited from its parent folder
     

Best Practice: Identify each object with complex sharing settings by discovering locations with high permission counts and non-inherited, or explicitly assigned permissions. Easily preserve the desired permissions infrastructure by assigning a group permission at the root level of all locations which only rely upon inherited permissions.

Report fields

This report contains the following fields:

 

Field Name

Description

User

Owner

Id

ID for the file or folder

Path

Path to the object

Title

Name of the object

Total

Number of users with permissions to the object