Administration

Overview

Use Administration to manage server-side configuration and entities when a Kimura server is running and reachable.

The Administration panel can be accessed from both Visual Server and Visual Client, and requires admin access. The Administration window is organized into tabs so each management area has a focused workflow.

When you use it

Use Administration when you need to manage repositories, users, groups, file servers, revision rules, identity configuration, or licensing from one place.

What you can do here

• Open tab-specific administration workflows from a single window
• Create and update server-side entities
• Review current configuration and apply changes
• Validate administrative updates against the running server

Typical flow

1. Make sure a Kimura server is running and reachable.
2. Open Administration from Visual Server or Visual Client.
3. Open the tab for the area you need to manage.
4. Apply your changes and confirm expected results.

Repositories Tab

Use this tab to review existing repositories and their branches.

Main actions:

• View repositories and repository branches
• Create and delete repositories
• Delete branches

Branch creation is currently available from the Visual Client History tab.

Groups Tab

Use this tab to manage user groups and related group membership workflows.

Main actions:

• View current groups
• Create, edit, or remove group definitions as needed
• Assign users to groups and remove users from groups

Access control in this tab is managed per group through a hierarchy:

• Repository
• Branch
• Directory
• File

For each level, you can set access with No Access, Read, Write, or Super user from the context menu.

Access is inherited downward unless an explicit rule is set at a lower level.
Clear removes the explicit rule at the selected level and reverts to inherited access.

In the access list, * indicates an explicit rule on that specific item.

Users Tab

Use this tab to manage user accounts.

Main actions:

• View current users
• Create, edit, or remove users
• Adjust user properties and membership assignments
• Assign users to groups and remove users from groups

The Users tab shows key account fields including creation date, last access, group membership, and a Write access indicator. Write access means the user has write access to at least one repository.

User access to repositories, branches, directories, and files is group-based:

• Users do not receive these access rules directly in the Users tab
• Effective access comes from the groups the user belongs to
• To change repository/branch/directory/file access, update group access rules in the Groups tab

OpenID Connect Tab

Use this tab to configure OpenID Connect integration for authentication.

Main actions:

• Load the current OIDC configuration from the server
• Update identity-provider settings and submit them to the server

Configuration fields include:

• Authority
• Client ID
• Audience
• Scopes
• Authorize endpoint
• Token endpoint
• Redirect URI
• Require PKCE
• User name claim
• Issuer override
• Clock skew (seconds)

Use Update configuration to submit changes. The status area shows success/failure messages for load and update operations.

Clock skew must be a non-negative integer. The values entered here depend on the configuration used by your identity provider (IdP).

File Servers Tab

Use this tab to manage file server entries and repository access assignments.

A file server is a special user identity. Creating a file server in this tab creates a new user that can act as a file server.

Main actions:

• Add, edit, or remove file server entries
• For a selected file server, review repository access in the lower list
• Set repository access for the selected file server (Primary, Secondary, Backup, or NoAccess) from the repository list context menu

When adding a file server, you provide:

• File server name
• Password
• Up to three endpoints
• Optional Backup server flag

The configured endpoints are exposed as reference addresses. They define how users and other file servers can reach that file server.

When editing a file server:

• The file server name is read-only
• Endpoints and backup-server flag can be updated
• For FS-DEFAULT, the backup-server option is disabled

Repository access assignment behavior:

• Select a file server in the upper list to load repository access entries below
• Right-click a repository row to assign access for that selected file server
• Primary is only offered when the repository does not already have a primary file server assigned

Notes

• Administration changes affect shared server resources.
• Apply changes carefully in production environments.