Accounts & access
Signing in, what your persona changes, and who can see or promote a model.
Signing in
eode uses hosted single sign-on — there's no in-app password screen. Visiting the app redirects you to your organization's sign-in, and you land back where you started. During the beta, sign-in is limited to invited accounts.
Your session is a secure, HTTP-only cookie that refreshes while you're working. Signing out clears it.
Persona — what you see
Your persona shapes the interface around how you work. The header shows it next to your name (for example MEMBER · MODELER).
| Persona | The interface leans toward |
|---|---|
| Modeler | Building: authoring surfaces, model structure, the develop backlog |
| Analyst | Analysis: scenarios, workspaces, comparisons |
| Operator | Execution: workflow runs, approvals, the ops board |
| Executive | Review: what needs you, what's in flight, what changed |
Personas trim the left rail and reshape Home. They don't grant or remove permissions — that's roles.
Roles — what you can do
| Role | Can |
|---|---|
| Member | Build personal models, run scenarios, use shared organizational models per their permissions |
| Promoter | Everything a member can, plus promote models to the organizational tier |
| Org Admin | Everything, plus lock/unlock and force-release locks, and org-wide scope on Home |
Model-level access
Every model sits in one of two tiers:
- Personal — visible only to you.
- Organizational — visible to your whole organization, with versions, an audit log, locking, and a recorded permission map: Owners, Contributors, Viewers, Promoters, and AI agents.
Promotion is deliberate: it requires a description and primary use case, runs a readiness checklist (base solved cleanly, not locked, at least one KPI), and writes both a version snapshot and an audit event. Demote to Personal reverses it.
Permission assignments are currently displayed for review rather than edited in-app. Locking and promotion are already available to the roles above; per-user permission editing arrives in a later release.
Data isolation
Everything you create is scoped to your organization. Models, conversations, scenarios, and results are never visible across organizations — the scoping is enforced on every request, not just in the interface.