Skip to content

Commit f27ad49

Browse files
author
Heathpackard
authored
Update access-policies.mdx
1 parent 670c248 commit f27ad49

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

content/docs/guides/(data-access)/definitions/access-policies.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -41,11 +41,11 @@ Access policies evaluate claims and key/value pairs in the provided context. The
4141

4242
- **context.server**: This context is generated by the server and is generally considered trusted. It includes information like trusted JWT claims, IP addresses, and actions.
4343
- **context.server.claims**: Contains claims extracted from a JSON Web Token (JWT) that has been signed by a trusted issuer. This is typically used for claims that are standardized and validated by an identity provider like Okta.
44-
- **context.server.purpose_names**: the purposes specified on an accessor to which this access policy is attached (does not apply in all cases)
45-
- **context.server.ip_address**: the IP address of the user or system initiating the request
44+
- **context.server.purpose_names**: the purposes specified on an accessor to which this access policy is attached (does not apply in all cases).
45+
- **context.server.ip_address**: the IP address of the user or system initiating the request.
4646
- **context.client**: This context contains key/value pairs specified in the request comments by the client and is not considered trusted. It includes data such as user-specified parameters that are not verified by the server.
4747
- **context.user**: Information about data for the user whose data is row being accessed.
48-
evaluated by the access policy
48+
evaluated by the access policy.
4949
- **context.query**: Specific query parameters relevant to the request.
5050
- **context.row_data**: Specific Column data for the user row data values related to being evaluated by the request.
5151

@@ -232,7 +232,7 @@ function policy(context, params) {
232232

233233
UserClouds has several built-in access policies for common use cases, like role-based and time-based expiration of data. However you can also create custom policies, in two ways:
234234

235-
- Call the [CreateAccessPolicy API](/docs/reference/tokenizer/policies/access/post)
236-
- Compose a new policy from existing policies and parametrizable templates in the UserClouds Console
235+
- Call the [CreateAccessPolicy API](/docs/reference/tokenizer/policies/access/post).
236+
- Compose a new policy from existing policies and parametrizable templates in the UserClouds Console.
237237

238238
To learn more about creating access policies, see our How to Guide on Creating Access Policies.

0 commit comments

Comments
 (0)