Picture of Rules and Weightings in Access Permissions | Example Scenario 2 | BG_AP_005

Rules and Weightings in Access Permissions | Example Scenario 2 | BG_AP_005

In this video, we delve into a more complex scenario involving multiple rules, customers, and products to illustrate how Infigo's access permissions can be configured and managed. You'll see how different rules, with varying priorities (weightings), interact to establish connections that grant or deny access to specific products. The tutorial explains how default access settings, individual rules, and department or category-level permissions come together to create a flexible and controlled access environment within your storefront. This session is ideal for those looking to understand the nuances of access permissions in Infigo, especially when dealing with multiple customers and products.

Tutorial Video Transcript

A transcript of our tutorial video, ensuring you can find exactly what you need, when you need it.

You can search this page to find the relevant time-stamp in the video. Also, this text can be used as part of the tutorial search feature.

00:00:05:25 - 00:00:08:04
Okay, so hopefully that makes sense.

00:00:08:04 - 00:00:10:09
What I want to do now is scenario

00:00:10:09 - 00:00:13:09
two where I'm going to build
expand this a little bit.

00:00:13:15 - 00:00:15:06
So rather than just looking at one

00:00:15:06 - 00:00:18:18
single connection
between one customer and one product,

00:00:18:29 - 00:00:24:16
I want to put in a few more connections,
a few more products, a few more customers,

00:00:24:24 - 00:00:27:24
and we'll see how those interact
with one another.

00:00:28:03 - 00:00:30:26
So what we have in
this scenario is multiple roles

00:00:30:26 - 00:00:34:03
establishing connections
between products and customers.

00:00:34:03 - 00:00:37:11
So this is an already configured
storefront which again you have access to.

00:00:37:11 - 00:00:40:07
So the scenario to storefront,

00:00:40:07 - 00:00:42:23
what we're going to do in the next slides

00:00:42:23 - 00:00:46:15
is address these rules in order of waiting
to see what impacts

00:00:46:15 - 00:00:51:02
they're going to have on our connections,
see how they actually work.

00:00:52:02 - 00:00:55:04
And this scenario primarily aims
to clarify the order in which

00:00:55:04 - 00:00:58:04
rules are enacted and how they influence

00:00:58:07 - 00:01:01:07
how the connections are actually working.

00:01:01:18 - 00:01:05:11
So as we've just a brief example,
what we've got here is three products.

00:01:05:25 - 00:01:08:00
We've got three customers.

00:01:08:00 - 00:01:09:26
Two of those products are in a category.

00:01:09:26 - 00:01:12:08
Two of those customers
are in a department.

00:01:12:08 - 00:01:15:26
And we've got all of these connections
which we've defined as various roles

00:01:16:03 - 00:01:19:03
linking up these different products.

00:01:20:26 - 00:01:23:26
Now, as I mentioned, we do have this in.

00:01:26:12 - 00:01:27:14
Another page as well,

00:01:27:14 - 00:01:30:18
which I've lost the link to
at the moment, but

00:01:30:18 - 00:01:33:18
we'll work with that.

00:01:33:29 - 00:01:35:04
Right.

00:01:35:04 - 00:01:38:04
So step one here is the default access.

00:01:38:12 - 00:01:41:12
So again the default access applies

00:01:41:21 - 00:01:42:15
regardless.

00:01:42:15 - 00:01:45:07
It's part of the general setup
for access permissions.

00:01:45:07 - 00:01:46:18
So it will always apply.

00:01:48:02 - 00:01:51:17
So in this case we've
denied default access from no customer

00:01:51:17 - 00:01:54:23
has access to any product
without any other rules

00:01:54:24 - 00:01:57:24
being applied. So.

00:02:00:11 - 00:02:01:04
Now remember

00:02:01:04 - 00:02:04:22
we're going to proceed from the highest
to the lowest weighted rules.

00:02:04:22 - 00:02:08:08
That's
how this order of operation occurs.

00:02:08:28 - 00:02:13:19
So the first example we've got here is
a direct customer to product connection.

00:02:13:27 - 00:02:17:06
So customer three has been granted access
to product three.

00:02:18:28 - 00:02:20:19
That's got the highest weighting
in this case

