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
{{ message }}
This repository was archived by the owner on Sep 10, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: docs/reference/scopes.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ MAS also has a few scopes that are specific to the MAS implementation.
81
81
82
82
### `urn:mas:graphql:*`
83
83
84
-
This scope grants access to the whole MAS [GraphQL API].
84
+
This scope grants access to the whole MAS [Internal GraphQL API].
85
85
What permission the session has on the API is determined by the entity that the session is authorized as.
86
86
When [authorized as a user](../topics/authorization.md#authorized-as-a-user-or-authorized-as-a-client) (and without the `mas:urn:admin` scope), this will usually allow querying and mutating the user's own data.
87
87
@@ -91,7 +91,7 @@ The default policy allows any client and any user to request this scope.
91
91
92
92
This scope grants access to the MAS [Admin API].
93
93
94
-
Combined with the `urn:mas:graphql:*` scope, it also grants full access to the MAS [GraphQL API].
94
+
Combined with the `urn:mas:graphql:*` scope, it also grants full access to the MAS [Internal GraphQL API].
95
95
This allows the authenticated entity to perform any operation on the API, regardless of whether the entity owns the data or not.
96
96
97
97
The default policy doesn't allow everyone to request this scope.
0 commit comments