Algolia Enterprise Access Design

Overview

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.

Prerequisites

• A named repository, environment, and Algolia application or index in scope
• The local lockfile and installed client types as implementation authority
• A safe read-only query or explicitly disposable test target
• Current first-party documentation for any provider behavior that affects the change

Tool Discipline

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.

Current Contract