Set up CE for a team

A shared CE instance gives a team a common place to connect to databases. Decide who can reach the instance and what its database credentials allow before distributing its URL.

Define who gets access#

Run WhoDB on a network or access path intended for the team. If you configure server-managed profiles, everyone who can reach that CE instance can select them and use their credentials. A profile alias names a connection; it does not create a separate user permission rule.

Use database accounts with permissions appropriate to the audience. An inspection instance can use read-only accounts. If two groups need different access boundaries, separate their instances or network access paths rather than relying on profile names.

Make the deployment persistent#

Follow Installation with a persistent data directory and a stable encryption key. This keeps the session store and its encryption configuration available when a container is replaced.

Configure HTTPS at the proxy and set WHODB_SECURE=true for the HTTPS deployment. Store connection credentials through your deployment's secret handling rather than putting production passwords in a shared example file.

Establish a few working conventions#

Name profiles so the environment and purpose are clear. Keep schema migrations, reusable queries, and fixture files in version control. Scratchpad pages, query history, and preferences belong to each browser; a shared CE URL does not turn them into shared documents.

When handing off an investigation, include the connection context, query, expected result, and relevant date. This makes the result reproducible without depending on another person's browser state.

Test the intended experience#

Connect with the planned database account and verify visible objects, read queries, and any permitted writes in a disposable target. Test a fresh browser session from the team's actual network before sharing the instance more widely.

Continue with Access control and Collaboration.