Dashboard overview

CLI results appear at app.corelayersecurity.com. Your role determines which pages and records you can see.

Signing in

Go to app.corelayersecurity.com and sign in with the account your organisation admin invited. SecureAI is invite-only: there is no public sign-up, and accounts are always created by an admin inside an existing organisation.

After signing in you land on the overview for your role. Everyone has a profile page reachable from the icon in the bottom-left corner.

The four roles

Role	Lands on	Built for
Organisation Admin	`/app/admin/overview`	Running the organisation: people, projects, models, CLI access, audit.
Security Researcher	`/app/security/overview`	Doing the security work: triage findings, inspect sessions, accept risk.
Developer	`/app/developer/overview`	Fixing what is theirs: their models, their scans, their findings.
Executive	`/app/executive/overview`	Reading posture: risk, compliance, and summary reporting.

The exact permission matrix is on Roles & permissions.

Where things are

AdminManaging usersInvite people, change roles, suspend or remove access.AdminModels & projectsRegister the AI systems you are securing and group them into projects.SecurityFindingsTriage what the CLI found, change severity, and accept risk.AdminCLI accessIssue, rotate, and revoke scoped CLI tokens.EveryoneReportsGenerate technical and executive assessments.TerminalCLI referenceThe commands that produce everything you see here.

Sections by role

Organisation Admin

Overview, Organisation, Projects, Models, Users, Access, CLI Access, Reports, Integrations, Audit Logs, Settings.

Security Researcher

Overview, Models, Scans, Findings, Sessions, Runtime Events, CLI Activity, Reports.

Developer

Overview, My Models, Scans, Findings, CLI Activity, Reports. Each scoped to their own work.

Executive

Overview, Risk, Models, Compliance, Reports. Summary-level throughout, with no raw findings.

First-time setup

The first admin in a new organisation is walked through onboarding: confirm the organisation details, create a project, and register a model. You can skip this and return later. Scans upload against a model, so registering one early makes results land where you expect.

The dashboard reflects CLI runs, it does not replace them

Scans, tests, and runtime evaluations are started from the CLI. The dashboard is where results accumulate, are triaged, and become reports. It is also where you manage access to users, models, projects, and tokens.

Data isolation

Your organisation's findings, scans, and reports are visible only to members of your organisation.
CoreLayer staff administer the platform by provisioning organisations and managing billing, but they do not have access to your security findings, scan results, or reports.