RightSignature for ShareFile Overview

To Send Documents For Signature

To send a ShareFile document for signature, start by right clicking on the document and select Send for Signature.

User-added image

You will be redirected to RightSignature with the document uploaded. Click Prepare Document.

User-added image

Next enter the name and email of each signer. When finished, click Next: Place Fields.

User-added image

On the next screen you will create the signer and annotation fields for the document’s recipients. Click Next: Review when finished.

User-added image

Finally, you can add or edit a customized name and message, add CC’s, and add an optional document passcode. Click Send Document when done.

User-added image

To Sign Your Own Documents

To sign a ShareFile document, start by right clicking on the document and select Sign Yourself.

User-added image

You will be redirected to RightSignature with the document uploaded. Click Prepare Document.

User-added image

Select Add Signature under the Annotate section in the toolbar and drag the signature box onto the document where you wish to sign.

User-added image

You will immediately be prompted to sign the document. Use your mouse or trackpad to create a handwritten signature, upload a saved signature, or use the type-to-sign feature. Click Apply when you are ready to submit your signature.

User-added image

You can also use the other annotation tools to add text and checkmarks to your document. When finished, click Next: Review.

You will then have the option to share the document with others or simply save the document back to your Sharefile account.

User-added image

Related:

  • No Related Posts

How to install Root CA cert on the iOS 11 with Receiver 7.3 upgraded from 7.2

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

Unable to connect to StoreFront from NetScaler after logging into NetScaler page. Http/1.1 Internal Server Error 43531

Verify the StoreFront URL. In case of HTTPS store, Verify the certificate on StoreFront servers.

You should have the valid certificate for the Base URL and Base URL should be along with FQDN not anything like only hostname or something.

Example: StoreFront.Domain.com

Refer to Citrix Documentation – Configure NetScaler Gateway connection settings

Related:

  • No Related Posts

Recommended Hotfixes for XenServer 7.x

This article contains the complete set of recommended updates/hotfixes for XenServer 7.x .

For XenServer 6.x hotfixes, refer to CTX138115 – Recommended Hotfixes for XenServer 6.x

XenServer 7.4 XenServer 7.3 XenServer 7.2 XenServer 7.1 XenServer 7.1 CU1 XenServer 7.0

For more information, refer to the following Knowledge Center articles

Note: Citrix recommends updating the XenServer Console before updating any new hotfixes. All XenServer hotfixes can be applied at the same time and the hotfixes in the article are not relevant to the installation order

Hotfix XS74E003 –

For XenServer 7.3
This is a hotfix for customers running XenServer 7.4. All customers who are affected by the issues described in CTX235745 – Citrix XenServer Security Update for CVE-2018-3665 should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Content live patchable** Yes
XenServer 7.3.0 Update The link contains XenServer 7.3 Current Release as an update package. This update can be applied by using XenCenter to an existing XenServer 7.2 installation.

For more information, see the XenServer 7.3 Release Notes and Installation Guide.
XenCenter 7.3.0

This release of XenCenter is for customers who use XenCenter as the management console for XenServer 7.3.

Hotfix XS73E006 –

For XenServer 7.3
All customers who are affected by the issues described in CTX235745 – Citrix XenServer Security Update for CVE-2018-3665 should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Content live patchable** Yes
XenCenter

This hotfix is for customers who use XenCenter as the management console for XenServer 7.2.0. It constitutes two deliverables:

File Name Description Download Link
XenServer-7.2.0-XenCenterSetup-7.2.0.exe This file updates the XenCenter Windows Management Console DOWNLOAD
Hotfix XS72E005-

For XenServer 7.2

All customers who are affected by the issues described in CTX225941 – Citrix XenServer Multiple Security Updates should install this hotfix.

In addition, it resolves the following issue:

  • When large number of VMs are booted together, a kernel softlockup can occur resulting in kernel crash.

Content live patchable* Yes

This hotfix also includes the following previously released hotfix:

Hotfix XS72E010-

For XenServer 7.2
All customers who are affected by the issues described in CTX230138 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable* No
Hotfix XS72E014-

For XenServer 7.2
This is a hotfix for customers running XenServer 7.2. All customers who are affected by the issues described in CTX233832: Citrix XenServer 7.2 Multiple Security Vulnerabilities should install this hotfix.

