Core ConceptsAuthentication
Core Concepts

Authentication in CUSNIR OS

Learn how to authenticate to unlock full features of CUSNIR OS beyond the demo mode, including account setup and permissions.

Overview

CUSNIR OS provides a demo mode that lets you explore the user interface without authentication. To access full governance and decision-making features, authenticate using email/password or API tokens. Complete registration first, then log in to manage cognitive processes and permissions.

Demo mode limits you to read-only views. Authenticate to enable editing, role assignments, and API integrations.

Registration Process

Create your account to start. Follow these steps to register via the dashboard or API.

Navigate to Registration

Visit https://dashboard.example.com/register in your browser.

Enter Details

Provide your email, a strong password, and optional organization name.

Verify Email

Check your inbox for a verification link and click it to activate.

Log In

Return to the login page and sign in with your credentials.

Authentication Methods

Choose from UI-based login or API authentication. Use the UI for dashboard access and API for programmatic integration.

Use the web interface at https://dashboard.example.com/login.

// Example: Direct browser navigation (no code needed)
// Enter email: user@example.com
// Password: your-secure-password
const response = await fetch('https://api.example.com/v1/auth/login', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    email: 'user@example.com',
    password: 'your-secure-password'
  })
});
const { token } = await response.json();
console.log('Token:', token);

User Roles and Permissions

CUSNIR OS assigns roles that control access. View your role in the dashboard under account settings.

RoleView ProcessesEdit DecisionsManage Users
Viewer
User
Admin

Feature Access Levels

Unauthenticated users (demo mode) see limited UI elements. Authenticated users unlock everything based on role.

Never expose YOUR_TOKEN in client-side code. Rotate tokens regularly and use HTTPS only.

Was this page helpful?
Built with Documentation.AI

Last updated today