Activities overview
Start here to understand what Activities solves, how its modules connect, and why the product matters inside the broader operating model.
Prerequisites
Before using this guide, make sure the user has access to the module and the initial portal setup is consistent.
1. Process introduction
Activities structures execution, task coordination, deliverables, and follow-up so teams can operate with clearer responsibility and progress visibility.
Activities should be understood as a connected product, not as isolated apps. Its modules work better when users read them as part of a shared operating sequence.
2. Shared foundation
Before entering the business flow, these shared modules usually define the operating context: Companies, Areas, Projects, Activity Types.
3. Business flow modules
The business flow of Activities is organized around these modules: Activities, Deliverable Types, Deliverables, Deliverable Trackings, Email Address Mappings, Email Thread Mappings, Reports.
Use the manuals that follow this introduction in order to understand the logic of the product before going into individual operations.
You may also be interested in
PIC to connect business partners
Connect task execution with customers, suppliers, and external participants.
FIS to connect execution with control
Link projects and deliverables to a clearer view of financial impact.
IA Core for quick answers
Accelerate adoption with rapid answers about modules, processes, and decisions.
Previous
-
Next
Companies manual