|
|
|
|
|
Temporary Users ("Temp Users") can be limited to a minimal level of access to MOVEit Transfer resources. Temporary users (like other users) can be configured to expire after a certain amount of time has passed. (See the Expiration Policy Feature Focus page for more information about expiration policies)
Temp Users are available to an organization when you configured it for either or both of the following licensed feature sets:
Temp User are allowed to sign in to MOVEit Transfer through the web and API interfaces, they are not integrated for FTP or SSH interfaces.
Temp Users can view packages sent to them, download files included in the package, and may send packages to users who they are authorized to send to. Temporary users can be granted access to shared folders.
Temporary users can change their password.
If the organization administrator configures Ad Hoc Transfer to create 'Temporary Users', when a registered user sends a package, the temporary-user recipients will receive a password for that package only. The temporary-user recipients will log on with that password, and can view a package, download files in it, and reply to the package. The Temporary User will have an account on the MOVEit Transfer system; the Temporary User suits limited-time use scenarios.
If the administrator enables Unregistered Senders along with 'Temporary Users', an unregistered user can self-register as a temporary-user sender. The temporary-user senders will either be automatically logged on after self-registering with a "Captcha" or they will manually log on with password using either a password or "password link" sent by email after they self-register. Then they can create a package, upload files to it, and send it.
Erin is a registered Ad Hoc Transfer user. Sending packages to Temp Users was enabled by her MOVEit Transfer Admin. She has the option of sending a MOVEit Transfer package to an email address rather than an exclusive list of registered users in her Contacts list. When composing her new package to a user outside of her org, Rodger, Erin is prompted for his email address, full name, and a password; Erin delivers the password over the phone.
Rodger, a new Temp User has limited access to Ad Hoc Transfer (he can only communicate with Erin) and his account automatically expires after 7 days of inactivity (or according to the temporary user expiration settings established by Erin the administrator).
David is an unregistered user, but he has access to a MOVEit Transfer sign on page (or equivalent API) that was configured to enable self-registration for temporary users. He needs to send a package and/or files to Erin, a registered Ad Hoc Transfer user. Normally, Erin would need to get her administrator to add David to the system, but because self-registration as a temporary user was enabled, David can self-register and then send Mary a package to her email address. After David self-registers, enters Mary's email address, his email address, and the letters in the "Captcha" question (to prove he is not a robot). David is then prompted for a password.
David has now been set up as a temporary user. For this package, he has limited access to Ad Hoc Transfer (he can only communicate with Erin) but he has been set up to have wider access (the ability to send to other users) until his account expires. His account will automatically expire after 7 days of inactivity (or according to the temporary user expiration settings established by Erin's administrator).
In a few seconds Mary receives an email that contains a link to the new package David sent to her. She can use her email or MOVEit Transfer account to view the package, download files, and reply and send files to David.
A Guest User has capabilities similar to a Temporary User, except that the Guest User is further restricted to viewing or sending a single package. If the administrator configures Ad Hoc Transfer to use 'Package Passwords', when a registered user sends a package, the guest-user recipients receive a password for that package only. The guest user recipients log on with that password, and can view a package, download files in it, and reply to the package. The Guest User does not have an account on the MOVEit Transfer system. The Guest User suits one-time use scenarios.
If the administrator enables Unregistered Senders along with 'Package Passwords', an unregistered user can self-register as a guest-user sender. The guest-user senders are either be automatically logged on after self-registering with a "Captcha", or they manually log on using a password sent by email after they self-register. Then they can create a package, upload files to it, and send it.