Content live patchable* No
Hotfix XS72E017-

For XenServer 7.2

All customers who are affected by the issues described in CTX234679 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Content live patchable* No

XenServer 7.1 Cumulative Update 1 (XS71ECU1) should be installed by customers running XenServer 7.1. It includes all previously released XenServer 7.1 hotfixes. Installation of XS71ECU1 is required for all future functional hotfixes for XenServer 7.1 LTSR. XenServer 7.1 Cumulative Update 1 and its subsequent hotfixes are available only to customers on the Customer Success Services program.

Citrix will continue to provide security updates to the base XenServer 7.1 product for a period of three months from the release date of the XenServer 7.1 Cumulative Update 1 (until December 11, 2017). After this three month period elapses, any new hotfixes released will only support XenServer 7.1 with CU1 applied.

XenCenter 7.1.2

This release of XenCenter is for customers who use XenCenter as the management console for XenServer 7.1.

XenCenter 7.1.2 is available on the Citrix downloads site as a restricted download. You must sign in to the site and have active membership of the Customer Success Services (CSS) program to access these downloads.

Hotfix XS71ECU1006-

For XenServer 7.1CU1
This is a hotfix for customers running XenServer 7.1 Cumulative Update 1. All customers who are affected by the issues described in CTX230138 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable* No
Hotfix XS71ECU1007-

For XenServer 7.1CU1

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerability as described in the Security Bulletin above. In addition, it resolves the following issues:

  • Occasionally, when SMB servers do not accept echo requests while reconnecting the sessions, the ISO SRs using the CIFS protocol become unavailable and may be recovered only by unplugging the SR or rebooting the host.
  • Race condition during a VM operation can lead to incorrect locking and reference counting in the ipset subsystem in Control Domain (dom0) and may occasionally cause a host crash.
  • Due to a race condition in Control Domain (dom0) kernel, multipath failover on a storage repository (SR) can occasionally cause a host crash.
  • Incorrect locking in the Fibre Channel subsystem of control domain (dom0) can lead to a deadlock causing the storage to stop working.
  • Incorrect locking in the iSCSI subsystem of the Control Domain (dom0) can cause corruption of critical data structures and result in sporadic host crashes.
Content live patchable* No
Hotfix XS71ECU1011-

For XenServer 7.1CU1
This hotfix addresses the following issues:

  • When you copy a Virtual Disk Image (VDI) into a thinly-provisioned SR (NFS, EXT or SMB) that does not have enough space for the VDI, the copy fails and does not report an error.
  • On Nutanix hosts, the host’s memory-overhead is miscalculated after first boot. This is because toolstack (XAPI) calculates the available host RAM on startup assuming no domains other than the XenServer Control Domain are running. On first boot this is true but on subsequent boots, the Nutanix Controller VM (CVM) is started before toolstack.
  • When migrating VMs that have Dynamic Memory Configuration enabled, the VMs shutdown operation can unexpectedly fail. This is caused by memory consumption shrinking before shutdown and this operation takes longer than expected.
  • On rare occasions, after a toolstack restart, XenServer cannot recognize the host a VM is located on. This is caused by failed VM migration misleading the xenopsd daemon, which toolstack queries on startup.
  • If the disable_pv_vnc key in a paravirtualized VM’s other_config field is set to 1, the xenconsoled daemon stores all console output from this VM. This can cause the xenconsoled daemon to consume all memory in control domain (dom0).
  • When XenServer loses connection to the license server, the v6d license daemon grants a grace license when it temporarily cannot reach the license server. For some license types it would not grant such a license.
Content live patchable* No
Hotfix XS71ECU1013-

For XenServer 7.1CU1
This is a hotfix for customers running XenServer 7.1 Cumulative Update 1. All customers who are affected by the issues described in CTX232655 – Citrix XenServer Multiple Security Updates should install this hotfix.

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above. In addition, it resolves the following issue:

  • If SNMP configuration is modified to request interface statistics Object Identifiers (OIDs) and when SNMP service happens to start before Openvswitch service, all further statistics requests to SNMP returns incorrect data.
Content live patchable* No
Hotfix XS71ECU1014-

For XenServer 7.1CU1

This hotfix addresses following issues:

  • After rebooting, a XenServer host can fail to connect to iSCSI targets on Compellent arrays.
  • When shutting down, the XenServer host can hang at ‘reached target shutdown’. This happens if XAPI is unable to cleanly unplug PBDs to iSCSI SRs before shutdown.

