Olyron Accounts
One identity.
Every Olyron product.
Accounts holds the person, the organization and the role. CRM, Labs, Browser and OwnBite read them off the token instead of rebuilding auth four times.
Password · Google · Sign-in link
Issued by
accounts.olyron.com
What the session carries
- Signed in as
- you@your-domain.com
- Organization
- Your organization
- Role on the token
- Admin
- Tenant claim
- org_id + role
Opens without a second sign-in
Olyron CRM(opens in a new tab)
Member and patient lifecycle CRM for health orgs — included with the suite.
Olyron Labs(opens in a new tab)
Clinic roster, consent, and provider ops on Olyron Identity.
Olyron Browser(opens in a new tab)
Identity-native browser cockpit for clinics and care teams.
OwnBite(opens in a new tab)
Health recipes, AI food analysis, and social diet communities — signed in with Olyron.
Olyron Accounts at a glance
5
Health products
Accounts, CRM, Labs, Browser and OwnBite, on one login.
12
Logistics surfaces
Operator desks, partner inboxes and public quote sites.
5
Roles that travel
Owner, admin, member, billing and read-only ride the token.
3
Sign-in methods
Password, Google, or an emailed sign-in link.
How it works
How a session is issued
Four steps, and only the first one involves a password.
Sign in once
Password, Google, or an emailed sign-in link. Whichever route a person takes, the session is created here and stays here.
Bind an organization
Membership and role attach to the person, not to each product. Invite someone once and every surface already knows what they are allowed to do.
Issue claims
The token carries the active organization and role, so a downstream API can enforce the tenant without keeping a second copy of your org chart.
Enter the suite
CRM, Labs, Browser and OwnBite accept that token. Same person, same org, same role — and no second password to lose.
What signs in here
5 health products. One login.
Accounts is the identity platform. Everything else in the suite authenticates against it and reads the organization off the token.
- Packaging: Platform
Olyron Accounts
Hosted auth, orgs, RBAC, SSO, and org-aware tokens for every Olyron health app.
- Packaging: Included
Olyron CRM(opens in a new tab)
Member and patient lifecycle CRM for health orgs — included with the suite.
- Packaging: Add-on
Olyron Labs(opens in a new tab)
Clinic roster, consent, and provider ops on Olyron Identity.
- Packaging: Add-on
Olyron Browser(opens in a new tab)
Identity-native browser cockpit for clinics and care teams.
- Packaging: Add-on
OwnBite(opens in a new tab)
Health recipes, AI food analysis, and social diet communities — signed in with Olyron.
Plus 12 logistics desks and public sites — operator consoles, partner inboxes and quote surfaces — signing in against the same session.
See the full catalogCompared
What the other products stop having to build
Accounts is the control plane. Nothing downstream rebuilds auth, because nothing downstream is allowed to own it.
Each app on its own
Each product keeps its own session
With Olyron Accounts
The session lives on Accounts
Each app on its own
A new password for every app
With Olyron Accounts
Password, Google, or a sign-in link — once
Each app on its own
Org membership rebuilt per product
With Olyron Accounts
Membership and role attach to the person
Each app on its own
Consent implied by the redirect
With Olyron Accounts
An explicit approve step names what the app can read
Each app on its own
Tenant context left to each API to guess
With Olyron Accounts
Tokens carry the active organization and role
Each app on its own
Identity mixed into product data
With Olyron Accounts
Identity stays separate from product data
Questions
Before you create an account
The six things people ask first.
No. You can sign in with Google or have a sign-in link emailed to you. A password is available if you want one, and you can set it later under Settings.
Continue with Google on the sign-in page. That creates or links the same Accounts identity the rest of the Olyron products already recognize.
Yes. Accounts holds identity, organizations and consent. CRM, Labs, Browser and the rest keep their own databases. The token tells them which person and which organization is calling.
The consent screen lists the scopes before you approve. First-party suite apps and third-party clients go through the same grant, and you can unlink a method later in Settings.
You create an organization, invite people by email, and assign owner, admin, member, billing or read-only. The active organization travels on the token so every API can enforce the tenant.
Ask an owner or admin to remove you from the organization's members screen. Your Accounts login stays exactly as it was; only that membership ends.
Invite the team
Create an account. Invite the team.
Open an organization on the same login every Olyron product already uses, then hand out any of the 5 roles by email.
Password · Google · Sign-in link