> ## Documentation Index
> Fetch the complete documentation index at: https://help-empuls.xoxoday.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Complete admin walkthrough — all modules
> An end-to-end tour of the Compass admin console — users, data, connections, metrics, plans, approvals, reports, and dashboards.
Compass is a no-code commission automation and analytics platform. This walkthrough covers every admin module — from uploading user and sales data, through metrics and plans, to approvals, reports, and dashboards.
## Users
The **Users** section holds the full list of users in the account, with all user-level data.
Users can be imported by CSV or added manually. When importing, five columns are **mandatory**: name, email ID, supervisor, access role, and partner code. Admins can include any additional columns beyond these.
## Data and integrations
In **Data and integrations**, upload sales data via CSV or through built-in integrations (custom integrations are also supported). All uploaded data is browsable here.
A connection joins user data with sales data. Click **New connection** and pick a join type:
* **Left join** — all rows from the left table + matching rows from the right (union-like; most common)
* **Inner join** — only rows present in both tables
* **Full outer join** — all rows from both tables
Choose the fields to join on — for example, join **user table.partner\_code** with **sales data.partner\_code**. Joins can span multiple fields with `AND` / `OR` conditions, and a single connection can contain multiple chained joins.
Once created, view the consolidated table and the configuration behind it — a full view of user attributes alongside sales transactions.
## Metrics
Metrics are the rules and conditions used to calculate commissions. Give the metric a name, pick a type, and choose the underlying connection.
Use built-in mathematical functions on the fields exposed by the connection — for example, `SUM(achievement) / SUM(target)` to get a sales achievement percentage.
Metrics can reference other metrics. For example, define `Coke sales = SUM(invoice_value) WHERE brand = 'Coke'`, then reference it inside a higher-level metric. This lets you build nested and conditional logic step by step.
## Commission plans
Click **Create a plan**, choose a plan label, and pick **Milestone plan**. Milestone plans give out rewards in slabs based on KPI achievement.
Include everyone, or define user groups with conditions (for example, `designation = SDR`). Multiple user groups can be part of one plan.
Add milestones as slab conditions — for example, `Coke sales BETWEEN 20 AND 40`. Every user meeting the condition is placed in that milestone.
For each milestone, add a reward — either a fixed amount (like `1000`) or a dynamic expression (like `Coke sales × 0.5`). Apply a **cap** to bound dynamic rewards (for example, capped at `10000`). A milestone can carry multiple rewards.
Configure start date, end date, and **recurrence** (daily, weekly on a specific day, monthly, or custom). Recurring plans create scheduled copies through the end date.
Set a **display name** (what end users see), a **rewarding buffer time** (grace period between calculation and payout — for example, 10 days for admin edits), and the **transaction date** field from the connection.
Add a plan description and attach supporting files (PDF, PNG, JPEG) if needed. Toggle **Hidden plan** to run a plan without exposing it to end users, or **Cascading plan** to feed this plan's output into another (useful for rolling monthly plans into quarterly or yearly ones).
Choose from built-in plan themes or upload logos and imagery to create a custom theme.
Add per-metric targets that show up on the end user's mobile and web app. Under **Metrics to display**, choose which task and reward metrics — and how much detail — end users see.
Use **Threshold for metrics** to bump users close to a target into a milestone — for example, promote users at 80–90% achievement into the next tier.
An estimator lets end users forecast commissions on pipeline deals. Define the input fields they can adjust (like Coke sales) and map them to metrics so the estimator can compute earnings.
Once configured, click **Activate** to publish.
## Plan labels and approval workflows
Every plan belongs to a **plan label**. Plan labels carry the approval permissions for three stages: rewards, plan report, and plan configuration.
Choose whether rewards are given out automatically or after approval. If approval is required, pick approvers — for example, **supervisor level 1** routes to each user's first-level supervisor, or a specific person / distribution list routes centrally.
Repeat the same setup for the plan report and the plan configuration — deciding who signs off before a plan can go live and before its report is considered final.
## Approvals
The **Plan approvals** page shows pending plan approvals, plus counts of active-approved and rejected plans.
Under **Approvals pending**, select individual or all incentives and approve or reject with a reason.
Under **Performance validation**, review pending plan reports — checking that metrics, achievements, and rewards are calculated correctly. Approve, reject, or view plan details (approver list, prior comments).
In the **Approved** section, view earnings, approved amount, payout, and balance per user. Use **Override adjustment** to add or subtract a value with a reason if needed.
## Reports and logs
Reports cover: **Overview** (logins, redemption trends, points awarded, available balance), **Login** (user activity times), **User access** (first activity of the day + web vs. mobile), **Payout** (per-user earnings and payouts for a period), and **Consolidated user performance** (a user's plans, earnings, KPI values, and transactions across time).
Logs track CSV uploads (which rows were accepted vs. skipped and why), plan processing, metric edits, and the processing queue — giving visibility into how much data is being processed and where.
## Groups and escalations
Create a **Town hall** (public group with everyone included) or **closed groups**. For private groups, admins approve who joins. Post announcements — users can react, share, or interact.
Escalations surface user-raised issues — for example, discrepancies in commissions or missing achievements. Investigate and respond, then close the ticket.
## Dashboards
The account dashboard summarises everything running in the account. Switch the time frame (week, month, quarter, year) — all widgets update accordingly. See user access, pending escalations, payouts to approve, user groups, approved and pending earnings, and configurable performance reports.
Add widgets for **plan-vs-plan comparison** (compare metrics like Coke sales vs. Thumbs Up sales across plans to gauge ROI), **plan payout trends** (how much has been paid out and when), and any performance reports you want at the top.
From a plan (or from the account dashboard), click **View dashboard** to open its plan dashboard. See **milestone performance** (participants in each milestone) and the plan's single source of truth for achievements and payouts.
Compare performance reports between plans, or upload a CSV to validate that Compass calculations match your own systems.
Add a leaderboard widget: name it, select up to three metrics as ranking criteria, choose ranking direction, group by any user-data field, control visibility (managers or specific participants), and optionally award ranks or rank-ranges with fixed or dynamic rewards (with caps).
Add comparison reports (for example, aggregate Coke vs. Thumbs Up sales grouped by a user attribute), line graphs, bar charts, and tables — each configurable by metric and user field.
## Settings
See the details you provided at sign-up.
Under **Branding and customisation**, set the Compass logo, background, and theme colours. The interface reflects the changes throughout the app.
Define the reward types available on the account — points, scores, or badges.
Share knowledge or reference files. Make repositories public for all users or private for specific users, and map attachments to individual users where relevant.