User Management
Relevant source files
The following files were used as context for generating this wiki page:
User Management in the Inkweave Admin project governs access to private administrative tools and facilitates the interaction between admin users and the core Inkweave application logic. The system prioritizes security by utilizing third-party authentication and isolating administrative functions from the public application codebase.
The system serves as a management layer for the primary Inkweave Platform, maintaining a clear separation between public user capabilities and internal administrative operations.
Sources: README.md:1-4
Administrative Access Control
The Inkweave Admin application does not implement a local user database for credentials. Instead, it relies on environment-level authentication to ensure only authorized personnel can access the management interface.
Vercel Authentication
Access to the admin tools is restricted at the deployment level. The project deploys to a Vercel environment that requires a valid Vercel login for access. This mechanism prevents unauthorized public access to the admin routes and internal data.
Sources: README.md:4, vercel.json
Authorization Flow
The following diagram illustrates the high-level process of gaining access to the admin management interface:
This diagram describes the authentication handshake provided by the Vercel deployment platform to secure the admin tools.
Sources: README.md:4
Integration with Upstream Inkweave
The admin tool operates by interacting with the main Inkweave application, which is integrated as a git submodule. User management within the admin tool involves managing data and configurations that affect the upstream project.
| Component | Role in User Management | Configuration File |
|---|---|---|
| upstream/inkweave | Provides core data models and business logic | .gitmodules |
| vercel-login | Handles identity and session persistence | README.md:4 |
| admin-interface | Allows modification of upstream application states | README.md:1-2 |
Sources: README.md:3-4, .gitmodules
Submodule Architecture
The project pins a specific version of the public application to ensure compatibility during administrative tasks.
The diagram shows the relationship between the private admin tools and the public core application.
Sources: README.md:3
Project Guidelines and Planning
User management and system development follow specific rules and roadmaps defined in the project's documentation files.
- Working Rules: Developers must follow the guidelines established in
CLAUDE.mdfor all implementation tasks. - Phase Status: The progression of management features is tracked within
docs/PLAN.md.
Sources: README.md:6-7, CLAUDE.md, docs/PLAN.md
Conclusion
User Management in Inkweave Admin is centered on secure, delegated authentication via Vercel. By leveraging submodules and environment-level security, the project ensures that administrative access remains private and isolated from the public-facing Inkweave application.