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: content/docs/guides/(authorization)/Implement-AuthZ-in-3-steps/1-design-your-model.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,9 +37,9 @@ The first step is to define the structure of your permission system. There are f
37
37
38
38
The first step is to scope your authorization project. Write a list of the <Glossary>permission</Glossary>s you want to model in your system. Then write a list of permission 'stories' you want the model to support, like:
39
39
40
-
- A user with view access to a folder should have view access to all files inside that folder
41
-
- Leaders in the Sales department should be able to create new deals
42
-
- A manager should be able to view the compensation of all their reports (direct & indirect)
40
+
- A user with view access to a folder should have view access to all files inside that folder.
41
+
- Leaders in the Sales department should be able to create new deals.
42
+
- A manager should be able to view the compensation of all their reports (direct & indirect).
43
43
44
44
This exercise will give you a sense of which users, groups and resources you want to model permissions on, the relationships between those <Glossary>object</Glossary>s, and how those relationships affect permissions.
45
45
@@ -69,8 +69,8 @@ To add an edge type, go to the Authorization tab in UserClouds Console and click
69
69
70
70
Attributes are defined at the edge type level, so all edges of a given type share the same attributes. Each attribute typically achieves one of the following goals:
71
71
72
-
- They give a user permission on an object directly (<Glossary>direct</Glossary> attributes)
73
-
- They pass a permission from one user or group to another (<Glossary>inherit</Glossary> attributes)
74
-
- They propagate a permission down a hierarchy of nested objects, like folders and files (<Glossary>propagate</Glossary> attributes)
72
+
- They give a user permission on an object directly (<Glossary>direct</Glossary> attributes).
73
+
- They pass a permission from one user or group to another (<Glossary>inherit</Glossary> attributes).
74
+
- They propagate a permission down a hierarchy of nested objects, like folders and files. (<Glossary>propagate</Glossary> attributes)
75
75
76
76
For more intro on attributes, see [Modelling Hierarchy with Attribute Scopes](/docs/guides/overview/modelling-hierarchy-with-attribute-types).
0 commit comments