Vercel Authentication Integration
Relevant source files
The following files were used as context for generating this wiki page:
Vercel Authentication Integration provides secure access control for the private administrative tools of the Inkweave platform. This system ensures that only authorized personnel can access the management interface by leveraging Vercel's native deployment protection features.
The integration functions as a security wrapper around the core Inkweave application code, which is pulled into this repository as a submodule. By deploying to a Vercel project configured with "Vercel Login," the project avoids the need for a custom-built authentication backend for administrative functions.
Sources: README.md:1-6, docs/PLAN.md
Deployment Architecture
The system uses a delegated security model where Vercel acts as the Identity Provider (IdP). The admin tools are hosted on a separate Vercel project from the main public application to isolate administrative capabilities and data.
Authentication Flow
When a user attempts to access the admin dashboard, the Vercel edge network intercepts the request. The platform checks for a valid session token associated with the Vercel team or specific authorized accounts.
The diagram shows the request lifecycle where Vercel Authentication serves as a mandatory gateway before the application code is executed.
Sources: README.md:4-6, vercel.json
Submodule Integration and Security
The admin interface tracks the public Inkweave application via a Git submodule. This structure allows the admin tools to use the same UI components and logic as the main app while maintaining a strict security boundary.
- Submodule Path:
upstream/inkweave - Security Scope: The admin project is private and requires specific Vercel permissions to view deployments.
- Separation of Concerns: Public features reside in the main repo, while administrative overrides and tools are managed in this restricted repository.
Sources: README.md:3-5, package.json
Configuration and Management
The authentication behavior is governed by the Vercel project settings and the repository's configuration files.
Key Configuration Elements
| Element | Location | Description |
|---|---|---|
| Deployment Protection | Vercel Dashboard | Enables Vercel Authentication for all preview and production deployments. |
| Submodule Pining | .gitmodules | Tracks the specific version of the Inkweave core used by admin tools. |
| Working Rules | CLAUDE.md | Defines development constraints and interaction rules for the admin environment. |
| Project Plan | docs/PLAN.md | Outlines the phases of admin tool development and security implementation. |
Sources: README.md:8-9, CLAUDE.md, docs/PLAN.md
Access Control Logic
Vercel Authentication Integration validates the user's session against the Vercel Team membership. If you are not a member of the designated Vercel Team, the platform denies access to the deployment environment, regardless of the application-level code.
The sequence diagram illustrates the interceptor pattern used by Vercel to protect the admin routes.
Sources: README.md:6, vercel.json
Summary
Vercel Authentication Integration secures the inkweave-admin repository by placing the entire deployment behind a Vercel-managed login wall. By utilizing upstream/inkweave as a submodule, the project maintains parity with the core application while ensuring that administrative tools remain inaccessible to the public. This approach simplifies the security architecture by offloading identity management to the hosting provider.
Sources: README.md:1-9