Role-Based Access Control (RBAC)
Relevant source files
The following files were used as context for generating this wiki page:
Role-Based Access Control (RBAC) in the inkweave-admin project manages access to private administrative tools. The system ensures that only authorized personnel interact with the administrative interface of the Inkweave platform.
The RBAC implementation relies on external deployment protections and repository-level access constraints. This prevents public users from accessing the internal tools hosted in this repository.
Sources: README.md:3-5
Access Control Architecture
The project implements a centralized access model by leveraging Vercel's infrastructure. Authentication occurs at the network edge before a user reaches the application layer.
Deployment Protection
The application deploys to a Vercel project configured with mandatory login requirements. This configuration serves as the primary barrier for administrative access.
- Vercel Login: The system requires a valid Vercel account authorized for the specific project.
- Private Scope: The tools remain isolated from the public-facing application located at
Doberjohn/inkweave.
Sources: README.md:4-5
Access Flow Diagram
The following diagram illustrates how a user gains access to the admin tools.
The diagram shows that authentication is handled by Vercel before the request reaches the inkweave-admin application code.
Sources: README.md:4-5
Component Overview
The RBAC system involves specific components within the repository structure that define the administrative scope.
| Component | Function | Access Level |
|---|---|---|
inkweave-admin | Host repository for administrative logic. | Private / Restricted |
upstream/inkweave | Submodule containing core application code. | Read-only for admin |
docs/PLAN.md | Contains design and phase status documentation. | Internal |
CLAUDE.md | Defines working rules and operational guidelines. | Internal |
Sources: README.md:3-8, .gitmodules
Configuration and Rules
Access and operational behavior are guided by internal configuration files.
Repository Restrictions
The inkweave-admin repository is explicitly marked as a private environment. It pins the public inkweave repository as a submodule to provide administrative oversight without exposing admin logic to the public.
- Submodule Reference:
upstream/inkweave - Target Project: Vercel-protected production environment.
Sources: README.md:3-5, .gitmodules
Operational Guidelines
Development and administrative actions within the RBAC-protected zone follow specific rules defined in the repository. These rules ensure that changes to the administrative interface remain consistent with project standards.
- Design Rules: Managed through
docs/PLAN.md. - Operational Rules: Managed through
CLAUDE.md.
Sources: README.md:7-8
Summary
The Role-Based Access Control in inkweave-admin is enforced through Vercel's deployment protection. By requiring a Vercel login, the project restricts access to the private admin tools. This architecture maintains a clear separation between the public Inkweave application and its internal administrative utilities.