Users and sign-in
draftPitwall has its own accounts, an email and a password each. There is no sign-up page and no single sign-on: an instance is meant for a small team that knows each other.
Getting an account
Section titled “Getting an account”| Who | How |
|---|---|
| The first person | Opening Pitwall with no users leads to /setup, which creates the first account. It works once |
| Everyone after | A signed-in person creates a link in Your settings → Invitations and sends it. It works once and expires after 7 days; the invitee chooses their own email and password |
Invitations also lists the links not yet used, and revokes one.
Sessions
Section titled “Sessions”| At sign-in, “Keep me signed in on this device for 30 days” | The session lasts |
|---|---|
| Checked | 30 days from last use |
| Unchecked | Until the browser closes, or 12 hours without use |
Sign-in is limited: 5 failures for one email, or 20 from one address, within 15 minutes, and the next attempt is refused for a while. A wrong email and a wrong password answer the same.
A forgotten password
Section titled “A forgotten password”A password is reset from the server, not from the sign-in page. In the server’s container:
core user reset someone@example.comIt prints a link that works once, for one hour. Send it to that person: opening it sets a new password and signs them out everywhere. The link is whole when PITWALL_PUBLIC_URL is set; otherwise it prints the path to add to your instance’s address. See core CLI.
There is no administrator of the instance. A role is per project:
| Role | Can |
|---|---|
| Owner | Everything in the project, including its settings and its members |
| Member | File tickets, run pipelines, answer agents, test and merge |
| Viewer | Read the project. Is notified for nothing |
A project always keeps at least one owner.