This hotfix also includes the following previously released hotfix:

Content live patchable* No
Hotfix XS71ECU1015-

For XenServer 7.1CU1

This hotfix addresses following issues:

Customers using Active Directory (AD) with XenCenter are unable to log on to XenCenter, or get disconnected intermittently. In some cases, XenCenter displays incorrect AD group membership details. This hotfix resolves this issue.

Content live patchable* No
Hotfix XS71ECU1019-

For XenServer 7.1CU1

This hotfix resolves the following issues:

  • A race condition in XenBus can cause pauses in Windows VM operation, which lead to Timeout Detection and Recovery (TDR) events. The TDR can cause the VM to crash.
  • Under low resource situations, Xennet can consume all of the RAM on a Windows VM. This causes the VM to crash.
  • XenVBD can consume 100% of a vCPU and can block other processes from using that vCPU.
Content live patchable* No

This hotfix also includes the following previously released hotfixes:

Hotfix XS71ECU1022-

For XenServer 7.1CU1
All customers who are affected by the issues described in CTX235745 – Citrix XenServer Security Update for CVE-2018-3665 should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Content live patchable** Yes
XS71ECU1

For XenServer 7.1

XenServer 7.1 Cumulative Update 1 (XS71ECU1) should be installed by customers running XenServer 7.1. It includes all previously released XenServer 7.1 hotfixes. Installation of XS71ECU1 is required for all future functional hotfixes for XenServer 7.1 LTSR.

XenServer 7.1 Cumulative Update 1 and its subsequent hotfixes are available only to customers on the Customer Success Services program.

Citrix will continue to provide security updates to the base XenServer 7.1 product for a period of three months from the release date of the XenServer 7.1 Cumulative Update 1 (until December 11, 2017). After this three month period elapses, any new hotfixes released will only support XenServer 7.1 with CU1 applied.

For more information about XenServer 7.1 CU1, see the Citrix XenServer 7.1 Cumulative Update 1 Release Notes.

Prerequisite
  • XenServer 7.1

  • Licensed customer with Customer Success Service

Post-update tasks Restart Host
Content live patchable* No

* Available to Enterprise Customers.

Apply the following hotfixes for XenServer 7.0 and restart XenServer when the hotfix installation is complete.

Hotfix XS70E001 –

For XenServer 7.0
This is a XenCenter update (a .exe file) and not a host side Hotfix. This package needs to be installed

on the Windows Machine Running XenCenter
Hotfix XS70E002 – For XenServer 7.0 All customers who are affected by the CVE-2016-2107 issue described in

CTX212736: Citrix XenServer Multiple Security Updates should install this hotfix.
Hotfix XS70E004 – For XenServer 7.0 Important: This is a critical hotfix for customers running XenServer 7.0. All XenServer 7.0

customers must apply this hotfix.
Hotfix XS70E009 – For XenServer 7.0

This hotfix resolves the following issue:

  • In rare circumstances when a XenServer host is enabling HA, or during a host reboot with HA enabled, the host can fail to establish HA communication with the other hosts. This is due to another process on the host using the listening port required by the HA software.
Update XS70EU001 – Management Agent for XenServer 7.0 The Management Agent update resolves the following issues:

  • Installation of Management Agent can fail after installing newer I/O drivers through Windows Update.
  • Failure to reboot a Windows VM after installing XenServer Tools can result in excessive log entries being written to xensource.log and xenstored-access.log until the VM is rebooted. If customers do not reboot the VM, or delay the reboot, excess logs can fill up the XenServer host log partition.
  • The Management Agent can crash and respawn on systems without a terminal services Windows Management Instrumentation (WMI) object causing high CPU usage and excessive logging in /var/log/daemon.
  • If the Management Agent auto update is enabled after installing XenServer Tools, and a new update is available, the initial auto-update can fail due to a race condition that can cause multiple update attempts to occur simultaneously.
