Accounts & access

Signing in

eode uses hosted single sign-on. There is no in-app password screen: visiting the app hands you to your organization's sign-in and lands you back where you started. Your session is a secure, HTTP-only cookie that refreshes while you work. Sign out in the profile menu ends the session and clears it.

Access is by invitation. If the account you signed in with is not in an organization, eode does not open: you get a single page headed Your account is not in an organization, showing the address you are signed in as, and one button, Sign out. Ask your organization's admin to invite that address, then sign in again with it. If you signed in with a personal address where a work one was invited, sign out and use the invited one.

If you were invited but your membership could not be set up yet, the same page is headed Your membership could not be completed yet instead: "Your invitation is recorded, but the service could not finish setting up your membership. Try again later, or contact support."

When an admin removes you from your organization — from the organization's Members list, or through your sign-in provider — your session ends right away, and signing in again shows the page above.

The profile menu

Your chip sits at the right of the header: your initials, your name, and a small-caps line reading your organization — or your role, if you are not in one — and your persona. Live, that reads like RIVERLOGIC.COM SSO · MODELER.

Clicking it opens the menu: your name, email and standing (Owner of <org>, Org Admin at <org>, Member of <org>), then

• Organization, with your organization's name beside it.
• Credits — your Decision Credits balance and how to top it up.
• Send feedback — a bug, idea or question, sent with a diagnostics snapshot attached.
• Beta survey — the beta questionnaire.
• Sign out.

Personas

Your persona sets the shape of the product around how you work. There are four:

You choose one the first time you sign in. What it changes:

• The Home greeting, and whether Home leads with a grid of models to run or review.
• Whether authoring affordances are offered — an operator and an executive are not asked to build models.
• The RIA Console's opening line and its suggestion chips.
• Where you land, and which guided walkthrough is offered, on your first visit.

A persona is not a permission and it does not hide anything: every rail item, every command and every screen is reachable under all four. What you are allowed to do comes from your roles.

Platform roles

Organization roles

An organization has its own, separate set of roles — owner, admin, member — and they are what govern the organization itself. The Organization screen names your standing as the owner, an admin or a member.

Who can act on whom:

• The owner can never be changed or removed by anyone else.
• An admin can only be changed by the owner.
• A member can be changed by the owner or by an admin.

Organizations

Organizations are set up through your sign-in provider, and you join one by invitation — there is no way to create or request to join an organization from inside eode. Membership is an admin's decision in both directions: an admin invites you in, and an admin removes you.

Organization in the profile menu opens the organization's screen. It is tabbed:

Admins get row actions on the roster — Make admin, Make member, Remove — and an Invite form below it: enter an Email address, then Invite. "Someone who already has an account is added right away. Otherwise an invitation is emailed, and they join when they accept it." Remove asks first: "They lose access to the organization's models. Work they created inside it stays with the organization." The removed member is signed out at once.

Settings holds three zones:

• Name — rename the organization, then Save name. Admins only.
• Ownership — an organization always has exactly one owner. Transferring makes someone else the owner and leaves you an admin. Make owner beside a member, and a confirmation, does it. Owner only, and only the new owner can transfer it again.
• Leaving — leaving is not self-service. "Ask an admin to remove you from the members list. Work you created inside the organization stays with it." The owner cannot be removed, so an owner who wants out transfers ownership first.

Model-level access

Every model sits in one of two tiers, and the tier is what decides who can see it:

• Personal — yours.
• Organizational — visible to everyone in your organization, with versions, an audit log, locking, and a recorded permission map.

The permission map is on a Model Library row, under Permissions. It lists five groups — Owners, Contributors, Viewers, Promoters, AI agents — with their members and counts.

Promoting a model

Promote to Organizational is deliberate work, and only an Org Admin or a Promoter can do it. "<model> will become visible to every member of your organization." The promotion writes a version snapshot and an audit event.

The dialog runs a checklist first:

RIA drafts the two fields your colleagues will read — Description (40 characters minimum, "Teammates see this in search results and library cards.") and Primary use case (20 characters minimum, "What planning question this model answers.") — labelled RIA-drafted — edit before promoting, with Re-draft to try again. Reason (optional) goes into the audit trail.

Then Promote. Soft warnings do not block it. If a certification check refuses the promotion you get the reason and the remedies, and may override it with Publish anyway, and record that I acknowledged it. Demoting a model back to Personal is a button on the Library card.

Decision Credits

Credits meter what your models cost to run. The Credits screen shows your balance — Your credits, or Your allowance where an organization funds you — alongside the organization's pool, each with a meter that appends (low) as it runs down. One credit is $0.01 of metered model usage, and "turns are charged after they finish, so a balance can end a turn slightly below zero."

Buy credits shows a card per pack with a Buy button. Where purchasing is not enabled, you are pointed at your River Logic representative instead; where your organization funds you, "credits for <org> are managed by your organization admins."

History is the ledger — When, Reason, Credits, Note — reading Welcome credits, Organization grant, Purchase, Added by River Logic, Moved out, Moved in, Turn and Refund. In an organization you can switch the ledger between Yours and the organization's wallet.

Run out and RIA stops rather than guesses: "You are out of Decision Credits. Add credits to keep going." with a Get credits link.

Beta feedback

Seven questions, about two minutes, every one of them optional: how satisfied you are, what you used the product for, how much you used each feature, what was confusing or broken, what you make of the design, whether you would recommend it, and what to build or fix next. The footer counts <n> of 7 answered; Submit needs at least one answer, and sending gets you "Thanks — your answers went straight to the team."

An Org Admin also gets a Responses (admin) tab with everyone's answers.

Review Queue

Review Queue at the foot of the left rail is where the platform proposes things it noticed while running models, for someone to check before it is kept. Every signed-in user can open it; some deployments hide it along with model authoring. Its Auto-detect setting is organization-wide, so only an Org Admin can change it — everyone else sees the current value as text.

It is a platform-operations surface rather than part of decision work, and is not documented further here.