Marco Service Platform
Overview
The Marco Service Platform or simply Marco, powered by Marco OS, is a robust and customizable system designed to manage payroll, HR, and other operational functions. It supports a multi-layered data structure that ensures seamless collaboration between vendors, their customers, and staff users. This document explains the key data components within the platform and their roles.
Data Structure in the Platform
The Marco Service Platform is built around four key data categories:
1. Platform Data
Definition: Platform Data refers to the core technical and operational information that drives the functionality of the Marco Service Platform.
Includes:
System-wide settings and configurations.
Platform-wide activity logs.
Application versioning and updates.
Purpose:
To maintain the stability and efficiency of the system.
To support the customization and branding required for white-labeled vendor platforms.
2. Customer Data
Definition: Customer Data represents the information specific to the companies (customers) using the platform.
Includes:
Company profiles (e.g., name, address, and registration details).
Employee records (e.g., staff profiles, payroll details, and timesheets).
Company-specific configurations (e.g., payroll schedules, leave policies).
Purpose:
To enable companies to manage their operations effectively.
To ensure accurate payroll processing and HR management.
3. Partner Vendor Data
Definition: Partner Vendor Data pertains to the information related to vendors who manage the customers on the platform.
Includes:
Vendor profiles (e.g., organization name, contact details).
Vendor-specific settings and configurations.
Assigned customer data (e.g., list of companies under a vendor's management).
Purpose:
To empower vendors to manage their assigned customers efficiently.
To ensure accountability and visibility across vendor activities.
4. Vendor User Data
Definition: Vendor User Data focuses on the individual users within a vendor organization who interact with the platform.
Includes:
User profiles (e.g., name, email, and role such as Vendor Admin or Vendor User).
Permissions and access levels.
Activity logs (e.g., customer management actions, changes made to platform configurations).
Purpose:
To enable vendor users to perform their specific roles effectively.
To track and log activities for audit and transparency.
How Data Interacts Across Roles
Vendor Admin
Access: Full access to all customer data and vendor-specific settings.
Actions:
Create and manage customer accounts.
Configure platform settings for all customers under their management.
Assign Vendor Users to specific customers.
Vendor User
Access: Restricted to assigned customers.
Actions:
Manage payroll and HR operations for their assigned companies.
Provide support to staff users within those companies.
Staff Users (Manager/Worker)
Access: Limited to their company's data.
Actions:
Managers: Approve payroll, manage employee data, and oversee team operations.
Workers: Access personal information, submit timesheets, and view payroll details.
Why This Structure Matters
Scalability: The structured data model ensures the platform can grow with the needs of vendors and customers.
Security: Role-based access controls protect sensitive data and prevent unauthorized access.
Efficiency: Clear data boundaries streamline operations and improve usability for all roles.
Last updated