> ## Documentation Index > Fetch the complete documentation index at: https://docs.eosb.org/llms.txt > Use this file to discover all available pages before exploring further. # Roles and responsibilities > Who does what on the EOSB platform, who approves it, and who can see it. Every person who signs in has **one role**, tied to **one organisation**. The role decides which workspace you see and what you can do there. The organisation decides whose records you see: an employer user sees only their own employer, a trustee only the trusts it holds, and so on. ## The roles **Organisation:** EOSB, the platform operator. **Responsible for:** registering employers, trustees and fund managers; setting up and activating employers; approving changes to employee salary, start date and payment details; paying out approved benefits; user accounts; benchmarks; payment service providers. **Can also:** do anything an employer does with employees or funding, on their behalf; decide fund manager budgets; record verification decisions when MELSS asks. **Cannot:** confirm employer funding, approve a benefit payment, or move trust money to or from the fund manager. Those belong to the trustee. **Organisation:** MELSS. **Responsible for:** verifying every employer, trustee and fund manager before it can take part. **Sees:** every active employer's monthly accruals, computation exceptions and transaction ledger. These views are read-only. **Cannot:** change records or move money. **Organisation:** one employer. **Responsible for:** registering employees and keeping their records accurate; terminating leavers; paying into the trust and submitting proof; approving or rejecting fund manager budgets for its trust. **Sees:** its own employees, liability ledger, trust, funding history and the trust's portfolio (read-only). **Cannot:** change salary, start date or payment details without approval; see other employers. **Organisation:** one trustee, holding one or more trusts. **Responsible for:** confirming employer payments; approving or rejecting leavers' benefit payments; logging transfers to the fund manager; approving recognitions that differ from what was sent; confirming money returned; approving expenses above SLE 100,000; deciding budgets. **Sees:** the trusts it holds, their portfolios, allocation and returns. **Cannot:** pay a benefit out (the administrator does that), or post expenses and buy assets (the fund manager does). **Organisation:** one fund manager, managing one or more trusts. **Responsible for:** recognising cash from the trustee; setting up portfolio frameworks; buying assets and recording income, valuations and write-offs; proposing budgets and posting expenses; returning money to the trust; month-end snapshots and reconciliation. **Cannot:** spend without an approved budget, spend above SLE 100,000 without the trustee, or use one trust's cash for another. **Organisation:** their employer. Employees are told by SMS and email when they are registered, and their benefit is paid to their payout account or SmartPay wallet. An employee portal is planned; employees do not sign in yet. Reserved for a custodian of trust assets. The role exists and accounts can be created, but the custodian workspace is planned and has no functions yet. ## Who does what **D** = does it · **A** = approves or confirms it · **V** = can view it · — = no part. ### Onboarding | Action | Admin | Regulator | Employer | Trustee | Fund manager | | - | - | - | - | - | - | | Register an employer | D | V | — | — | — | | Verify an employer | (on request) | **A** | — | — | — | | Register a trustee or fund manager | D | V | — | — | — | | Verify a trustee or fund manager | (on request) | **A** | — | — | — | | Create the trust, appoint providers, confirm bank account | D | — | V | V | V | | Activate the employer | D | — | V | — | — | | Create user accounts | D | — | — | — | — | ### Employees | Action | Admin | Regulator | Employer | Trustee | Fund manager | | - | - | - | - | - | - | | Register or bulk-upload employees | D | — | D | — | — | | Change contact details, job title, location | D | — | D | — | — | | Change salary, start date or payment details | **A** | — | D | — | — | | Terminate an employee | D | — | D | — | — | | Approve the final settlement | — | — | — | **A** | — | | Pay the benefit out | D | — | — | — | — | ### Money | Action | Admin | Regulator | Employer | Trustee | Fund manager | | - | - | - | - | - | - | | Pay into the trust (manual proof) | D (on behalf) | — | D | **A** | — | | Pay into the trust (wallet) | D (on behalf) | — | D | — | — | | Send money to the fund manager | — | — | — | D | — | | Recognise money received | — | — | — | A (if different) | D | | Return money to the trust | — | — | — | **A** | D | | Propose an expense budget | — | — | — | — | D | | Approve an expense budget | A | — | **A** | **A** | — | | Post an expense up to SLE 100,000 | — | — | — | V | D | | Post an expense above SLE 100,000 | — | — | — | **A** | D | For a budget, any one of the approvers settles it: whoever decides first. ### Investments and oversight | Action | Admin | Regulator | Employer | Trustee | Fund manager | | - | - | - | - | - | - | | Create and activate a portfolio framework | — | — | — | — | D | | Buy assets, record income and valuations, write off | — | — | — | — | D | | Asset register, allocation variance, ROI | — | — | V | V | D | | Maintain and assign benchmarks | D | — | — | — | V | | Monthly accrual | runs automatically; admin can rerun | V | V (in ledger) | — | — | | Computation exceptions | D (fixes data) | V | — | — | — | | Liability ledger | — | V (all employers) | V (own) | — | — | ## One person, one role A person who works for two organisations, or needs two roles, needs two accounts. Your role and organisation are shown in **Settings › Access**. To change them, ask the platform administrator. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.