Skip to content

Commit 656e4aa

Browse files
authored
Update 3-applying-access-policies-to-queries.mdx
1 parent 202b7b6 commit 656e4aa

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/docs/guides/(data-access)/proxy-and-plug-in-implementation/3-applying-access-policies-to-queries.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,11 @@ Access policies are evaluated per row of returned data from the database. Theref
2121
2. **Select and Edit the Query, Blob Store, or API Call:**
2222
1. **For SQL Proxies:** In the UserClouds Console, go to Accessors (under Access Methods), find the relevant query in your list of data accessors, and click "Edit".
2323
2. **For NoSQL Proxies:** In the UserClouds Console, navigate to Object Stores under User Data Storage in the side navigation, select the object store, and click "Edit".
24-
3. **For API Proxies:** In the UserClouds Console, navigate to API connections under User Data Storage in the side navigation, select the API connection, and click "Edit".
24+
3. **For API Proxies:** This is not yet implemented.
2525
3. **Add Access Policies**: Scroll down to the access policy section and add one or more access policies.
2626
1. **For SQL Proxies:** Apply policies at the query level.
2727
2. **For NoSQL Proxies:** Apply policies at the object store level, but you can also consider the file path as context (e.g., a user ID in the file path) for finer-grained access control.
28-
3. **For API Proxies**: Apply policies at the individual endpoint level.
28+
3. **For API Proxies**: This is not yet implemented.
2929
4. **Define Policy Logic**: If adding two or more access policies, define whether all policies or one policy must be true for the overall policy to pass, by ANDing or ORing the policies together.
3030
5. **Save**: Click "Save".
3131

0 commit comments

Comments
 (0)