Accounts and access
Accounts, sign-in and workspace access
Understand invite-only access, account settings, passwords, authenticator codes, passkeys and the difference between Rollout and Todoist permissions.
Reviewed October 22, 2026
Rollout is currently invite-only, with public signup closed. Anyone can read these public guides. Opening release sheets and making changes in the shared workspace requires an existing account with the appropriate role.
Sign in to your account
Existing invited users can open the Rollout sign-in page and use the options available there. Password sign-in is supported, and Continue with Google is available when shown. Use the email associated with your Rollout account.
If you cannot sign in, use Forgot password? on the sign-in page or contact your workspace administrator. A sign-in option does not create a new workspace or bypass the invitation requirement.
Manage your sign-in options
Open Account to update your profile and manage sign-in settings:
- Password: set or change your password. The form asks for at least 12 characters and a repeated entry.
- Two-factor codes: choose Enable authenticator codes and follow the setup shown in the app.
- Passkeys: choose Add a passkey on this device when your browser supports passkeys. The account page lists registered passkeys.
- Google: link your Google account when this section is available.
- Todoist: manage your personal task-service connection.
Use Sign out when you finish on a shared device. Do not send another person your account password, authenticator codes or integration credentials.
Understand access
Editors and admins can edit release sheets. Viewers can read releases but cannot edit the sheets or change which Todoist project a release uses. Admins manage workspace members.
Todoist permissions are separate. A viewer with their own connected Todoist account can perform supported task actions when that account has access to the linked project. Reading the shared task view does not automatically grant permission to change those tasks.
Labels organize releases inside the current shared workspace; they are not separate private spaces. Use selected, password-protected sharing links for external readers instead of treating a label as a boundary between audiences.