Advanced Account Settings

Today, we're gonna look into the tab called Global settings under Dashboard => Integrations => Global settings. These settings are applicable for the entire account, as I mentioned, and they also cover some really cool features like duplicates, tags, specifying documents per specific country, etc. And we're gonna look into one of them in detail.

Starting from the general settings. Here on the applicant settings, the most important in my opinion, is specifying the support email. As you can see, we already specified the support email for us. What it means is that it allows users to contact our support in case they have questions, didn’t fully go through the verification flow, or have any additional questions.If we don’t have a support email address, what do we do then? That’s a good question. Here you can see a quick visual presentation. On the left-hand side, you see the message that an applicant will see in your verification step, in your app, or on your web, when they’re trying to pass the verification flow. If they don’t have a support email, it will just say: We couldn’t verify your profile. Please contact the company you’re verifying with. And if you have a support email mentioned, they will see a message on the right-hand side, highlighted in green: We couldn’t verify your profile. If you have any questions, contact the company you are verifying with — and then the support email. So this is how it looks in two different cases — for the company and for the users. OK, it sounds like having an email address here is rather important, as my users may contact me and provide some additional documentation needed for verification, correct? Correct. They can contact you and give some additional information or more details. Another good setting here is the file upload size. Here you can choose the minimum or maximum size of the upload file. There’s really no strict limit on how many megabytes you want to support. Obviously, the bigger the file, the better the resolution or image. It’s a general setting, and it depends on what is permissible for you. The next setting here is called applicant tags. Can you guess what tags are? It’s a tricky question. I guess it’s to separate something from something, or mark something? Correct, you’re spot on. Here’s the list of some tags that are already pre-created for this account. You can also create a tag at any stage. Essentially, tags are used for reporting or to visually separate applicants when reviewing them, for example, to highlight high-risk versus low-risk. They are visible on the applicant page, like this. Tags can mean anything, and they can be applied manually to each applicant, or you can create a workflow to apply tags automatically under certain conditions. We’ll talk more about workflows in our next session.

The next step is user verification. This is a pretty important setting, and here are a few key things. The first one is applicant’s age. Here it’s set from 21 years old to 110 years. Do you have any restrictions for age? We actually don’t have any restrictions on age — it’s a very friendly company — but I understand correctly that you would need it, for example, if you were an app selling alcohol. Then you’d have to set the restriction not under 21 years old. Correct. If you want to only accept applicants of legal adult age, you would need to set it to 21. But since the company is super friendly, we’ll put it back to 18–110. The next important setting is duplicates. Are you accepting any duplicates in the account? When you say duplicates, do you mean people who have the same address and are trying to create multiple accounts? You’re correct. By default, the system doesn’t allow duplicates — we don’t support multiple accounts. So if you don’t want the same person creating multiple accounts, you don’t need to make any changes. But in case you want to allow applicants to create multiple accounts, you can simply select Allow duplicates. Oh, just clarifying: by default no duplicates, but I can adjust this in settings? Correct. You can either allow all duplicates or allow duplicates under specific conditions, for example, with different email addresses. But by default, duplicates are not accepted. There are a few additional settings here that are also important. ID document expiry settings. Honestly, I feel like these were created during the COVID times. You have a few options: respect the actual validity period of the document, or accept expired documents if permissible by local regulations. By default, expired documents permissible by local regulations are accepted. But you can also choose to respect the actual validity period. Another setting is the minimal residual validity of ID documents. You can choose to accept documents while they are valid, or require that they remain valid for at least 3 months, depending on compliance preferences. It’s best to confirm this with your compliance officers. The most common setting is simply to accept ID documents while they are valid, but again, it depends on regulations. Once you make the changes and you’re ready, press Save changes. Then we move on to additional settings in this tab. The next one is proof of address. We’ll cover this in one of our next webinars. Ongoing document monitoring: this refers to periodic checks of whether documents are still valid. If enabled, users will be prompted to re-verify when documents expire. The last important setting here is supported ID documents. This is pretty cool because you can select which documents you support per country. For example, if we select France to accept only passports, it would mean that French applicants could submit only a passport, and not an ID card, driver’s license, or residence permit. We saw something similar before, right? Yes — at the verification level. The difference is that verification level settings apply only to that specific level, while global settings apply to the entire account. If you press Edit, you can also choose which fields are extracted from the documents, and even add extra fields, like place of birth, depending on compliance requirements. Once you’re ready, press Apply, and the changes are saved.

