Administrators can create Shares user accounts that will automatically added to the local database (not a directory service). For DS users, please refer to the topic Configuring DS within Shares. Once a local user is created, he or she can be added to a local Shares group. To add a new local user, log in to Shares and go to Admin > Accounts > Users > New .

You will be prompted to input the following details:

Once you create a local user, you will be directed to the User screen, which displays seven tabs:

Tab Description
Detail

Update the local user's name, username and email address. You may also delete the local user from the Shares application.

Member of

Add this user to a local group by selecting one from the drop-down list. You will only see local groups that have been added to Shares (i.e. local groups that you have set up through the Shares UI).

IMPORTANT NOTE: You will not be able to add local users to a DS group; only local groups. For instructions on configuring DS users, see the topic Configuring DS within Shares.

After adding a local user to a local group, you may click the Edit link to modify the group's settings or Remove to delete them from the group (but not from the Shares application).

When you click the Edit link, you will be taken to local group's configuration page. Please refer to the topic Configuring Local Groups for details on modifying a local group's settings.

Security Under the Security tab, you can update the following settings:
  • Send the user a password reset link
  • Disable the user's account. Note that if you disable this user's account on this screen, then the user will not be able to log into Shares even if he or she belongs to a group that has group access permissions.
  • Explicitly allow the user to log into the Shares application.
  • Explicitly make this user an Administrator.
  • Allow the user to log into the API (which means that even if the user does not have BROWSE permissions, he or she can still perform transfer and file operations).
  • Set an account expiration date.
  • Set a temporary password.

Shares

Click the Add Share link to authorize specific shares for the local user to access. Note that if this user belongs to a local group, and the group has access to a share, then that share will be listed here (i.e., permission to access the share is "inherited" from the group).

Upon doing so, you will be provided a list of nodes and shares that are currently configured in your Shares application, along with an Authorize link.

After authorizing a share, you can modify the user's permissions for browsing, transferring and performing file operations within it. Note that the default permission is browse only. If browse is not selected, the user will only be able to access functions if he or she has been made an API User (see Security tab description above). To edit these permissions or de-authorize the user's access to the share, click the edit link.

From here, select (checkmark) permissions that the user has for the authorized share. For example, the user in our office example is only allowed to download and browse the marketing share; however, he cannot upload content or perform any file operations within the share.

After modifying your settings, click the Update button. You may de-authorize access to this share by clicking Delete.

NOTE: Non-admin users are not automatically notified when given access to a share unless they have explicitly enabled it. To enable notifications about shares access, users can open user > Preferences, locate the Authorization Email setting, and select Edit to change it. For non-admin users, the default setting is false. For admin users, default setting is true.

Preferences

Select a timezone and input any comments.

Transfer Settings

Implement transfer settings/restrictions specifically for this user. In doing so, you will be overriding Share's app-wide transfer settings and group settings (if the user belongs to a group).

Transfer settings include the following:

  • Upload target rate: For example, 1.5 Gbps, 500Mbps, 10 K, 3000. Leave blank to use the node's settings.
  • Upload target rate cap: For example, 1.5 Gbps, 500Mbps, 10 K, 3000. Leave blank to use the node's settings.
  • Download target rate: For example, 1.5 Gbps, 500Mbps, 10 K, 3000. Leave blank to use the node's settings.
  • Download target rate cap: For example, 1.5 Gbps, 500Mbps, 10 K, 3000. Leave blank to use the node's settings.
  • Starting policy: Select the policy that will be enforced when the transfer starts, where policies include fixed, high, fair and low. You can also select Inherit from node to use the node's settings. If fixed, the transfer will utilize a fixed rate policy. Under this policy, the transfer will transmit data at a rate equal to the target rate (although this may impact the performance of other traffic present on the network). If fair, the transfer will utilize a fair rate policy. Under this policy, the transfer will attempt to transmit data at a rate equal to the target rate. If network conditions do not permit that to be achieved, it will transfer at a rate lower than the target rate, but not less than the minimum rate.
  • Allowed policy: Select the policies that are available to the user during the transfer. You can also select Inherit from node to use the node's settings. For example, if the starting policy is fair, then you may allow them to change between fair and low by selecting the fair and low option from the drop-down list.
  • Encryption: Select from optional or AES-128. You can also select Inherit from node to use the node's settings.
  • Encryption at rest: Required or optional. You can also select Inherit from node to use the node's settings. If required, uploaded files must be encrypted during a transfer for the purpose of protecting them while stored on a remote server. The uploader sets a password before uploading the file, and then the downloader is required to enter that same password to decrypt the protected file.
Activity

View and search for Shares activity by this user.