You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/segment-app/iam/labels.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,9 +37,9 @@ Permissions can then be assigned to users in Access Management by label, on the
37
37
38
38
To create additional custom labels, a Workspace Owner can create new key types in the Manage Labels screen. The Workspace Owner can customize any combination of labels to mirror how resources should be partitioned in their organization.
39
39
40
-
For example, some organizations may prefer to restrict access on their sources and spaces by brand or product area, while other organizations may find it more useful to restrict their resources by tech stack or engineering department.
40
+
For example, some organizations may restrict access to sources and spaces by brand or product area, while others might organize resources by tech stack or engineering department.
41
41
42
-
When you create a new key, it becomes available in the S ources page as a column type that can be used to organize sources.
42
+
When you create a new key, it becomes available in the Sources page as a column type that can be used to organize sources.
43
43
44
44
## FAQ
45
45
@@ -68,7 +68,7 @@ No. If you need to rename a label, first create a new label, assign it to all re
68
68
69
69
##### Can I assign multiple values from the same category to a resource?
70
70
71
-
No, you can assign only one value per category. This prevents confusion about permissions. For example, if a user has access to `brand:A`, it’s unclear whether they should also access sources labeled both `brand:A` and `brand:B`. To avoid this, each resource can have just one value per label category.
71
+
No, each resource can have only one value per label category. This prevents confusion about permissions. For example, if a user has access to `brand:A`, it’s unclear whether they should also have access to sources labeled both `brand:A` and `brand:B`. Limiting resources to one value per category avoids this confusion.
72
72
73
73
##### How does assigning permissions based on labels work?
74
74
@@ -91,4 +91,6 @@ Then the following users with Source Admin restricted with labels will only have
91
91
| Jane |`product: car`| A, C |
92
92
93
93
##### Can I grant a user permissions with `OR` statements?
94
-
You can only assign one set of additive labels on a per-user basis. However, to give a user who needs access to all sources labeled `brand:a` or `brand:b`, we recommend that you use Group permissions and assign this user to two separate groups, where one group has Source Admin access to `brand:a` and the other has Source Admin access to `brand:b`.
94
+
95
+
To grant a user access to sources labeled `brand:a` or `brand:b`, use group permissions. Create two groups: one with Source Admin access to `brand:a` and another with Source Admin access to `brand:b`, then assign the user to both groups.
0 commit comments