Accounts: sign up, sign in, invite teammates
Every NitroPush workspace (“organization”) owns its own projects, releases, and integrations. The first person who signs up becomes the owner — they can invite the rest of the team, change roles, and edit org settings.
Sign up
Sign-up creates a new organization for you. You’ll need:
- An email address (used for the OTP code + future notifications).
- A display name (shown in the dashboard nav).
- An organization name (we generate a URL-safe slug from this — you can rename it later in Settings).
The flow is two steps:
- Fill in
name,email,orgName. Submit. - Check your inbox for a 6-digit code. Type it in. You’re in.
No password to remember. We use one-time codes by email; if your code doesn’t arrive within ~30 seconds, retry — the request endpoint silently re-issues so you can’t get into a stuck state.
Already have an account? Skip the sign-up page and go to Sign in. Same one-time-code flow, just no org gets created.
Sign in
We use email + OTP instead of passwords. The flow:
- Enter your email at
/login. - We email you a 6-digit code (valid for 10 minutes, max 5 attempts).
- Type the code. The browser gets a session cookie and you’re routed to
/dashboard.
Sessions persist for 30 days; closing the browser doesn’t sign you out.
Invite teammates
Once you’re in, head to the Users page in the dashboard sidebar to add the rest of your team.
You can give each invitee one of four roles:
| Role | Can release? | Can manage members? | Can edit org settings? |
|---|---|---|---|
| Owner | ✅ | ✅ | ✅ |
| Admin | ✅ | ✅ | — |
| Developer | ✅ | — | — |
| Viewer | — | — | — |
The owner role is unique to whoever signed up first. To transfer ownership later, contact support.
Edit your profile
Your display name appears in the sidebar nav and in audit logs. Change it anytime from the Profile page (avatar dropdown → Profile, or open the link below). Email is your sign-in identity and can’t be changed in-app.
Edit your organization
Org owners can rename the org or change its slug from the Settings page. Be careful with slug changes — the slug appears in deployment URLs and storage paths, so renaming it can break in-flight bookmarks until the next deployment.