Administer projects and access in the browser¶
The web interface separates project administration from server administration. Project administrators manage domain settings and access in their project. Server administrators configure the installation. A server sign-in does not replace a project role; AI requires additional approval.
Visitors to the public demo share one example project. It is reset every night. Demo visitors cannot open, create or close projects or sign out of the shared project. The Server administration link takes administrators to a separate sign-in page. The demo account alone does not grant access to administration.
Find your way around server administration¶
The dashboard and navigation menu group actions by task. Open Projects and users to manage projects and users, or Server and security for server settings. Jenkins and AI are under Integrations. API keys are under MCP. Open Diagnostics for the system check and server logs. Help and session gives you access to the manual, support and sign-out.
Support opens the support website, where you can contact support or download the remote assistance client.
In global or project MCP key management, choose Create API key. Set the expiry and permissions in the dialog. After creation, copy the key while it is displayed.
Choose Cancel to leave a form without saving. After a successful Save, you return to the previous administration page, or to the dashboard if you opened the form directly. If validation fails, the form stays open. Actions such as sending a test email show their result on the current page.
Open Report data sources to see the configured connections. Choose New data source or the name of an existing source to open its dialog. You can test the connection there before saving. Creating a project also opens a dialog. Jenkins connections have a dedicated editor page. In AI management, open the dialog for a new access rule from the list of rules.
For technical names and credentials, such as those for data sources, SMTP and Jenkins, the web client asks 1Password to skip fill and save suggestions. You can still use your password manager when signing in.
Choose your personal appearance and language in the user menu in the upper-right corner.
Recover a forgotten server password¶
When setting the initial server password, you can enter a recovery email address. This step is optional. On an existing installation, open Server and security → Admin password recovery in server administration and enter the address and your current password. Enter the confirmation code sent by email. The mailbox can then be used to reset the server password.
If you forget the password, open the server administration sign-in page, select Forgot password and enter the confirmed email address. Enter the code from the email within 15 minutes and choose a new password. The code can be used once. Existing server administration sessions expire; sign in with the new password. If no mailbox has been confirmed or you have lost access to it, contact the installation operator.
Configure email for server administration¶
In Server administration → Server and security → Email delivery (SMTP), configure email for the server administration, including password recovery codes. Each project's outgoing email uses its own settings.
- Enter the SMTP host, port and a sender address accepted by the provider.
- Select the encryption and authentication required by the provider. Selecting Username and password on an unencrypted connection enables STARTTLS. A custom port is retained. Choose Save to apply the settings immediately.
- Enter a recipient for the test email, send it using the saved settings and check the inbox. A success message means the SMTP server accepted the message.
| Connection | Typical port | When to use it |
|---|---|---|
| STARTTLS | 587 | The server must upgrade the connection to TLS before credentials or messages are sent. |
| Implicit TLS (SSL/TLS) | 465 | The connection is encrypted from the start. |
| Unencrypted | 25 | For a trusted relay without authentication. Messages and recovery codes can be read in transit. |
The port can be changed. Certificate validation is enabled by default. The exception for invalid certificates applies only to this SMTP connection. Someone intercepting the connection could obtain credentials or recovery codes. For an internal certificate, install the issuing certificate authority as trusted on the server whenever possible.
Authentication: Use no authentication for an IP-authorized relay, or enter the SMTP username and password. If your provider requires an app password, enter it as the SMTP password. For Microsoft 365 (OAuth 2.0) you need the tenant ID, application ID, client secret and a mailbox authorized to send. Use smtp.office365.com with STARTTLS and a valid certificate. In Exchange Online, set up SMTP AUTH, grant the application SMTP.SendAsApp and give the service principal access to the mailbox. Microsoft setup instructions
The web interface does not display saved secrets. Enter the secret again when changing the host, port, TLS or authentication details. When first saving settings in the browser, re-enter any password supplied by the service configuration.
Service configuration defaults: Until settings are saved in the administration area, the application uses AppSettings:Smtp from the server configuration. Choose Use server configuration to remove the settings saved in the browser and reactivate the service defaults. Restart the service after changing its environment variables.
| Environment variable | Value |
|---|---|
AppSettings__Smtp__Host |
SMTP server hostname |
AppSettings__Smtp__Port |
SMTP port, e.g. 587 for STARTTLS or 465 for implicit TLS |
AppSettings__Smtp__FromAddress |
Sender address accepted by the mail server |
AppSettings__Smtp__Security |
Encryption (StartTls, ImplicitTls, None) |
AppSettings__Smtp__Authentication |
Authentication (None, Password, Microsoft365) |
AppSettings__Smtp__IgnoreCertificateErrors |
Certificate exception (default: false) |
AppSettings__Smtp__TenantId, AppSettings__Smtp__ClientId |
Microsoft 365 tenant and application IDs |
AppSettings__Smtp__UseSsl |
For existing installations without Security: true for STARTTLS, false only for a local relay without authentication |
AppSettings__Smtp__UserName, AppSettings__Smtp__Password |
Credentials if the SMTP server requires authentication |
Verify delivery by confirming the recovery address. Use a mailbox that the responsible administrators can access even when they cannot sign in to Zeta Test Management.
Make a project available¶
- Sign in to server administration and open project management.
- Open an existing project or create one at the intended server-accessible storage location.
- Check its name, database and access paths. The browser does not need direct access to the project share or database.
- Open the project and configure settings, users and groups.
- Verify access using an intended user account before inviting further users.
Project folders and databases are accessed through the server identity. Technical administrators therefore need to check server access when file or database permissions fail.
Enable or disable project features¶
As a project administrator, open Project settings → Display and editor settings → Modules and relations. Select the features you need and save. Both administration pages update the same five switches.
As a server administrator, open Manage projects, select the project and click Check status. Under Project features, select the features you need and click Save. The selection applies to all web users of that project. Disabled features disappear from navigation and the dashboard, and direct requests are blocked. Existing data is retained.
Exploratory testing and Reference baselines are off by default. Reference baselines also controls importing a baseline into the test library. Reusable test steps and Library health are on by default. Requirements uses the existing project setting.
Configure users, groups and permissions¶
- Open project user management. Create users or use the configured Active Directory/LDAP integration.
- Assign users to suitable groups and grant those groups the required roles. Membership in multiple groups can give a user multiple roles.
- Set object permissions directly on folders, plans, test units or requirements. Review read-only access, full access and inheritance.
- Check access with a representative role: visible structure, reading, editing and execution must match the task.
- Send a web-access invitation where required. Check the recipient and project before triggering it.
Hiding a menu item does not replace permission enforcement. See user management for roles and inheritance; its Windows steps describe the Windows access path to the same project administration.
Change project settings¶
Open project settings and choose the relevant area, such as access, attachments, quick tests, attributes, result presentation or external tools. Record the current value before making a change, then check the affected user workflow.
For local tools and linked files, Local Bridge can provide approved Windows access. Browser downloads and web links do not require that local host.
Configure Office previews¶
- Sign in to server administration and open Appearance.
- Under Excel file preview (XLSX), select HTML table (default) or PDF (DevExpress).
- Save the setting. Newly opened XLSX previews use this selection for all projects and users of this web server installation.
The HTML table retains the existing worksheet selection and displays stored cell values. The PDF option generates a preview on the server. This setting does not change stored files or Windows previews. A project administrator role alone does not permit changing the server setting. DOCX and PPTX use Office PDF previews independently of this selection where the document is supported; see limitations and original downloads.
A global MCP API key can read the effective mode with ztm_admin_office_preview_settings_get and {}. The response contains xlsxPreviewMode as HtmlTable or DevExpressPdf. The same read operation is available through the REST API. Changes are made only in server administration; project API write permissions do not apply to this global setting.
Enable AI¶
Server administrators configure provider profiles, scenarios, data zones and traffic. Project administrators then grant the intended AI permissions. Test access with a domain question and review the visible sources. Changes also require ordinary object permissions and the preview/confirmation lifecycle.
Configure AI · Use AI in daily work.
If an area or action is missing¶
First check the signed-in account, project, group role and object permissions. Then check the licence, project features and administratively disabled web areas. Regular web areas are enabled by default in version 6; an installation can deliberately disable individual areas. For AI, also check global approval, provider readiness and scenario assignment.
Server administrators also have access to licensing, updates, logs, support packages, diagnostics and live statistics. Review diagnostic and support files for confidential project data before sharing them.
Version history¶
In server administration you can search and export release notes. In Spanish and Japanese, search and export use the translated entries. English is the source language. External entries without a translation appear in their original language.