Skip to main content
All CollectionsNotabene DashboardAccount ManagementMembers
Group Admin FAQ
Group Admin FAQ
Emanuel Clodeanu avatar
Written by Emanuel Clodeanu
Updated over 8 months ago

  1. What is the difference between an Admin and a Group Admin

    A Group Admin enjoys broader control, overseeing all jurisdictions within their Group VASP. They possess the ability to modify the group structure, upgrade/downgrade packages, access billing details, and manage invoices. On the other hand, Regular Admins have jurisdiction-specific access, lacking control over the entire group.
    ​

  2. What is a Group VASP?

    A Group VASP is composed of multiple VASPs operating in different jurisdictions, all nested under a single parent entity known as the gateway VASP.

  3. If my package allows for only one jurisdiction, what happens with other VASPs in the group?

    While your package may limit you to a single jurisdiction, you are still allowed to create travel rule transfers in additional jurisdictions. However, since they will operate under SafeTransact-Rise conditions, they will have no API access and a transfer limit of $10,000. To operate in more jurisdictions with full capacity, you'll need to upgrade your package.

  4. What is the maximum number of Group Admins appointed to a Group VASP?
    You can appoint multiple Group Admins according to your organizational needs. However, we advise being stringent with permissions, as they can significantly impact the organization.
    ​

  5. Who can appoint a Group Admin?
    Any existing Group Admin has the authority to appoint other Group Admins within the system. Additionally, they possess the capability to revoke these appointments if the need arises at a later stage.
    ​

  6. Does a Group Admin have the capability to perform nesting?

    Certainly, Group Admins have the ability to execute nesting operations within the jurisdictions assigned to them.
    ​

  7. Who will be able to see if nesting opportunities arise?
    All members of a VASP will be able to notice there are other existing VASPs with the same domain. However, only Group Admins will be able to perform the nesting.
    ​

  8. Why is nesting important?

    Nesting establishes a cohesive structure for organizing entities, facilitating efficient compliance management and enhances visibility in jurisdictional management. It substantially reduces end-customer confusion, as post-nesting, they will only encounter one VASP name.

  9. How do I manage complex jurisdictional structure where certain VASPs operate independently?

    In complex structures, Group Admins can oversee only the jurisdictions assigned to them. If VASPs operate independently, their administrative control is confined to their specific jurisdiction. This ensures that decisions are made autonomously in distinct operational centers.
    ​

  10. Why are my transfers currently stuck, and how can the issue be resolved?

    By default, a transfer will be directed to the parent VASP. To address this, you should implement a systematic redirect setup to the appropriate jurisdiction VASP.

  11. How can I setup proper redirect?

    You can upload a list of wallet addresses for each subsidiary VASP or implement our address webhook. Please note that these methods are exclusively available for paid jurisdictions.
    ​

  12. How can I redirect transfers if I don't have a paying license.
    You have the ability to redirect travel rule transfers manually by selecting the addresses and specifying the respective jurisdiction VASPs using our user interface (UI).
    ​

Did this answer your question?