We finished with the global settings. I just want to quickly walk you through all of the additional tabs that are available here and that you can select. So, Business verification — those are additional settings that are possible to apply for our KYB solution, Know Your Business, and they are set up here. Payment method checks — these are the settings to verify users' payment methods. AML screening — there are a bunch of different settings under AML screening, and I usually recommend keeping it as is, without making any changes. But obviously it depends on your compliance officers and your regulations. For example, you can choose that for warning types, sanctions from OFAC should not trigger. But again, as I said, generally we recommend keeping it as is, unless there are specific requirements from your compliance officers. Another thing possible to set up here is ongoing AML monitoring. This essentially refers to applicants changing their status and constantly reviewing if the applicant’s status has changed or not. For example, right now I’m just a normal person, I’m Nasta and I’m a normal human. But in a couple of months, hopefully, I’ll become President of the United States. In this world, anything can happen. Then, if I have this enabled, with auto-screening for AML, I’ll be triggered by the system automatically. If I don’t have it enabled, then I’m not triggered. Next one is Data comparison. This essentially allows you to confirm how the system compares applicant data, especially names and addresses, to detect mismatches and inconsistencies. Usually by default it is set to fuzzy. What I mean is, for example, my name is Nasta, but also Nastaa would be triggered because it is set to fuzzy. But you can also select strict name. All right, moving on. We have a Customization tab, which we covered last time. SDK translation tab — that’s pretty cool. Do you remember last time when we discussed that it’s possible to set up the language of the verification flow? So this is how the verification flow currently looks like, and we mentioned that we can make changes to this language, remember? Yeah, absolutely. So this is what you can do in the SDK translation. For any language, for example English, you can find the place where you want to make changes, for example address, just make the change, save changes, and here you can customize the SDK language to meet your brand requirements and brand language. It’s a pretty powerful feature. All right, moving on. Client lists — these are applicable to the workflow builder, which we will cover in one of our next webinars. Database product — it refers to our non-document verification products. Questionnaire — another pretty cool setting. This is especially useful for FinTech. You can see I was testing it yesterday as well. This product allows you to ask predefined questions before, after, or during the verification flow. For example: Have you ever opened any brokerage account for trading? If we were to try and do so, how would you recommend approaching it? Yeah, it’s very common, for example in trading, to ask questions like How familiar are you with trading? And these questions are recorded. This is something you can set up here. We’re gonna look into this in one of our next webinars, so I’ll skip it for now. And last but not least, Payment methods. Can you guess what it does? Confirm ownership of payment methods like bank cards or crypto wallets, and I assume prevent fraudulent activities or suspicious transactions? Oh my God, you’re spot on. That’s exactly what it does. So that’s what confirming the payment method is, and you can set it up here as well. I’m not gonna look into it today, but it’s upcoming in one of our webinars as well. All right, so we’re done with the settings, or is there any more to run through? We’re done with the settings. This is all available here. As you can see, there’s a lot of customization. Sumsub is really customizable and you can make it as unique as possible.

