Skip to content

First login

A freshly deployed Docsentry database has roles but no users. The first account is created from configuration at startup.

Supply both bootstrap keys. In development, user secrets keep them out of source control:

Terminal window
dotnet user-secrets set "Bootstrap:AdminEmail" "admin@example.com" --project src/Docsentry.Web
dotnet user-secrets set "Bootstrap:AdminPassword" "<a strong password>" --project src/Docsentry.Web

In a deployment, supply them as environment variables instead:

Terminal window
Bootstrap__AdminEmail=admin@example.com
Bootstrap__AdminPassword=<a strong password>

On startup the seeder runs in two steps:

  1. It creates any missing system role.
  2. If both Bootstrap:AdminEmail and Bootstrap:AdminPassword are present, it creates that user and assigns the Administrator role.

The step is idempotent - restarting does not create duplicates. If either key is absent, administrator seeding is skipped entirely and no account is created. That is a supported state for an environment where accounts arrive some other way, but it does mean a fresh database with no bootstrap keys leaves you with nothing to sign in as.

The password must satisfy the configured policy: at least 12 characters, with upper case, lower case, and a digit. If a breached-password source is configured, a password found in it is refused.

Five roles are seeded:

Role Intended for
Administrator Every administrative capability, and an override of document permissions.
RecordsManager Retention and metadata configuration: governance, content types, taxonomy, numbering.
WorkflowManager Authoring and managing workflow definitions.
Auditor The audit log and audit integrity verification. Cannot be combined with the three roles above.
User Ordinary use of the workspace.

Administrative screens are gated by capabilities assigned to these roles, so an auditor can review the audit trail without being an administrator. See Security hardening.

The Docsentry sign-in page

The sign-in page. Two-factor authentication is requested after the password.

1. Sign in with the bootstrap credentials. You land on the dashboard, which will be empty.

2. Enrol two-factor authentication. Administrators must enrol before they can reach anything else, so Docsentry sends you straight to the enrolment page. Scan the QR code with an authenticator app and confirm with a generated code. Store the recovery codes somewhere safe - they are shown once.

3. Create a folder. Go to Folders and create a root folder. Folder depth is capped by Folders:MaxDepth, which defaults to 10.

4. Upload a document. Open the folder and drag a file onto it, or use the upload page. A PDF or an image is the best first test, because those preview without needing LibreOffice installed.

5. Confirm the pipeline ran. The document should appear with a thumbnail once preview generation has run. If text extraction is configured, the document’s text panel fills in shortly after. Both happen on background jobs rather than during the upload request, so a short delay is expected - see Background jobs.

There is no public registration. Create further accounts from the Users screen under Administration; each new user receives an invitation email with a link to set their own password. Then assign roles and grant repository access. Configure Email first, or the invitation stays queued until mail is available.

See Users and roles for the account creation flow, and Departments and org units for grouping people so that access can be granted to a group rather than one person at a time.