Skip to main content

Manage sign-in methods and account deletion

Open Account from the top bar to manage your identity. A workspace Owner manages a workspace; a server administrator manages accounts and server settings. These roles are separate.

Share your User ID​

In Account → User ID, choose Copy user ID. If copying is unavailable, select and copy the displayed UUID. Give this ID to an Owner who needs to add you to a workspace; it works even when your account has no email.

Display name is how people recognize you. Account email is your registered address, when present. Automatic username identifies the account separately from the display name; it is generated by dtxWiki and is not used to sign in. Neither a matching name nor a provider's profile email replaces the user UUID.

The sign-in page offers email/password and the external providers configured by the operator. An external-only account can exist without a local password or account email. A provider profile email is not necessarily your account email.

To keep existing documents and memberships, sign in to the existing dtxWiki account first. Under Login methods, choose Add login method, then Link for the intended provider. Confirm with the identity belonging to this account. Matching email addresses do not automatically merge accounts.

You can Unlink a method when another available login method remains. Check that remaining method before confirming. Set password, when offered, creates an initial password rather than replacing an existing one. Add account email is available only when the server's mail and password-login capabilities are enabled; open its confirmation in the same signed-in browser. An account without email can continue using SSO.

Sensitive account and administrator actions require recent sign-in or verification, normally within 60 minutes. Session renewal does not extend that period. If it expires, use the displayed password, provider or email option. A one-time email verification link expires after five minutes. An SSO round trip does not guarantee that the provider requested a fresh password or MFA.

If a trusted email belongs to your existing account, sign in to that account and link the provider there. If the conflicting unverified-email account is not yours, choose This isn’t my account — ask a server admin. Its request ticket expires after 10 minutes; if expired, start the provider sign-in again and send a new request. The administrator reviews release of the address under the configured policy, deactivating the old account and revoking access while retaining its data. See SSO recovery.

Review deletion before confirming​

  1. Choose Delete account → Review account deletion.
  2. Read the retention period and affected workspaces.
  3. If you are the only admin of a workspace with other active members, appoint another active member or deliberately delete that workspace in its Settings. If you are the last active server administrator, the operator must first grant that separate authority to another active account with dtxwiki admin grant --user-id USER_UUID in the installation's configured maintenance environment. Members and administration explains the boundaries.
  4. Recheck the impact, type your account email when requested, and complete the password or recent identity confirmation shown.
  5. Confirm after reading the final scope.

Expected result: access ends immediately. Browser sessions, API keys and OAuth credentials are revoked. The account is retained for the configured period, 30 days by default. Zero days makes it eligible for the next cleanup. A server administrator can use Settings → User accounts → Restore account before cleanup starts. Restoration does not revive revoked credentials.

Workspaces in which you are the only member close with your account and are deleted with it. Documents, shared drafts, submitted changes, attachments and conversation history in other workspaces remain. After cleanup your name is no longer shown as their author; unsubmitted author-private MCP edits are deleted. Deletion does not erase every contribution from a team's records.

An administrator deleting another account reviews every workspace left without an admin. Appoint an admin → Make admin can preserve a held workspace by choosing an active member. That is workspace authority, not a server-admin grant. A changed policy or impact requires a fresh confirmation. Recovery is unavailable after cleanup begins.

See server account tools, SSO setup, and privacy.

Sources: account UI, administrator controls, account deletion, email-conflict ticket, identity recovery, administrator grant command.