Your organization is the account: the account-level owner of every project, entry, subscriber and API key, with one owner, a name, a slug and a plan. Everything you create lives under it. Open it from "Settings" in the dashboard. The page opens with "Manage your organization and account."
The settings page
| Field | Editable here |
|---|---|
| "Organization name" | Yes |
| "Organization slug" | No |
| "Owner email" | No |
"Organization name" is the only field you can type into. Change it and press "Save Changes". The page shows "Saved." when the write lands.
"Save Changes" does nothing on an unchanged name. The button stays disabled until the typed name differs from the saved one, so retyping the same name is a no-op. The name field is required, so a blank name cannot be submitted and the browser blocks the submit before any request goes out.
The slug is displayed, not edited. Renaming the organization never changes the slug: the save writes the name and nothing else.
The owner email is displayed the same way, and cannot be changed on this page.
Members
Today there is exactly one person per organization: the owner, shown by email under "Owner email". There are no invitations, no roles, no seats and no member list.
Connected repositories
An installation is the DeployLog GitHub App installation that connects repositories to your organization. A manual is the documentation DeployLog builds from a connected repository. The manual is chapter 10. The settings page carries a "Connected repositories" section, described on screen as "Repositories the DeployLog GitHub App can read for your manuals. Pick them on GitHub; the connection comes back here."
- With none connected, the section reads "No repositories connected yet."
- Otherwise it lists one line per repository, owner and repository name, sorted by owner and then repository.
- The button "Connect repositories" sends you to GitHub to pick them. They appear here afterwards.
The page lists and adds. It never disconnects: to remove a repository, take it out of the DeployLog app's repository list on GitHub, and the page drops it the next time GitHub sends you back or you press "Connect repositories".
Danger Zone
The Danger Zone is the red-bordered block at the foot of the settings page. Its copy: "Deleting your account permanently removes your organization, projects, entries, subscribers, and all associated data. This cannot be undone."
This is not "delete the organization and keep the login". The organization goes, the sign-in account goes with it, you are signed out, and you land back on the home page.
The label above the box reads "Type" followed by your organization name and "to confirm". Type that name exactly, character for character. "Delete Account" stays disabled until the typed text matches, and the server checks the match again on arrival; a mismatch is refused with "Confirmation text does not match the organization name" and nothing is deleted.
API keys
An API key is a secret string beginning with the fixed prefix dk_, shown once, kept only as a SHA-256 hash, that lets the DeployLog CLI and integrations act as your organization. A key carries two permissions, read and write. The CLI is chapter 05 and the GitHub Action chapter 06.
A key belongs to the organization, not to a project. One key reaches every project the organization owns.
Open "API Keys" in the dashboard: "Manage API keys for the DeployLog CLI and integrations." With none created, the page shows "No API keys" and "Create an API key to use the DeployLog CLI."
Create a key
- Press "New API Key".
- Fill "Key name", labelled "A label to help you identify this key (e.g. "CI/CD" or "Local CLI").", with the placeholder "e.g. Local CLI".
- Press "Create Key".
The form asks for a name and nothing else. There is no permission picker: every key created from the dashboard carries both read and write.
The key is shown once
The new key lands in a green box: "API key created. Copy it now. You won't see it again." Press "Copy" and the button reads "Copied!" for two seconds.
That box is the only place the full key ever appears. Press "Dismiss", reload, or leave the page and it is gone for good. The list afterwards shows only the first ten characters of the key followed by "...". There is no way to view a key again; if you lose it, revoke it and create another.
The list
Each row shows the key name, its short prefix, and "Created" with the date. "Last used" and a date appear only after the key has authenticated at least once, so a fresh key shows its creation date only.
Revoke
"Revoke" sits at the right of each row. It opens one browser dialog: "Revoke this API key? Any integrations using it will stop working." Cancel and nothing happens. Confirm and the key is deleted immediately and permanently: no undo, no grace period. Revoke the key you just created and its green box disappears with it.