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.

Make a project available

1. Sign in to server administration and open project management.
2. Open an existing project or create one at the intended server-accessible storage location.
3. Check its name, database and access paths. The browser does not need direct access to the project share or database.
4. Open the project and configure settings, users and groups.
5. 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.

Configure users, groups and permissions

1. Open project user management. Create users or use the configured Active Directory/LDAP integration.
2. Assign users to suitable groups and grant those groups the required roles. Membership in multiple groups can give a user multiple roles.
3. Set object permissions directly on folders, plans, test units or requirements. Review read-only access, full access and inheritance.
4. Check access with a representative role: visible structure, reading, editing and execution must match the task.
5. 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.

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.