0:00 In this tutorial, we're going to cover one of the key building blocks for iFrame customers, how users are represented inside Infigo, and how to create the accounts you need to operate the system.
0:11 Before we start, a quick note on setup, because this affects what you see in admin. Most iFrame customers have their own Infigo platform and at least one storefront, even if your license only includes one single storefront.
0:24 A smaller set of customers use the PrintIQ iFrame offering, which is a more handed over and managed approach. In that scenario, you'll usually operate within a single storefront.
0:35 And won't be able to create storefronts yourself. Either video are the same. You still need to understand where users live and how roles work.
0:45 The most important thing to understand is this. Administrator accounts and customer accounts are crafted in the same place in Infigo.
0:52 They're the same type of account. The difference is simply the roles that you assign to those accounts, which control what they can access.
0:59 So the place to remember is customer management.
1:02 Now, scope matters here. If you can see Switch Storefront on the top right of your screen, you have platform-level access.
1:11 If you can't see it, you're typically logged in as a storefront administrator with access to a single storefront. If you're on the PrintIQ iFrame offering, it's completely normal to never see Switch Storefront.
1:22 You'll usually just be managing what you need within the storefront that you've been provided. So with that covered off, let's start with the accounts that your team needs.
1:33 If you need to create additional administrators who manage the wider environment, you do that at a platform level. So what I mean by this is actually adding the administrator account on the platform area of the system that you've been given.
1:48 To do this we click on dynamic switch storefront, and then we'll see right at the top of the list that we've been given, of which yours will be much shorter, you'll have this platform entry.
1:57 Select here, and we'll now be making changes to the platform level of the system. Make sure we've navigated back to customer management, and then we're going to go ahead and click add new.
2:10 Now you'll see a lot of fields in here but the only mandatory ones are email address and password. Once those are set, the roles you assign determine the privileges.
2:21 So we go over to the customer roles section, and for a platform administrator created on the platform level, we want both platform administrator and storefront administrator.
2:35 Heading back to the customer info tab, one final option you might need to be aware of is this password expired option.
2:45 If you enable it, the user will be forced to reset their password the next time they log in. Once all that's been set, click save, or save and continue edit to store that user.
2:58 at Storefront Administrators. If you're creating a user who should manage a specific storefront, make sure you're operating in the correct storefront first.
3:08 So the same process as before, if you logged in as the Platform Administrator, you go to switch storefront at the top of the screen, and navigate to the storefront of interest to you, and then click We can verify at the top of the screen that our correct storefront is our current account.
3:26 Thank much. Thank you. Make sure you navigate back to Customer Management, and then repeat the same steps again. Customer Management, add new, enter an email and password, and then this time we're assigning the role of Storefront Administrator, Now here's one important detail.
3:45 To be active on a storefront, an account needs the registered role at minimum. That applies to storefront admins, and it also applies to iFrame customers.
3:58 So we'll go ahead and save that. And now let's create a standard end user. this is the type of account that represents the customer your external website maps to within Infigo.
4:12 So once again, add new. Email password. And for a standard end user, keep it very, very simple. The only customer role we want is registered only, with no additional admin roles.
4:27 At this point, you might be thinking, do we always create customers manually? The answer is not necessarily. There are a couple of common implementation approaches.
4:37 Some iframe integrations, ensure every customer in your external system has a corresponding customer created in Infigo. Now, these can be created manually, or we do have batch upload tools for customer accounts.
4:49 Other integrations use one shared website user within Infigo, which is always passed into the iframe workflow. Either way, you still need to understand customer management, because this is where you'll review customers, troubleshoot access, and confirm roles.
5:09 Finally, let's cover the identifiers you'd hear about in documentation and support conversations. related to the iframe. In the Infigo UI, customer ID and email are readily available.
5:23 For iframe integrations, the customer GUID is also required for subsequent API calls. If you don't store the GUID in your own system, it can be retrieved via an API request that returns the GUID field.
5:38 And if you don't have a customer linkage at all yet, there's also a call that generates a customer SSO URL, and it can automatically create a customer in Infigo with the provided GUID if the customer isn't found.
5:54 Now, one final point here before we move on, where is the GUID located if we want to get it for a particular customer in an Infigo customer account?
6:03 So if I access one of those customer accounts I've created, scroll down on the Customer Info tab and we'll see the GUID field.
6:12 One final heads up that prevents a lot of confusion later.
6:17 If your workflow records orders in Infigo, all jobs within a single order must belong to one customer. If jobs are owned by different users, the create order call will fail.
6:31 Now that's it for the fundamentals of users and customers. Next we're going to move on to products. What iframe customers need to know in the product catalogue and why product IDs matter for linking your external product list to a to the embedded editor?