Update XS70EU002 – Management Agent for XenServer 7.0 New versions of the I/O drivers, compatible with Microsoft Windows Server 2016 have been released.
Update XS70EU003 – Management Agent for XenServer 7.0
  • The default behavior of the Management Agent has been improved to enable customers to configure whether any I/O driver updates included in the Management Agent should be applied automatically. For more information, see section 4.3.1 Installing XenServer Tools in the XenServer 7.0 Virtual Machine User’s Guide.
  • This version (v7.1.844) of the Management Agent includes new versions of the I/O drivers that are compatible with Microsoft Windows Server 2016. These drivers have been released previously through the Microsoft Windows Server Update Service. For more information, see Update XS70EU002 – Windows I/O Drivers for XenServer 7.0.
Hotfix XS70E018 – For XenServer 7.0 This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX220112: Citrix XenServer Multiple Security Updates should install this hotfix.
  • This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX219378: Citrix XenServer Multiple Security Updates should install this hotfix.
  • This hotfix supports the improvements to XenServer’s Direct Inspect APIs.
Hotfix XS70E024 – For XenServer 7.0
  • When booting a vGPU provisioned Virtual Machine (VM) from network, an interaction between VGA BIOS and VGA emulation code in the vGPU device model can result in the corruption of the VM console in XenCenter.
Hotfix XS70E027 – For XenServer 7.0
  • When Installing XenServer or upgrading XenServer to a newer version, PBIS services get enabled (even when Role-based access control (RBAC) is not used) and display a lot of error messages. Also, this issue consumes a lot of control domain (dom0) resources.
Hotfix XS70E028 – For XenServer 7.0 This hotfix supports the following new guest operating systems.

  • Oracle Linux 6.8
  • Red Hat Enterprise Linux 6.8
  • CentOS 6.8
  • NeoKylin Linux Advanced Server 6.5 ( only 64 bit )
  • NeoKylin Linux Advanced Server 7.2 ( Only 64 bit )
  • SUSE Linux Enterprise Server 11 SP4
Hotfix XS70E030 – For XenServer 7.0

This hotfix resolves the following issues:

  • Virtual Disk Image (VDI) operations on some Logical Volume Manager (LVM) over iSCSI (lvmoiscsi) configurations may experience long response times due to excessive scanning of the iSCSI fabric.
  • An error errno -12 is experienced at tapdisk_control_accept that can cause VMs to become unresponsive. This issue occurs when there are multiple I/O requests that lead the tapdisk scheduler’s uuid to overflow its positive integer range and becomes negative.
  • Probing an LVM over Fibre Channel or Fibre Channel over Ethernet or iSCSI HBA or SAS SR (lvmohba) backend containing an MPT-SAS adapter may result in an exception.
  • iSCSI configurations from some vendors require the Storage Manager to take code paths which can lead to an incorrect invocation of scsi_id. This can result in the SR being detached on the pool member, after creation.
  • When Block Allocation Map (BATMAP) in Xapi database contains erroneous data, the parent Virtual Hard Disk (VHD) does not get inflated causing coalesce failures and ENOSPC errors.
  • This fix lets users set a custom retrans value for their NFS SRs thereby giving them more fine-grained control over how they want NFS mounts to behave in their environment.
  • After applying Hotfix XS70E005 the sm-multipath is removed from the list of services. The removal of sm-multipath is observed only when the XenServer host restarts. If the root disk is managed by multipath, then the number of paths reported by it can possibly be incorrect.

This hotfix also includes the following previously released hotfix:

Hotfix XS70E037 – For XenServer 7.0

This hotfix addresses the following issue:

  • When attempting to use XenServer Conversion Manager (XCM) Console to connect to an XCM Virtual Appliance that runs on a slave host, the connection fails and the following message is displayed by the console: “There was a failure communicating with the plugin.” This hotfix ensures that the XCM Console can connect to a XCM Virtual Appliance that runs on any XenServer host.
Hotfix XS70E041 – For XenServer 7.0

This hotfix resolves the following issue:

  • When using SSH to connect to XenServer, a user might experience a memory leak in systemd on XenServer.
Hotfix XS70E042 – For XenServer 7.0