00:02:20:19 - 00:02:23:19
I waiting of two

00:02:23:26 - 00:02:24:15
nice and easy.

00:02:24:15 - 00:02:26:01
Don't need to go into much else on that.

00:02:26:01 - 00:02:29:01
One customer has access to one product.

00:02:31:19 - 00:02:32:28
As we've talked about already,

00:02:32:28 - 00:02:37:06
the same can also the same methodology
can also be utilized to deny access,

00:02:37:13 - 00:02:40:18
to establish a connection,
to refuse access to a product.

00:02:41:07 - 00:02:45:14
So this is regardless of the fact that
the default access is saying it's denied.

00:02:45:24 - 00:02:48:19
This is kind of cementing that capability.

00:02:48:19 - 00:02:51:13
So in this case, we've defined a rule
which says

00:02:51:13 - 00:02:54:24
customer three cannot access product two.

00:02:55:10 - 00:02:57:00
So that is now an established connection.

00:03:02:27 - 00:03:04:16
Now our third rule here

00:03:04:16 - 00:03:08:28
is showing that it doesn't just have to be
a single customer or a single product.

00:03:09:13 - 00:03:10:21
So our third rule we're saying

00:03:10:21 - 00:03:14:07
that Department one
has been granted access to category one.

00:03:14:22 - 00:03:18:01
And what that means is that we establish
multiple connections here

00:03:18:01 - 00:03:21:04
between multiple products
and multiple customers.

00:03:21:17 - 00:03:25:10
So with that one rule, we've applied
all of these different connections

00:03:25:20 - 00:03:28:20
and we fix those in place.

00:03:31:29 - 00:03:34:22
Our next rule and we're still going down
waiting here.

00:03:34:22 - 00:03:35:21
So these are less and less.

00:03:35:21 - 00:03:40:18
Priority is for customer three
to be granted access to category one.

00:03:41:14 - 00:03:44:07
Now what they should do
on the face of it is grant

00:03:44:07 - 00:03:47:24
that customer access
to both product one and product two.

00:03:48:15 - 00:03:51:24
However, we need to be aware
that one of those connections

00:03:51:24 - 00:03:54:24
has already been established
using a previous rule.

00:03:55:06 - 00:03:58:15
So we had a previous rule which
granted customer three access to product

00:03:58:16 - 00:04:02:06
two, denied access rather between those

00:04:02:23 - 00:04:05:10
because that previous rule
was higher weighting.

00:04:05:10 - 00:04:07:25
We do not override it with this one.

00:04:07:25 - 00:04:11:20
So even though we've said
customer three has access to category one,

00:04:11:28 - 00:04:15:27
the only connection that will be changed
and established is this one here.

00:04:29:03 - 00:04:30:00
Okay.

00:04:30:00 - 00:04:32:01
And I was hoping to show that.

00:04:32:01 - 00:04:35:01
So let me just.

00:04:36:27 - 00:04:39:27
Change my sample storefronts.

00:04:43:28 - 00:04:44:06
Yeah.

00:04:44:06 - 00:04:45:19
So you have access to this?

00:04:45:19 - 00:04:48:15
This is one of the sample storefronts
I've given you.

00:04:48:15 - 00:04:51:15
If I just share the rules
that we've been created for that one.

00:04:52:28 - 00:04:55:28
You can see that's been covered with four
rules.

00:04:55:28 - 00:04:57:29
We've got two rules
which have a weighting of two,

00:04:57:29 - 00:05:00:29
which are single customer,
two single product.

00:05:01:26 - 00:05:03:19
We've got one rule
with a weighting of one,

00:05:03:19 - 00:05:06:19
which is department to category.

00:05:07:14 - 00:05:10:29
And then our final rule
which was one customer to a category.

00:05:11:13 - 00:05:14:13
And that's exactly the scenario
that we've been looking at.

 

Incomplete
Step by Step Guide
Search Terms

Individual Search Words

rules, connections, departments, categories, weightings, priorities, scenario, access, permissions, products

Alternate Search Phrases

set product access levels, manage customer access, configure department rules, establish connection priorities, adjust category access, control product visibility, define user access rules, troubleshoot access permissions, customize storefront access, create access rules