If you're new to Clustdoc, you may want to learn about these terms to get up to speed with the platform in no time.
|The blueprint of your routine workflow: Your process checklist is listing all tasks and steps that must be executed every time you launch an onboarding with a new person.
|The resources section gathers everything you need to get started with Clustdoc. For example, that's where you're going to map out repeatable onboarding processes that your team would later use with your business contacts.
An application is an executed version of your draft process.
Using an application involves a real end-user while your process would be your wireframe.
Based on your industry or your business needs, an application could also refer to a project, a program, a client record.
A Business user is someone who needs to access your company account or admin console to manage incoming applications.
Business users include team members and external members.
|Client or End-user or Stakeholder
|These are the people who are joining your workflows.
|The portal, client portal or onboarding portal is a public access link from where anyone can start your process.
|A form in Clustdoc is the HTML form which you can build from scratch and list as one of the steps of your process.
An e-contract is a digital document which you can get signed as part of your process.
If you don't use a signature on your e-contracts they would just be what we call e-documents :)
|The checklist is the specific section of your process where you'll list onboarding steps and tasks are listed.
|Conditional display rules allow you to dynamically show your checklist steps to end-users based on criterias you can define upfront.
|Merge fields allow you to prepopulate data onto various parts of your checklist, forms or e-contracts automatically.
|Logic jumps specifically refer to Clustdoc forms. It allows you to hide/show specific fields based on previous answers captured in your forms.
|The toolbox is the place where you can save your forms, contracts, spreadsheets as templates. This way, they can be used across all processes you want and can be managed or edited from a single place.
|A custom stage allows you to define milestones associated with your process completion. It can be internal or visible by end-users.