11Organization

Your organization is the single account that owns your projects, entries, subscribers, API keys and connected repositories. Settings is where you manage your organization and account.

Name, slug, owner

Three fields. The organization name is editable; the organization slug and the owner email are shown but fixed.

A name is required and capped at 100 characters. Anything outside that is refused with a VALIDATION_ERROR and a 400, and nothing is saved.

Members

There are none today. Members cannot be added: organization settings accept a name and nothing else. Settings shows one owner email, and that is the whole membership model.

Deleting the organization

Deleting your account permanently removes your organization, projects, entries, subscribers, and all associated data. Type the organization name to confirm; the delete button stays disabled until the text matches. The server checks again, and a mismatch comes back as a 400 with Confirmation text does not match the organization name and deletes nothing. A delete that goes through also removes the owner's user account and signs you out.

API keys

An API key is a secret string the CLI and the GitHub Action send in place of a login. The CLI is chapter 05 and the GitHub Action chapter 06.

Every key starts with dk_ and carries 32 random bytes. The full key is shown once, at creation: API key created. Copy it now. After that the list stores and shows only the first ten characters, so a lost key is replaced, never recovered.

A capability is one permission a key holds. There are four.

Never create a key without read. The picker renders it ticked and disabled, and the API enforces the same floor: a create request without it is refused with Every key needs the read permission, and a request with no capabilities at all is refused with At least one permission required. A key that somehow got minted without it is refused on the one action it exists to do, with 403 API key lacks read permission.

Four presets sit above the checkboxes:

• Full access. Read, write, publish and delete. This is the default for a create request that names no capabilities.
• CI / automation. Read, write and publish.
• Read only. Lists projects and entries. Changes nothing.
• Custom. Pick capabilities. Read stays on: every key needs it.

A CI key posts an entry and publishes it. It cannot delete an entry, and it cannot unpublish one: unpublishing takes the delete capability. Publishing an entry at the moment you create it needs both write and publish, which is what deploylog push --publish does. A key whose stored capability set is unreadable authorizes nothing: the caller gets the ordinary 403 FORBIDDEN rather than silent full access.

The key list

Each row carries the key name, its visible prefix, its capabilities, the date it was created and the date it was last used. A key holding nothing reads no capabilities.

Revoking is one click and one confirmation: Revoke this API key? Any integrations using it will stop working. The key is deleted and every call presenting it stops authenticating.

Connected repositories

An installation is the GitHub App's grant over the repositories you tick on GitHub. Settings lists them as owner/repo and offers a Connect repositories link that starts the install flow.

What the grant buys: repositories the DeployLog GitHub App can read for your manuals, a manual being the documentation set DeployLog keeps for a project. The manual is chapter 10. Pick them on GitHub; the connection comes back here. Before you install anything, the section reads No repositories connected yet.

Disconnecting is deliberately not offered here yet: removing a connection breaks every chapter, a numbered section of a manual, that points at that repository. The section lists and adds, and nothing else. It appears only when the manual feature is enabled for your account; with the feature off, settings renders without it.