Repository navigation
docs(connectors): document ACL enforcement (PRO-3222 PRO-3223) - #334
Conversation
…O-3223) Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
✅ Mintlify HygieneNo issues found. |
Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com>
55d8bd8 to
8759e90
Compare
[Low impact] The documentation appears safe to merge, with a non-blocking mismatch between the guides and the generated API reference. Findings
SummaryDocuments per-connector ACL enforcement for workspace owners and writers.
Reviews (8) · Last reviewed commit: "docs(acl): Drive group membership, key r..." · Reviewed by Greptile |
Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com>
✅ OpenHack SummarySecurity review of docs(connectors): document ACL enforcement (PRO-3222 PRO-3223). 12 changed files; 0 findings at or above the low reporting threshold. Confidence Score: 5/5No reportable security findings were detected in this scan. Security merge-readiness rubric: 1 = critical, 2 = high, 3 = medium, 4 = low, 5 = no reportable findings. This score reflects scan findings, not a guarantee of correctness or complete coverage. Files Needing Attention: None Important Files Changed
Last reviewed commit: 61a0788 · View review on OpenHack
|
Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com>
869590a to
d94579d
Compare
Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com>
Signed-off-by: Vorflux AI <249966464+vorflux[bot]@users.noreply.github.com>
|
@greptile-apps Please review this current head against its focused stack-layer scope and report a score for this exact SHA. |
|
@greptile-apps Please review this current head against its focused stack-layer scope and report a score for this exact SHA. |
1aa9eee to
9c49672
Compare
Signed-off-by: SohamRatnaparkhi <92905626+SohamRatnaparkhi@users.noreply.github.com> Co-authored-by: Soham Ratnaparkhi <soham@hydradb.com>
9c49672 to
2ca1361
Compare
SohamRatnaparkhi
left a comment
There was a problem hiding this comment.
Approved on Soham's behalf: Greptile 5/5 at head, CI green. Behaviour to be verified on staging.
… to autogen - Access Control: a Google Drive-only section on files shared with a group: what google_group_membership_resolves reports, why a false result keeps group-shared files restricted, and the fix (reconnect as a Workspace admin with Directory access). States that no other connector reports it. - Connectors: removing a member, or a member leaving, revokes every key they created in the workspace, and re-inviting restores none. A provider whose acl_supported HydraDB withdraws stops enforcing and keeps enforce_acl. - Update Connector: the 503 when the provider catalog cannot be read while enabling enforce_acl. - api-reference/v2/openapi.json goes back to main. The generated spec (#343) now carries acl_supported, acl_description and enforce_acl from the API's own annotations, so this PR no longer hand-edits it and the two do not conflict. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Soham Ratnaparkhi <soham@hydradb.com>
Goal
Document how workspace owners and writers set per-connector ACL enforcement and how enforced reads use the authenticated caller.
Why
Soham's 13:25 UTC decision updates requirements-sheet rows 1 and 13. Owners and writers can change enforcement. Readers can see the current setting but cannot change it. API keys remain blocked.
Links
Before and after
enforce_aclin human dashboard sessions.What changed
only workspace owners and writers can change ACL enforcement.Tests
make buildpassed.npm run hygienepassed.npm run verify:agents-endpointspassed.jq empty api-reference/v2/openapi.jsonpassed.2ca136184b4bfeb3fec60b787ffbdda160091e5a.Where to look
essentials/v2/connectors.mdx.essentials/v2/access-control.mdx.api-reference/v2/endpoint/create-connector.mdx.api-reference/v2/endpoint/update-connector.mdx.api-reference/v2/openapi.json.Risks
Publish these docs with the coordinated application and dashboard changes.
Session Details
(aside)to your comment to have me ignore it.Need help on this PR? Tag
@codesmith-botwith what you need.