Live Search | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Info |
---|
Tip |
---|
Note |
---|
Campaign | A campaign is a repeatable group of modules or stand-alone tasks, that is designed to achieve one or more objectives. They may be ordered or unordered. |
---|---|
Campaign Types | Individual: best suited for reporting and managing activities of individual users. Enterprise: best suited for reporting and managing groups of users. Entity: best suited for enabling a single user to initiate multiple iterations of the same campaign. |
Ordered vs Unordered | Ordered campaigns require completion of modules in a linear sequence. Ordered modules require completion of tasks in a linear sequence. When a campaign is configured as ordered, the modules and their tasks are treated as ordered by default, unless the modules are changed to ordered. |
Campaign, Module, or Task Statuses | Overdue – Uncompleted and current date is past the Due Date At Risk – Uncompleted and current date is 2 days or less prior to the Due Date On Track - Uncompleted and more than 2 days prior to the Due Date Completed – All tasks are completed and approved |
Campaign Builder | The Rivet work area for designing, editing, and publishing campaigns. |
Inbox | The Rivet work area for completing assigned tasks. |
Task | A piece of work to complete. Examples include forms, videos, file downloads, file uploads, and quizzes. |
Module | A logical grouping of tasks based on task attributes or relationships. Modules may be ordered (tasks completed in order) or unordered. |
Rivet Board | The Rivet main dashboard used to manage and research user, group, and company activities in campaigns, modules, and tasks. The Rivet Board communicates the status of completion of campaigns, modules, and tasks, and by whom the tasks were completed and approved. |
User | A User is a subscriber to one or more Rivet accounts. Users may be one of four roles, based on types of access needed. |
User Roles | |
Groups | A Group is a logical set of internal users within an account, for example Supply Chain. Groups may contain Subgroups, for example Distribution Centers as a subgroup within the Supply Chain group. Users may be assigned to one or more groups and one or more subgroups within groups. Users do not need to be assigned to a group in order to be assigned to subgroups within that group. |
Companies | A Company is a logical set of external users within an account, for example a Vendor. Companies may contain Departments, for example Compliance as a department within a Vendor company. Users may be assigned to one or more companies and one or more departments within companies. Users do not need to be assigned to a company in order to be assigned to departments within that company. |
Tags | Tags are attributes assigned to groups or companies to create logical sets of groups or companies. Tags may be used to assign groups or companies to campaigns. |
Rules | A rule is a condition-based event that responds to a condition by triggering an action, such as an assignment or sending a report. |
PII | |
Assignment | An assignment is the appointment of a user, group, or company to complete one or more tasks or approvals, or to act as on observer to a campaign. |
Approvals | |
Notifications | |
Form Task | |
Upload Task | |
Download Task | |
Video Task | |
Quiz Task | |
Assignment | |
Observer |
Related Labels
Expand | ||
---|---|---|
| ||
|
Popular Labels
Popular Labels | ||||||
---|---|---|---|---|---|---|
|