This hotfix resolves the following issues:

  • Excessive input/output from a process could trigger a SCSI target reset while the process is still ongoing. This leads to tapdisk logs reporting invalid request type and/or invalid number of segments, and filling up the Dom0 log partition. This issue occurs due to a race condition that leads to an incorrect reference count.
  • When running XenDesktop on XenServer, if you have logged on to the console session using terminal services, then, multiple XenDpriv.exe processes are seen running. This issue occurs when VMs treat all logins as if they were console logins.
  • When installing windows PV tools on Windows 10 and Windows Server 2016, users are not notified to reboot the VM in order to continue with the driver installation.
  • If the clipboard buffer on a VM contains the “%s” format specifier, the VM can bug check with error SYSTEM_SERVICE_EXCEPTION 0x3B (c0000005).
  • When a Virtual Network Interface (VIF) receives malformed packets, the virtual CPU (vCPU) can cause Windows VMs to rise to 100% CPU usage and become unresponsive at the console.

This hotfix also includes the following previously released hotfix:

Hotfix XS70E043 – For XenServer 7.0

This hotfix resolves the following issue:

  • Under certain workloads on Skylake and Kaby Lake processors with Hyper-Threading enabled, applications can crash or incorrect program behavior can be observed. Microcode update fixes this issue.
Hotfix XS70E048 – For XenServer 7.0 This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX230138 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Hotfix XS70E052 – For XenServer 7.0 This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX232655 – Citrix XenServer Multiple Security Updates should install this hotfix.This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.
Hotfix XS70E053 – For XenServer 7.0

This hotfix addresses the following issues:

  • Rarely, after a toolstack restart, XenServer does not recognize which host a VM is located on. This is caused by a failed VM migration misleading the xenopsd daemon, which Xapi queries on startup.
  • If the disable_pv_vnc key in a paravirtualized VM’s other_config field is set to 1, the xenconsoled daemon stores all console output from this VM. This can cause the xenconsoled daemon to consume all memory in control domain (dom0). This fix restricts the amount of console output that the xenconsoled daemon stores for each VM to a 64 KB rolling buffer.
  • After installing a XenServer hotfix that recognizes an extended set of CPU features, XenCenter can incorrectly raise an alert that says some CPU features have disappeared.
  • Changing the name or description of a snapshot Virtual Disk Image (VDI) can cause a VM snapshot to lose track of its virtual disks (VDIs). This makes it impossible to revert the VM to the snapshot.

This hotfix also includes the following previously released hotfixes:

Hotfix XS70E054 – For XenServer 7.0

This hotfix addresses the following issues:

  • Race condition during a VM operation can lead to incorrect locking and reference counting in the ipset subsystem used by Cloudstack in Control Domain (dom0) and may occasionally cause a host crash.
  • Forcing a delayed work, to run in local CPU, exposed a bug in timer code. This bug triggered a Kernel panic due general protection fault.

This hotfix also includes the following previously released hotfixes:

Hotfix XS70E058 – For XenServer 7.0 All customers who are affected by the issues described in CTX235745 – Citrix XenServer Security Update for CVE-2018-3665 should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Related:

  • No Related Posts

Troubleshooting NetScaler Hard Disk Errors

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

NetScaler : HDX Insight Shows only 1 hour of data in NetScaler MAS

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

Windows Computer Name does not show the current layer ID number when creating a new layer

There are three main reasons why you might see the machine name not agree with the layer ID:

  • If you rename the machine for an App Layer, the captured registry hive may remember the name change
  • If you use a layer that renamed the machine as a prerequisite when creating or editing a layer
  • If you are using Layer Caching in your connector

When we construct the boot disk, we copy the registry hives from the OS layer, and then we immediately write in the new Windows machine name. Then we play in any prerequisite layers, and then we play in the current layer’s changes (if this is a Add Version instead of a Create Layer). This means that any change of the Windows Machine Name that is played in from a prerequisite layer or previous version of the layer you’re editing will overwrite the machine name as set by the ELM initially.

However, you can also see this problem when you create the first version of a layer, even if you are not using prerequisites, if you are using Layer Caching in your Connector. With Layer Caching, we upload the boot disk once, and for any subsequent layer operations, we clone the previously uploaded boot disk (or the customized boot disk for that specific layer version). The first time you create a layer, we build the boot disk normally, including putting in the Windows machine name. That disk is uploaded, and then it’s cloned to become the personal, customized boot disk for the specific app layer you’re editing. The original uploaded boot disk is left behind so that it can be used for other new layers.

When you create another new app layer, we clone the boot disk that was uploaded for the previous layer, including the machine name. So as long as that initial boot disk remains cached and usable for new layers, it will continue to supply new layers with the Computer Name that was set for the original layer. Each cached layer version keeps its own customized boot disk, which is why layers can individually same machine name changes. It’s only the first version of a layer, that is using a cached boot disk, that could see this.

