Map people and application actors to Algolia team roles, API-key permissions, index limits, and tenant restrictions. Get a least-privilege access matrix, safe allow-and-deny checks, and lifecycle findings for rotation, SSO, and account changes.
Map workforce roles and application actors to Algolia team permissions, API-key ACLs, and secured-key restrictions. Use when reviewing least privilege, tenancy, SSO requirements, or access rotation. Trigger with "Algolia RBAC", "Algolia SSO", or "Algolia tenant access".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
This skill separates human dashboard access, backend service access, browser search access, and tenant-scoped access. It verifies current account capabilities instead of assuming every plan exposes the same roles or SSO features.
Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan.
Review key descriptions, ACLs, restrictions, owners, and rotation dates without exporting secret values. Production services should use organization-owned, least-privilege keys.
Do not enable SSO, change team roles, revoke keys, or alter tenant filters without owner approval and a tested recovery path.
Return the actor matrix, role and ACL mapping, current-plan evidence, denied-path tests, lifecycle controls, findings, and remediation approvals.
| Condition | Response |
|---|---|
| Feature absent from current account | Record it as unavailable; do not infer entitlement. |
| Actor requires broad ACL | Split duties or document the exceptional grant. |
| Secured key has no restriction | Reject generation. |
| Role change risks lockout | Prepare and test break-glass access first. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
actor=catalog-indexer; operations=save,settings; indices=products_*
Expected handoff:
key=custom; ACL=minimum-reviewed; tenant-browser=secured-key; sso=contract-verified
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.
Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.
Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.