This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Information Request
When to Use Information Request
An Information Request in ShareFile Projects allows you to collect structured data, text inputs, or form-style responses from clients or internal teams — all tied to your project workflow. Unlike Document Requests, which collect files, an Information Request gathers details, numbers, or statements through a configurable form that you can design and share directly from your project workspace.
Key Use Cases
You can use information requests:
- To collect client information such as personal details, service inputs, or onboarding data.
- To request structured information from internal teams for status updates or internal reporting.
- When you need repeatable, form-based submissions for audits, tax data, or intake workflows.
- When you want to reduce file attachments and rely on typed or selectable responses instead.
Key Benefits
- Centralized, secure way to collect typed responses.
- Full visibility into completion and submission status.
- Conditional logic to show or hide form sections based on responses.
- Auto-save allows respondents to return later and finish incomplete forms.
- Easy export of responses to CSV for analysis or reporting.
How to create information request
To create an information request in a project, you can follow the steps given below:
-
Navigate to the Project
a. From the ShareFile web app, select Projects from the left-hand menu.
b. Open the project where you want to create the Information Request.
-
Access Information Requests
a. On the project dashboard, select the Requests tab.
b. Click on the Create Request button.
c. Hover over the information request section.
d. Select one option from either blank or template.

-
Add Request Details
a. Enter a Title for your Information Request.
b. (Optional) Add a Description explaining the purpose of the form.
c. Set a Due Date if you need the form completed within a specific timeframe.
-
Design the Request Form
a. Add questions or fields by selecting Add fields.
b. Choose a Field Type for each question:
- Short Text
- Paragraph Text
- Date Picker
- Dropdown / Multiple Choice
- File Upload (optional hybrid field)
- Yes/No Toggle
c. Reorder questions using drag-and-drop.
d. Use Conditional Logic to show or hide questions based on earlier responses. Example: Show “Proof of Address” field only if user selects “Yes” for “Do you reside in the U.S.?”
-
Assign Recipients
a. Select internal users or clients who need to complete the request.
b. Each recipient will receive an email notification with access to the form.

-
Configure Reminders
a. Automatic reminders are sent 1, 3, 5, and 10 days before the due date.
b. Post-due date, reminders are sent daily for 30 days after the deadline until completed.
c. You can also send manual reminders from the three-dot menu (…).
Life cycle of an information request
| Stage | Description | User Actions |
|---|---|---|
| Draft | Request created but not yet published. | Edit fields, add recipients, preview form. |
| Active | Request shared and open for responses. | Recipients complete and submit. |
| Partially Complete | Some recipients have submitted, others pending. | Send reminders or review progress. |
| Completed | All responses submitted and approved. | The owner can export or close the request. |
| Closed | Locked for further edits. | Forms remain viewable but not editable. |
Additional Capability
Send for resubmission
An IR response can be sent back for resubmission.
- Open the response.
- Click on Reopen button.
- Add note and click Send for resubmission
Note:
An information request sent back for resubmission will appear as open task on client portal. No need for the assigner to start from scratch, previous saved response will appear as draft and after editing the response can be submitted again.
Templates
You can save templates to reuse pre-defined information request forms.
-
Create a Template
a. Open an existing Information Request.
b. Click on Save as Template.
c. Enter a name and optional description.

-
Use a Template
a. Select Create from Template in the Information Request tab.
b. Choose a saved template.
c. Update fields or recipients as required.
Templates help standardize recurring workflows such as compliance checks, vendor onboarding, or client surveys.

Auto Save Progress
How It Works
- Auto-save occurs every few seconds or when the user navigates between questions.
- Saved data is stored securely in the user’s ShareFile account context — no manual “Save” button is required.
- If the browser closes unexpectedly, the system restores progress when the user reopens the form.
- Each auto-save is timestamped with “Last Saved at [time]” displayed at the bottom of the form.
Client Visibility
- A small indicator (“Auto-saved”) appears briefly whenever progress is captured.
- Clients can safely close the window and return later using the same link. They can also use the Projects -> Requests tab or open the Form tasks directly from client portal.
Conditional Logic
Overview
Conditional Logic allows you to dynamically control which questions appear on an Information Request form based on a respondent’s earlier answers. This enables adaptive forms that simplify the user experience by hiding irrelevant questions.
Setup Steps
-
In the form builder, add a section you want to control visibility for.
-
Click on Add Logic Rule.
-
Select a trigger question and define the condition (e.g., “If Question 1 = Yes”).
-
Choose the action:
a. Show this question or
b. Hide this question
-
Save the rule.

Example Use Cases
- Display “Upload Tax Document” only if the user selects “Yes” for “Do you have a tax ID?”
- Hide “International Address” fields when “Country = USA”.
- Show additional consent sections only for specific responses.
Notification and Due date reminder
Overview
Information Requests automatically manage reminders and notifications for both service providers and recipients. These alerts ensure deadlines are visible, forms are completed on time, and any changes are communicated instantly.
| Type | Trigger Event | Delivery Method |
|---|---|---|
| New Request Shared | When an Information Request is assigned | |
| Form Submitted | When recipient completes submission | |
| Due Date Change | When the project owner edits the due date | |
| Automatic Reminder | 1, 3, 5, and 10 days before due date | |
| Post-Due Date Reminder | Daily for up to 30 days after the due date | |
| Manual Reminder | Sent manually by project owner |
Delete Information Request
Overview
Deleting an Information Request permanently removes it and its responses from the project. Use this only for drafts, duplicates, or forms created in error — deleted requests cannot be recovered.
Who Can Delete
- Project Owners and Information Request Creators can delete requests.
- Collaborators or clients cannot delete or archive forms.
Steps to Delete
- Navigate to the project’s Information Requests tab.
- Locate the request you wish to remove.
- Click on the three-dot menu (⋯) beside the request name.
- Select Delete.
- Confirm the deletion in the pop-up dialog.
What Happens on Deletion
- The request and all responses are permanently removed from ShareFile.
- No notification is sent to participants upon deletion.
- Activity logs retain an entry noting that the request was deleted (for admin audit).
Best Practices
- If you may need to refer to past data, export responses before deleting.
- Use deletion sparingly — prefer Close for completed or inactive requests.
Export Responses
Overview
You can export all Information Request responses for offline review, analysis, or recordkeeping. Exports include metadata such as timestamps, respondent names, and all field-level answers.
Steps to Export Responses
- Navigate to the Information Requests tab in your project.
- Open the completed (or active) request.
- Select Export Responses -> CSV Format from the toolbar.
- Wait for the export to generate.
- Download the file to your local system.

Included in Export
- Request name and ID
- Field names (in order of appearance)
- Each respondent’s entries
- Submission timestamps
Notes:
- Export is available once at least one response has been submitted.
- CSV files can be opened in Excel, Sheets, or imported into analytics tools.
- Conditional logic affects exported columns — hidden or skipped questions appear as blank cells.
- If multiple versions of the form are active, each version is exported separately.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.