Solidgate Hub equips merchants with powerful tools for managing user roles and permissions, helping them maintain control over access to business data and operations.
Located in the account settings, the user management feature allows administrators to manage access across the Hub and help handle access and access issues. They can invite users and assign roles with predefined permissions to control what sections users can access and what actions they can take. Additionally, administrators can adjust roles and permissions as organizational needs evolve, reset passwords and two-factor authentication (2FA), and delete, block, or unblock users, ensuring security and control.
Roles and access
By assigning appropriate roles to team members, businesses can optimize operations, protect sensitive information, and ensure that each user has the necessary permissions to perform their job effectively. The role-based access in the Solidgate Hub offers a range of predefined roles, each created for specific functions and responsibilities. They can be combined, allowing users to hold multiple roles if needed:
- Merchant admin has the most comprehensive access, with permissions for all features, including payments, billing, risk management, account settings, user management, and more.
- Team lead has access similar to Merchant admin but with some limitations. For example, they cannot view analytics, modify products, or reset user passwords or 2FA. However, they can invite, delete, block, and unblock users.
- Manager has significant access to operational features like order management, subscriptions, and product details. However, they have more limited access to financial analytics and advanced settings.
- Analyst has access focused on analytical features, like payment analytics and risk analytics, and can view various operational details.
- Support tier 1, 2, and 3 roles have leveled access, with tier 3 having the most. For example, the Support tier 3 role can manage orders and subscriptions.
- Dispute support role includes Support tier 3 access, Alert manager rights, and control over the list of rejected and allowed transactions.
- Developer has specific access to technical features like API logs and channel details.
- Alert manager role is focused on alert-related features and some risk management aspects.
- Finance manager has access to financial features, reconciliation, and some analytical tools.
- Authorized signatory is a limited role with access primarily to legal entities, questionnaires, and document signing.
The detailed breakdown of permissions for each role can help you decide on the appropriate access levels for your team. This way you can ensure that each member has the rights they need to perform their tasks efficiently.
| Section | Merchant admin | Team lead | Manager | Analyst | Support tier 1 | Support tier 2 | Support tier 3 | Dispute support | Developer | Alert manager | Finance manager | Authorized signatory |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Home | ||||||||||||
| Dashboard | ✓ | - | - | ✓ | - | - | - | - | - | - | ✓ | - |
| Payments | ||||||||||||
| Orders | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | - | - | - |
| Order actions | ✓ | ✓ | ✓ | ✓ | - | - | ✓ | ✓ | - | - | - | - |
| Disputes | ✓ | - | - | - | - | ✓ | ✓ | ✓ | - | ✓ | - | - |
| APM dispute actions | ✓ | - | - | - | - | ✓ | ✓ | ✓ | - | - | - | - |
| Representment | ✓ | - | - | - | - | ✓ | ✓ | ✓ | - | - | - | - |
| Representment actions | ✓ | - | - | - | - | ✓ | ✓ | ✓ | - | - | - | - |
| Fraud notifications | ✓ | - | - | - | - | - | ✓ | ✓ | - | ✓ | - | - |
| Payment links | ✓ | - | - | - | - | - | - | - | - | - | - | - |
| Section analytics | ✓ | - | - | ✓ | - | - | - | - | - | - | ✓ | - |
| Billing | ||||||||||||
| Products | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | - | - | - |
| Product actions | ✓ | - | - | ✓ | - | - | - | - | - | - | - | - |
| Subscriptions | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | - | - | - |
| Subscription actions | ✓ | ✓ | ✓ | ✓ | - | ✓ | ✓ | ✓ | - | - | - | - |
| Coupons | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | - | - | - |
| Coupon actions | ✓ | ✓ | ✓ | ✓ | - | ✓ | ✓ | ✓ | - | - | - | - |
| Invoices | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | - | - | - |
| Section analytics | ✓ | - | - | ✓ | - | - | - | - | - | - | ✓ | - |
| Billing settings | ✓ | - | - | ✓ | - | - | - | - | - | - | - | - |
| Fraud prevention | ||||||||||||
| List | ✓ | - | - | ✓ | - | - | - | ✓ | - | - | - | - |
| List actions | ✓ | - | - | ✓ | - | - | - | ✓ | - | - | - | - |
| Antifraud list rules | ✓ | - | - | - | - | ✓ | ✓ | - | - | - | - | - |
| Rules | ✓ | - | - | ✓ | - | - | - | - | - | - | - | - |
| Alert list | ✓ | - | ✓ | - | - | ✓ | ✓ | - | - | ✓ | - | - |
| Finances | ||||||||||||
| Settlements | ✓ | - | - | - | - | - | - | - | - | - | ✓ | - |
| Monthly reports | ✓ | - | - | - | - | - | - | - | - | - | ✓ | - |
| Report actions | ✓ | - | - | - | - | - | - | - | - | - | ✓ | - |
| Developers | ||||||||||||
| Channels | ✓ | - | - | - | - | - | - | - | ✓ | - | - | - |
| Apple Pay domains | ✓ | - | - | - | - | - | - | - | ✓ | - | - | - |
| Apple Pay domain actions | ✓ | - | - | - | - | - | - | - | ✓ | - | - | - |
| API logs | ✓ | - | - | - | - | - | - | - | ✓ | - | - | - |
| Reports & Exports | ||||||||||||
| Reports | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | - | ✓ | - |
| Finance reports | ✓ | - | - | - | - | - | - | - | - | - | ✓ | - |
| Exports | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | - | ✓ | - |
| Taxes | ||||||||||||
| Locations | ✓ | - | - | - | - | - | - | - | - | - | ✓ | - |
| Location actions | ✓ | - | - | - | - | - | - | - | - | - | ✓ | - |
| Tax settings | ✓ | - | - | - | - | - | - | - | - | - | ✓ | - |
| Tax settings actions | ✓ | - | - | - | - | - | - | - | - | - | ✓ | - |
| Account settings | ||||||||||||
| Profile | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| User management | ✓ | ✓ | - | - | - | - | - | - | - | - | - | - |
| User invite | ✓ | ✓ | - | - | - | - | - | - | - | - | - | - |
| User reset access | ✓ | - | - | - | - | - | - | - | - | - | - | - |
| Agreements | - | - | - | - | - | - | - | - | - | - | - | ✓ |
| Questionnaires | ✓ | - | - | - | - | - | - | - | - | - | - | ✓ |
| Legal entities | ✓ | - | - | - | - | - | - | - | - | - | - | ✓ |
| Audit log | ✓ | - | - | - | - | - | - | - | - | - | - | - |
This approach to permission management provides customized access levels, ranging from full administrative rights to more specific and limited permissions based on roles. It ensures effective oversight and supports business operations while protecting sensitive data.
Audit log
Audit log records actions performed by users within Hub and provides a single source of truth for activity tracking. It captures who performed an action, what happened, where it occurred, and when, including data changes.
This supports security monitoring, analysis of user activity, and compliance requirements.
- Go to Account settings > Audit log.
- Find the required User in the list.
- Optionally, use filters to narrow the results.
- Click on Apply, and see the data update instantly.
Each audit log entry includes user role, user email, IP address, object ID, object type, action description, and timestamp. Logs become available within five seconds after an action, providing near-real-time visibility into activity.
Use the audit log to identify changes made to entities, track actions by role, review entity change history, and analyze login activity.
Handle access
Solidgate Hub applies several security measures to protect accounts, including role-based access management, automatic lockouts, mandatory two-factor authentication (2FA), and Google sign-in.
Account lockout
After multiple failed login attempts, the account locks automatically for 30 minutes.
To restore access:
- If you remember your password, wait 30 minutes for automatic unblock or ask a Team lead or Merchant admin to unblock the account in the User management section.
- If you have issues with your password or 2FA, ask a Team lead or Merchant admin to reset your password or 2FA in the User management section.
- If the standard methods do not work, contact us to restore account access.
2FA
2FA is required for all roles by default. To avoid sign-in issues, confirm that your authenticator app is set up correctly and that your device time is synchronized.
Common 2FA issues and solutions:
- Invalid verification codes
Verify that you are using the correct authenticator app and that your device time is set automatically. Turn on the automatic date and time in your device settings, then try again. - Lost or broken authenticator device
Ask the Merchant admin to reset 2FA. After the reset, set up 2FA again on your new device. - Moving 2FA to a new device
Ask the Merchant admin to reset 2FA, then complete the setup on the new device. - Errors during 2FA setup
First, ask the Merchant admin to reset 2FA, then try setting up 2FA again. If the issue continues, contact us to restore account access.
Google sign-in
Solidgate Hub supports Google sign-in to simplify the login process. You can sign in using your Google account instead of entering your email and password. To use this option, first link your Google account.
- Go to Profile > Personal.
- Click on Link your Google account.
- Follow the instructions to link your Google account.
Once linked, you can select Sign in with Google on the Hub sign-in page to access your account without entering credentials. If you lose access to your Google account, you can still sign in with your password or contact the Merchant admin to reset your Google sign-in.