# Roles and accesses The service has a hierarchy of three roles, each with its own features and level of access: 1. **Owner**\ A team founder with maximum rights. * Owner creates a team in the service and is a super-administrator with access to all functions and sections of the personal account 2. **Team Lead**\ Manager with full access to service functions within their assigned accounts. * Team leaders can only be appointed by the owner, giving them authority to deal with certain accounts and team members команды 3. **Member**\ A regular user with limited access. * Members can only access the accounts and actions related to their management {% hint style="info" %} Let's break down the accesses and limitations of each individual role in detail below. {% endhint %} *** ## **1) Owner** Team founder and super-admin. * **Role Features**: * Creates a team in the service * Has full access to all accounts, cards, users and activities in personal account * The only one who can appoint teamsters * **Accesses**: * Full access to all accounts, cards and users * Ability to appoint team leaders / memebers and delegate account access to them * Management of all service functions ## **2) Team Lead** A manager appointed by the owner. * **Role Features**: * Has full access to the service features, but only within the accounts available to him or her * Can interact with team members and manage their accesses * **Accesses**: * I**nviting new members to the team** * **Assignment of accounts to members** (within the limits available to the team leader) * **Creating new accounts** * **Card Management**: * Card issuance * Freezing and thawing of cards * Closing cards * **Card Limits**: * Setting limits when creating a card and afterwards * Editing the limits set by the owner is not available * **Financial Transactions**: * Replenishment of accounts * Funds transfers between available accounts * **User Management**: * Locking and unlocking of membranes * Locking and unlocking owner or other teamleads is not available * **METAPAY and 3DS Codes**: * Access to METAPAY and 3DS codes on available accounts * Enabling and disabling 3DS on cards * **Reports and Accesses**: * Access to transactions on available accounts * Downloading tables with data to Excel * Visibility into which members and teamleads have access to specific accounts and cards *** ## **3) Member** A normal user who has access only to the accounts assigned to him and working actions with them. * **Accesses**: * **Card Management**: * Card issuance * Freezing and thawing of cards * Closing cards * **METAPAY and 3DS Codes**: * Access to METAPAY and 3DS codes on available accounts * Enabling and disabling 3DS on cards * **Card Limits**: * Setting limits when creating a card and afterwards * Editing limits set by the ovner or teamleader is not available * **Reports and Accesses**: * Access to transactions on your accounts * Downloading tables with data to Excel * **Restrictions**: * Deposit and transfer functions between accounts are not available * The Balance history section is hidden * The Team management section is hidden * No access to information about who else has access to accounts and cards * It is not possible to issue new invoices * It is not possible to change account names *** ## **4)** Role comparison | Section | A**ccess/Function** | **Owner** | **Team Lead** | **Member** | | ------------------- | --------------------------------- | ----------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------- | | **Dashboard** | Summary visibility | Yes | Yes | Yes | | **Accounts** | Access to all accounts | Yes | No (appointed only) | No (appointed only) | | | Issuance of new accounts | Yes | Yes | No | | | Transfers between accounts | Yes | Yes | No | | | Changing account names | Yes | Yes | No | | | Visibility of other users' access | Yes | Yes | No | | **Team management** | Adding Team Lead | Yes | No | No | | | Adding Member | Yes | Yes | No | | | Locking and unlocking users | Yes | Yes (members only) | No | | | View all users of the team | Yes | Yes | No | | **Cards** | Card issuance | Yes | Yes | Yes | | | Freezing and thawing of cards | Yes | Yes | Yes | | | Closing cards | Yes | Yes | Yes | | | Changing card limits | Yes | Yes (if the owner has not previously set a limit) | Yes (if the owner or teamlead has not previously set a limit) | | | 3DS control of the cards | Yes | Yes | Yes | | **Payments** | Viewing payments | Yes | Yes (on available accounts) | Yes (on available accounts) | | **METAPAY & 3DS** | View codes | Yes | Yes (on available accounts) | Yes (on available accounts) | | **Profile** | Profile settings | Yes | Yes | Yes | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fbm-pay.com/eng/team/roles-and-accesses.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.