odooium.sh

Sign in

Control the frame. They run the core.
Continue with GitHub

GitHub is the only way in — for customers and for CDS. There is no password to set, no reset to request, and no second account to offboard. Your GitHub identity is already the one that grants push rights on the repository, which is what lets the two permission layers connect by username.

GitHub is about to ask for this — a reproduction of GitHub's consent screen, drawn so the scope decision is reviewable. This product never sees an Authorize button: the consent happens on GitHub's own page.

GitHub is asked for this — and nothing else
read:useryour login and public profile
user:emailyour verified email address
That is the whole list. Sign-in is identity-only. odoo.sh also asks for repo and write:repo_hook, because it pushes with your OAuth token. Ours are not human-initiated pushes — an agent proposes and an executor pushes — so repository authority is a per-repo GitHub App installation token, short-lived and attributable, that survives the day the person who connected it leaves. Nobody types a token, and your account's reach is never borrowed.

Odooium.sh is invite-only. If you have not been invited to a project you will be able to sign in and see nothing — that is not a fault, and the next screen says so plainly. Odooium.com ↗ is a separate product with a separate login; signing in there does not sign you in here.