The workaround is to ignore this, or if your infrastructure absolutely requires unique machine names for different layers (for joining the domain, for instance, if you require that in a layer), to manually edit the machines after they boot.

Related:

  • No Related Posts

Receiver stuck in Connection in progress

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

How to Manage Employee Permissions in ShareFile

How to Manage Permissions

  1. Go to People > Manage Users (or Browse Employees or Browse Clients)
  2. Browse or search for your user. Click the user or the Manage icon on the right, to open the user profile.
  3. Modify permissions as needed, then Save.

Default Employee Permissions

When creating a new employee, the following permissions are granted by default. You can modify these settings during the user creation process.

Note: A grayed setting indicates a permission that the creating user does not have access to or is not permitted to give to others – therefore, they cannot grant that permission to another user.

User Access

Basic Information:

  • Date Created
  • Email Address
  • First Name & Last Name
  • Company name.

Notifications

Modify the user’s default Notification Frequency settings.

Default Email Language

Modify the user’s default Email Notification Language.

Bandwidth Limit

You may select a maximum monthly bandwidth allowance for the employee. This limit will prevent the employee from personally uploading and downloading more data than you allow them. It will also apply to all of their folders, so that they may not share files with others more than you would like for them to.

Note: Employee bandwidth limits can also affect clients that the employee works with by limiting how much they may download from the employee’s folders. This is used by some accounts where employee use may need to be limited to prevent bandwidth overages.

Authentication

Whether the customer is utilizing ShareFile Credentials or Two-Step Verification.

User Access:

General

Change their password

If a user may change their password, they can use the ‘Forgot Password’ link on the login screen if they ever forget the password. If this is not marked, they will need to contact an employee who can manage employee permissions for help logging in.

Access Personal Settings

In personal settings, a user can manage their name, company name, and avatar. They will be able to update or change their password on this page if they have the permission to change their password.

Files and Folders

Use personal File Box

The File Box is a personal storage space where employees may store files for a limited period of time. This space is not generally a collaborative or shared space, although some users may be given access to see other employee’s File Boxes. If you do choose to take away a user’s access to the File Box, they will not be able to use any email plugin tool or add files from their computer when creating a Share message or Link.


Be added to file drops

This will only be available if File Drop is enabled on your account. This will allow users who create new file drops to list this employee as a contact that clients may select to send files to through a form.

People

Manage Clients

This will allow the employee to see the People tab in the navigation bar and to add new users to the account. They will also be able to edit settings for any clients that they create.

Note: Editing a client user’s email address requires the Manage Employees permission.

Edit the shared address book

The Shared Address Book is available to employee users on the account so that they may quickly and easily pull up contact information for users on the account. If this is checked, the employee will be able to add users to the Shared Address Book to allow others to see their contacts on the system.


Share distribution groups

If this permission is enabled, the employee user will be able to create a Shared Distribution group.


Edit other users’ shared distribution groups

When setting up a new Distribution Group, users will have the option to share the group with all employees. If this permission is enabled, the employee user will be able to add more users to a group that has been created on the system and shared with others.

Company Account Info

Edit account appearance

Allow the user to configure account branding and appearance settings.

Billing


View receipts and billing notifications

The Receipts & Billing Notifications link in the Admin Settings > Billing section will allow any user with this permission enabled to download copies of any receipt or invoice for the account.

*You may or may not see the below settings on your user page. These settings will display only if you have the feature enabled on your plan type.


Advanced Preferences

Connectors

Create Network Share Connectors

This permission grants the user the ability to create and manage new Network Share-type Connectors. This permission is only available to ShareFile users on select plans.

Create SharePoint Connectors

This permission grants the user the ability to create and manage new Sharepoint-type Connectors. This permission is only available to ShareFile users on select plans.


StorageZones

Select StorageZone for root-level folders

In order to change another user’s default storage location, membership to the Super User Group is required. This permission is only available to ShareFile users on select plans.


Related:

  • No Related Posts

ShareFile for Android


Supported Localization: German, French, Spanish, Japanese, Simplified Chinese, Korean, Dutch, Russian and Portuguese.


Requirements and Limitations

Related:

  • No Related Posts