Configure self-registration user defaults

Edit online
New users created by approved self-registration requests inherit self-registration user defaults. You can configure these defaults by going to Security > Account registration and clicking Configure defaults.

Account details and security

Setting Description
Account expires Select to set an expiration date for the user. The user becomes inactive on the specified date.
Note: Admin accounts do not expire.
Account is active Select to activate this account so that the user can log into Faspex. Clear to disable the account.
Note: Admin accounts are always active.

Custom password policy

Setting Description
Override default password policies Enable to set password expiration and password reuse limits.
Password expires and Days until password expires Expire passwords a specified number of days after they are set.
Prevent password reuse and Number of previous passwords

Prevent users from reusing a specified number of previously used passwords.

User permissions

Setting Description
Upload packages The user can upload packages to a node. Disabling this does not prevent the user from sending a package from a shared folder, if Create packages from a remote source is enabled.
Download packages The user can download received packages. When disabled, the user can still receive packages, but cannot download packages or the packages' files.
Forward packages The user can forward received packages to other users.
Send packages from a remote source The user can include content from a shared inbox when sending a package.

You must first add remote sources to Faspex to see the Source drop-down menu.

This setting must be set on a per-user basis. There is no global option to enable this setting for all users.
Send normal packages

If disabled, the user can only send packages to shared inboxes.

You can change the server default by doing to Security > Users.
Invite external senders You must enable this option globally to override this feature. For more information, see Allow Faspex users to send packages to external users.

Override the server default and select Allow to enable this user to invite anyone to send a package to this user.
Share submission links

You must enable this option globally to see this feature. For more information, see Public submission links.

Override the server default and select Allow to enable users to share their public submission link. Anyone with a public submission link can submit packages to this user through this submission link.

Note: Even if the public submission link feature is enabled for registered Faspex users, they can override the feature for their own account by going to their user preferences. See Share your public submission link.
Send packages to external emails

Override the server default and select Allow to enable the user to send packages to external email addresses. For more information, see Allow Faspex users to send packages to external users

Select Allow to enable this user to send packages to external.
Send to all Faspex users Override the server default and select Allow to allow users to send packages to all Faspex users.

If this feature is enabled, all existing Faspex users appear in the contact list.

By default, users can send packages to:
  • Users in their contacts
  • Personal distribution lists
  • Shared inboxes
  • Workgroups they are a part of (if workgroup settings allow)
  • Members of workgroups they are a part of (if workgroup settings allow)
  • Global distribution lists (if allowed to see)
See global distribution lists Override the server default and select Allow to enable the user to see and send to global distribution lists.
Keep user directory private Override the server default and select Yes to prevent users from being able to see the entire user directory, even if they have permissions to send to all Faspex users.

IP permissions

Important: Restricting access by IP address requires the requesting client's IP address be preserved through the TCP/IP network until the request reaches Faspex. If you have a network configuration that passes the requesting client's IP address through the network with the X-Forwarded-For HTTP Header, you will not be able to restrict access to Faspex via IP addresses.
Tip: For all of these settings, you can use a wildcard (*) to allow a range of options. For example, specifying 192.0.2.* allows a user to login from 192.0.2.1, 192.0.2.2, 192.0.2.3, and so on. Separate multiple IP addresses with commas (,).
Setting Description

User can log in from only these IP addresses

 Specify the IP addresses that a Faspex user can login from.

User can download only when downloading from these IP addresses

 Specify the IP addresses that the user must access Faspex from to download packages.

User can send packages only when sending from these IP addresses

Specify the IP addresses that the user must access Faspex to upload packages.