We're ready to move on to the roles. If I remember correctly, you wanted to set up a specific role, right? Yeah, I would like to create a custom role for a person who will only have access to the analytics in our account. Would you be able to walk us through that, please? Let's do it now, but before we jump into showing you how to create a specific role, let me quickly show you a short video overview of how roles in general work and what is possible within them. Welcome to Sumsub, where managing your team's access and responsibilities is seamless and efficient. Let's talk about user roles and how they can empower your team. Roles help you restrict access to certain dashboard functionality. You can create as many roles as you need. Each role has a set of permissions. Each permission regulates how your team members can use the dashboard. With Sumsub, you receive the following default roles: Admin – This user has full access to all functionality and statistics. They can set up rules and customize verification processes. Compliance Officer – This user can review applicant profiles, approve or decline applicants, and upload additional documents. Developer – This user can set up rules and customize verification processes. Permissions cannot be assigned directly to team members. Instead, you must create a role with the desired permissions and then assign the role to a team member. From time to time, we improve our product by adding new permissions. All newly created permissions can be found in the documentation portal. If you do not see some of the listed permissions, it likely means you do not have access to the corresponding Sumsub products or solutions. To obtain a new product, please contact our sales team or reach out to your account manager. To create a new role, simply go to the dashboard, select the Roles page, and click Add New Role. Provide the role name and an optional description. From the “Start from a copy of” drop-down list, select an existing role from which you want to inherit permissions. Although it is not necessary to set any access limitations or IP restrictions, you have the option to enable them if needed. Source keys are available only if they are included in the client's configuration. If no source key is selected, the user role will have unrestricted access to all source keys. On the right, select the permissions you want to grant to the role. Make sure to thoroughly examine each permission and its description before selecting it. Click Create Role to complete the process. Edit roles allows you to modify an existing role to update specific parameters. For example, you can change previously assigned permissions, rename the role, or make other adjustments as needed. Remove roles allows you to permanently delete a role if it is no longer required. However, keep in mind that a role cannot be removed if at least one team member is currently assigned to it. And that's it. Now you know how to create new roles and manage them. Amazing. That was a really cool video. I just want to quickly remind you that all of these videos and other help can be found in our Help Center, especially in Ask our AI. It's much cooler to ask her questions, and I find it easier to get answers than just typing. All sorts of videos are available here as well on different pages. Alright, so coming back to our demo, let's go into creating the specific role. Give me a second… Settings and Roles. Here we already have defined roles, and we want to create a new role. It's Analytics, right? Yes, please. Here we can choose if the role will mirror already predefined roles, but in our case, we just want to create a brand new role, so we keep it blank. For the description, we’ll say Analytics view only. On the left-hand side, you can see the access limitations for the role. There are a bunch of different limitations, and since our role should be read-only and not make any changes to the account, we will select Enable Read-Only Mode. On the right-hand side, you can select exactly what this role will view or have access to. In our case, it’s analytics. So in the search bar, we type analytics. It gives a suggestion: See Statistics and Analytics. Since that’s what we want, we select it. This role will only see these reports. And that’s it. We press Create Role. The role is created, and now we want to assign members. We go to Members with the Role and invite a new team member to the role. Alright, so that’s about roles.

So in general we have two billing types. One is called self-service billing, and that usually supports credit card payment. But it is limited in the number of services available, and has no prepayment requirement. The other form of billing we have is deposit billing. We support bank payments, we require prepayment, and a higher number of services is provided, as well as help with integration usually included as well. Let’s look into this in more detail. The first — deposit billing. This is how the deposit billing page usually looks. On the right-hand side, at the top, you will see the balance — how much money is left from the prepayment you made. Essentially it works like this: you make a prepayment, and then every month based on your usage, the money is subtracted. So here you can see on the balance how much money is still left. Then you can see the reporting period on the left side — for example, February to February. I just want to highlight that if you are looking at the reporting for the current month, it will be continuously changing and the data is not 100% correct. But if you’re looking at the reporting of the past month, the data is 100% correct and finalized. Moving on. On the right you see Export invoice and Export report. Here you can export invoices, as the name suggests, and export reports. At the bottom you will see the total for the month, with taxes, etc. The next step available is Service usage, and that’s just a graphical view of what was shown on this page. Here you can see the type of services and the quantity used, and on this page you see the same information but graphically presented. And last but not least, invoices will look this way. Now moving on to self-service billing. Let’s look into the billing page. This is how the page usually looks. I highlighted in red some of the important things. The first one — you will see the payment method associated with this account. On the left you will see the billing period, so you will always know when the next charge will come in. It’s the same as with deposit billing — you will see the quantity, the price, and the total for the month of billing. For self-service billing, the company information should be inserted in the billing information section. Keep in mind that in order to make a change after you insert that information, you need to contact our support. It’s not possible to make changes by yourself. And last but not least, billing reporting. There is no visual graph as we saw before, but essentially it does the same thing. It shows all product usage in a graphical way. So everything you see here — the price, the units, the number of usages — you will also see presented in a graph. All right, so that’s all our topics for today.