Admin Quick-Start Guide

Go to admin.corla.ai/signup and create your account. You'll need:

• Your name and email address
• Enterprise name (e.g. "Acme Engineering")
• A unique slug (e.g. acme-engineering) — this identifies your enterprise
• A password (min 8 characters, must include uppercase, lowercase, and a number)

After signing up, check your email for a verification link. Click it to activate your account, then log in.

Navigate to Assets in the sidebar. Assets are the proprietary context you want to share with developers. Click Upload Asset and provide:

• Name — a descriptive title (e.g. "TypeScript Review Standards")
• Type — System Prompt, Skill, Playbook, or Knowledge Doc
• Sensitivity — Low, Medium, High, or Critical
• File — upload a Markdown, PDF, DOCX, XLSX, or plain text file

You can also connect a GitHub or GitLab repository as an asset source. Go to Assets → Connect Repo, authorize access, and select the files or folders to sync. Changes pushed to the repo are automatically synced.

Go to Projects in the sidebar and create a project. Projects scope access — a developer granted access to "frontend-app" can only receive context relevant to that project.

• Name — e.g. "Frontend App" or "API Platform"
• Slug — e.g. frontend-app
• Description — optional, helps you organise

When uploading assets, assign them to the relevant project(s) so grants can be scoped correctly.

Go to Roles in the sidebar. Roles define what a developer can access. Create a role with:

• Name — e.g. "contractor" or "senior-dev"
• Permissions — select which asset types they can access (System Prompts, Skills, Playbooks, Knowledge Docs)

You can create multiple roles with different permission levels — for example, a "contractor" role with access to Playbooks only, and a "senior-dev" role with access to everything.

Go to Members in the sidebar. Add a member profile for each developer:

• Member ID — a unique identifier (their email, username, or external ID)
• Email — for sending onboarding instructions
• Name — display name
• Specialty — Frontend, Backend, Fullstack, Security, etc. (used for role-based asset filtering)

The developer will receive a welcome email with setup instructions.

Go to Grants in the sidebar. A grant is an explicit authorisation for a developer to access context within a specific project. Click New Grant and select:

• Member — the developer you just added
• Role — the role that defines their permissions
• Project — which project they're working on
• TTL — how long each session token lasts (default: 8 hours)
• Expiry — optional date when the grant itself expires

After creating the grant, you'll see a one-time invite secret. Share this with the member — they need it for their first login only. On first login (in the CLI or in the member portal), they set a password. Every subsequent login uses the password — no admin involvement, no fresh invite secret needed.

Your admin console gives you full visibility and control:

• Sessions — see active developer sessions, revoke access instantly
• Audit Log — every context delivery, login, and access event is logged
• Compliance — export audit data as CSV/JSON, configure SIEM webhook alerts
• Settings — manage billing, configure SSO (coming soon)

Revoking a grant or session takes effect within 30 seconds — the developer's token is invalidated immediately.