Core Concepts

To get the most out of your MeritFlow dashboard, it helps to understand how data is nested, organized, and scored.

1. Organizations (Tenants)

The top-level workspace representing a company (e.g., acme-corp). Every organization holds:

• Billing and subscription information.
• Global API integrations (Jira, Bitbucket access tokens).
• The organization-specific Merit Formula used to calculate scores.

2. Teams (Squads)

Sub-groups within an organization. Teams allow engineering managers to compare velocity and output across different product squads (e.g., "Frontend Platform", "Backend Checkout"). A member can belong to multiple teams if they split their time across different domains.

3. Members

The actual users on the platform. Members can be developers, engineering managers, or executives. Each member has:

• A platform profile (bio, role, avatar).
• Linked Accounts, mapping their MeritFlow account to their specific external UIDs (e.g., mapping a user to Jira ID 5f9d2...).
• Team memberships.

4. Contributions (Merit Events)

The atomic units of tracked work. Examples include:

• A Jira ticket transitioned to "Done".
• A Pull Request merged in Bitbucket.
• Resolving a critical production incident.
• Closing a difficult Epic.

Each contribution is automatically tied to a specific Member via their Linked Accounts, and is scored according to the Organization's merit formula before being saved on the permanent leaderboard.